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.
Identify the exact save you intend to edit
The researched Dead Cells 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. Known file/folder pattern: user_*.dat and customGameData_*.json. Storefront 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
Copy the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .dat, .json 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Dead Cells, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Dead Cells save paths and file patterns.