Dead Cells has several legitimate Windows save roots depending on storefront, which makes timestamps and launcher context more useful than the filename alone. Steam users should preserve app ID 588650 remote data; other editions may write under the install directory or LocalAppData. The save set also includes customGameData JSON separate from user_*.dat. SaveEditor recommends backing up both categories so a restored profile does not silently lose custom-mode configuration.
Which storefront context matters
Documented Dead Cells PC launchers/storefronts: Steam, GOG, Epic Games Launcher, EA app, Microsoft Store. The exact path depends strongly on storefront. Preserve both user_*.dat and customGameData_*.json if you want the same profile plus custom-game settings. 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, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition. 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: <Steam-folder>userdata<user-id>588650remote ; Microsoft Store: %LOCALAPPDATA%PackagesMotionTwin.DeadCellsWin10_rtjy889c6zgtgLocalCacheLocalMotionTwinDeadCells ; other desktop builds may use <path-to-game>save; the known file or folder pattern is user_*.dat and customGameData_*.json. 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 the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder. 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
A user_*.dat file can restore player progress without restoring custom-game JSON, so a partial copy may look inconsistent even when the main save loads. If progress disappears or rolls back, If the wrong profile appears, check whether the game is using Steam remote, LocalAppData, or an install-folder save. Then compare timestamps before overwriting anything. 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: Reviewed against current PCGamingWiki Dead Cells save paths and file patterns.