Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Game Hub / Save Reference

Dead Cells Save Files & Tools

Dead Cells PC save location, backup, file-format, launcher, cloud-sync, and compatibility reference. This Game Hub documents save-file facts without implying that a game-specific Save Editor is available.

PC

01 / Overview

Save reference at a glance.

Game Hubs separate documented save-file facts from actual Tool support. A Game Hub can be useful even when no custom editor exists.

Developer
Motion Twin; Evil Empire
Publisher
Motion Twin
Platforms
PC
Save extensions
.dat, .json

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.

For this PC reference, the documented storage 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. 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.

Backup guidance: Copy the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder. Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition. Launcher and cloud context matters because The exact path depends strongly on storefront. Preserve both user_*.dat and customGameData_*.json if you want the same profile plus custom-game settings.

Compatibility and recovery should stay conservative. 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 the expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.

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.

02 / Save locations

Where the save files are stored.

Paths are displayed only when they have been explicitly documented for this Game Hub. Environment variables and launcher-specific differences should remain visible instead of being silently normalized.

Windows
Steam: <Steam-folder>userdata<user-id>588650remote ; Microsoft Store: %LOCALAPPDATA%PackagesMotionTwin.DeadCellsWin10_rtjy889c6zgtgLocalCacheLocalMotionTwinDeadCells ; other desktop builds may use <path-to-game>save

Launcher / edition differences

The exact path depends strongly on storefront. Preserve both user_*.dat and customGameData_*.json if you want the same profile plus custom-game settings.

03 / File format

Files, extensions, and format notes.

This section documents only known file names and structures. Format notes can later connect directly to SaveEditor.com parsers, checksum engines, and converters.

Extensions

.dat .json

File names / patterns

  • user_*.dat and customGameData_*.json

Format notes

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.

Launchers / stores

Steam / GOG / Epic Games Launcher / EA app / Microsoft Store

Cloud save notes

Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition.

04 / Tools

Actual linked Tool support.

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

No active game-specific Tool is currently listed.

Planned and deprecated Tool records are intentionally excluded. The save-reference information on this page remains separate from Tool availability.

05 / Backup

Protect the original before editing.

Save editing should be reversible. Keep an untouched copy outside the active save directory before replacing, converting, repairing, or modifying a save.

  1. 01
    Close the game.

    Avoid modifying a save while the game or launcher may still be writing to it.

  2. 02
    Copy the entire relevant save set.

    Some games use multiple files, profile folders, metadata, or companion files rather than one isolated save.

  3. 03
    Store the backup elsewhere.

    Use a separate folder or archive so cloud sync or the game cannot overwrite the untouched backup.

  4. 04
    Edit a copy, then validate.

    Follow the exact compatibility and processing notes on the Tool page before replacing the active save.

Game-specific backup note

Copy the full active save directory, including user_*.dat and customGameData_*.json. On Steam, back up the complete 588650remote folder.

06 / Troubleshooting

When a save is missing or rejected.

Start with reversible checks. Do not delete or overwrite the only copy while diagnosing a path, cloud-sync, version, or format problem.

Game-specific notes

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.

A

Confirm the correct profile.

Games, launchers, and operating systems may keep separate save folders for different users, editions, or profiles.

B

Check cloud synchronization.

A cloud service can restore an older file or overwrite a local change. Preserve both copies before resolving a conflict.

C

Check Tool compatibility.

A matching filename does not prove a matching format. Verify platform, game version, extension, and Tool support state.

D

Restore the untouched backup.

If the game rejects a modified save, return to the original backup before attempting another change.

07 / FAQ

Dead Cells save-file questions.

Answers are generated only from visible Game Hub metadata and actual linked Tool states, plus universal backup guidance.

Where are Dead Cells save files stored?

The currently documented save locations are listed in the Save locations section above. Use the location that matches your platform or environment.

What save-file extension does Dead Cells use?

The extensions currently documented on this page are: .dat, .json.

Does SaveEditor.com have a verified Dead Cells Save Editor?

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

Should I back up the save before using a Tool?

Yes. Keep an untouched copy outside the active save directory before modifying or converting the file. Some games use multiple companion files, so back up the relevant save folder when in doubt.

Are there cloud-save considerations for Dead Cells?

Steam Cloud, GOG Galaxy, Epic, EA, and Xbox Cloud are documented depending on edition.

Editorial review

Game-specific metadata on this hub was last reviewed on 2026-08-08. Individual Tool pages maintain their own verification dates and compatibility notes.

Verification notes

Reviewed against current PCGamingWiki Dead Cells save paths and file patterns.