For DST, first identify whether you are preserving local client state or a hosted Cluster_* world. Copy the complete cluster, including all shards, rather than one session file.
Which storefront context matters
Documented Don't Starve Together PC launchers/storefronts: Steam. The active Steam installation determines which local profile and cloud copy can overwrite the save. Identify the storefront and account before restoring files. 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 can synchronize client data; dedicated/server-hosted clusters must be backed up at the host. 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: %USERPROFILE%DocumentsKleiDoNotStarveTogether; the known file or folder pattern is client profile data and Cluster_* world/server directories. 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
Close Don't Starve Together, let the launcher finish any synchronization, then copy the complete documented save directory to a dated folder outside the live path. Preserve companion files rather than selecting only the newest-looking record. 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
Treat saves as version-, storefront-, account-, and mod-sensitive unless the game or a separately verified migration workflow proves otherwise. A similar filename or extension is not evidence that two releases are interchangeable. If progress disappears or rolls back, If progress is missing after a restore, confirm the active Windows account, storefront/profile, cloud state, and exact directory first. Restore the untouched backup before experimenting with individual files or older autosaves. 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: Windows save location, file-boundary, launcher/cloud, and backup notes were reviewed against the linked game-specific references for Don't Starve Together. This Game Hub is documentation only and does not claim a new game-specific Save Editor.
Recorded Phase 40 evidence boundary
This Phase 40 entry is grounded in the researched PC save boundary for Don't Starve Together: Windows: %USERPROFILE%DocumentsKleiDoNotStarveTogether The recorded file or folder pattern is client profile data and Cluster_* world/server directories. These concrete identifiers are retained so backup, transfer, recovery, and editing preparation remain tied to the documented game/storefront context instead of a generic extension guess.