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.
Choose the correct backup boundary
For Dead Cells, the researched PC save location 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 save file or folder pattern is user_*.dat and customGameData_*.json. Copy the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: 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.
Account for cloud saves
Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Dead Cells stores player data and custom-game configuration separately. Steam uses app-ID remote storage, while other desktop releases can use the installation save directory and Microsoft Store uses package-local/WGS-style storage. Compatibility note: 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. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
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. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Reviewed against current PCGamingWiki Dead Cells save paths and file patterns.