Crimson Moon save file location on Windows
The best current public lead is %LOCALAPPDATA%\CrimsonMoonNG\Saved\SaveGames. Steam Cloud metadata reports that root, but this site has not performed a hands-on file check, so verify the folder before editing, moving, or deleting anything.
Use the reported local path first
%LOCALAPPDATA%\CrimsonMoonNG\Saved\SaveGames
Paste the path into File Explorer or the Windows Run dialog. The path comes from publicly visible Steam Cloud metadata mirrored by SteamDB; it is not presented as a personal confirmation of the active local save folder.
Two public results disagree about whether the game’s active files or Steam’s remote copy should be treated as the save location. That is why this guide gives you a verification-first path instead of telling you to overwrite a folder blindly.
How to check the Crimson Moon save folder
- Close Crimson Moon. Do not change files while the game is running.
- Press Win + R or open File Explorer.
- Paste
%LOCALAPPDATA%\CrimsonMoonNG\Saved\SaveGamesand press Enter. - Confirm that the folder exists and note its modified date before making any change.
- If it does not exist, search Windows for
CrimsonMoonNGand inspect the result rather than assuming that a generic Steam userdata folder is the active location.
Do not create a replacement folder just to make the path exist. Record your store, platform, game version, and whether Steam Cloud is enabled, then check the current official Known Issues ↗ (external; new tab) article.
Back up before troubleshooting save problems
For now, keep the same save on one device where possible. The developer still links many remaining save problems to switching devices after 1.0.2. Avoid moving the same run between PC and Steam Deck while that investigation continues.
- Exit the game and wait for Steam to finish showing its cloud-sync state.
- Copy the confirmed save folder to a separate dated folder, such as
Crimson Moon Save Backup 2026-09-03. - Keep the original folder unchanged. A backup is useful only if its files remain readable and separate from the live folder.
- When testing a recovery change, make one copy at a time and keep the previous backup available.
- If Steam presents a cloud conflict, stop and record which local or cloud version is being offered before choosing.
The official 1.0.2 release notes ↗ (external; new tab) describe safer overwrite prompts, corrected timestamps and fixes for information leaking between save slots. They also explicitly leave more complex save issues for planned Patch 1.1. An update is not a recovery procedure: preserve an independent copy, and do not replace the only good save to test whether a fix worked.
Local saves, Steam Cloud, and Steam Deck are not the same path
| Location or platform | Current evidence | How to use it safely |
|---|---|---|
| Windows local folder | Steam Cloud metadata reports %LOCALAPPDATA%\CrimsonMoonNG\Saved\SaveGames. | Use it as the first path to verify; do not treat metadata as hands-on confirmation. |
| Steam userdata remote copy | Some third-party pages mention Steam\userdata\<SteamID>\4317690\remote, but this was not verified as the active local root. | Do not overwrite or delete it while diagnosing a missing save. |
| Steam Deck / Proton | No reliable platform-specific local path was confirmed in this check. | Use current sync guidance and search the installed prefix only after making a backup. |
The Steam Cloud record identifies the Windows root used here; the released patch notes above provide newer sync context than the September 1 launch notice. The site does not claim to restore a lost save or guarantee that a copied file will load.
Crimson Moon save file FAQ
Start with %LOCALAPPDATA%\CrimsonMoonNG\Saved\SaveGames, which is the current public Steam Cloud metadata lead. Verify that the folder exists before changing anything.
It may contain a remote or cloud copy, but the checked evidence does not prove it is the active local save root. Treat it as unconfirmed.
Close the game, wait for sync to finish, copy the confirmed folder to a dated backup, and keep the original unchanged until the backup is readable.
No reliable Steam Deck or Proton-specific path was verified here. Do not copy a Windows path into Proton and assume it is correct.
PC and Steam Deck disagree: preserve evidence before switching again
In a September 12–17 Steam discussion ↗ (external; new tab), a player reported that the level shown in the load menu differed from the character actually loaded. A developer asked whether both devices were on 1.0.1 and passed the report to the team. This is evidence of an unresolved report, not a universal cause or a tested recovery method.
- Close the game on both devices. Preserve separate dated copies of any verified local saves before further testing.
- Record each device’s game version, Steam account and visible cloud-sync state.
- Record the level shown by the menu and the level actually loaded, if already observed. Do not overwrite a good save merely to reproduce the discrepancy.
- Send those details and the order of device use to official support ↗ (external; new tab). Do not assume the newer timestamp is the character you want.
The current 1.0.2 guidance is to avoid device switching for the same save while further fixes are pending. A missing character and an incorrect menu preview also require different evidence; keep both observations in the report.
For released and planned save-protection changes, check the official update timeline.
Further reference: Steam Cloud metadata mirrored by SteamDB ↗ (external; new tab) · Conflicting third-party path report ↗ (external; new tab).