Monster Hunter: World keeps its main Steam PC progress in SAVEDATA1000. Because the file sits under an account-specific Steam userdata tree, the account context belongs in the backup record. Copy the file outside Steam before major changes and keep multiple dated revisions rather than relying on cloud synchronization alone. A future editor must handle account/profile semantics explicitly; Phase 23 only documents where the file lives and how to preserve it safely.
Which storefront context matters
Documented Monster Hunter: World PC launchers/storefronts: Steam. The save is under Steam userdata, not the Monster Hunter: World installation directory. The numeric user folder identifies the Steam account context. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
Steam Cloud/remote storage is part of the normal PC workflow. Manual backups are still valuable because a damaged local revision can also synchronize. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: <Steam-folder>userdata<user-id>582010remote | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/582010/pfx/; the known file or folder pattern is SAVEDATA1000. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Copy SAVEDATA1000 to a dated location outside Steam userdata. For extra context, record the Steam account/ID that produced the file. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Third-party save transfers often need Steam-ID-aware handling. This Game Hub does not claim that a SAVEDATA1000 file from another account is directly portable. If progress disappears or rolls back, If progress is missing after a cloud conflict, preserve both the current remote/local file and any backup before trying replacement. Avoid repeatedly launching the game while deciding which copy is authoritative. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
Verification context: The Steam userdata path was reviewed against current PCGamingWiki coverage. SAVEDATA1000 naming is corroborated by long-running Steam/Nexus backup references.