Lost a save in RetroArch? Recover it — and set up auto-backup so it never happens again
A RetroArch save or save state that "vanished" is almost never actually deleted. In most cases it's sitting on disk under a name RetroArch no longer matches (a renamed, re-dumped, or different-region ROM) or it was held in memory and never flushed before a crash — find it first, then turn on SaveRAM autosave so it can't recur.
You boot a game in RetroArch and your progress is gone: the in-game save slot is empty, a save state won't load, or the save was there yesterday and today the game starts from scratch. Losing hours of progress feels catastrophic — but in the large majority of cases the save isn't actually deleted. It's sitting on disk under a name RetroArch is no longer looking for, or it was held in memory and never written out before the program closed.
First, the two save types RetroArch uses — because the fix differs:
- In-game saves (SaveRAM /
.srm): the save the game itself writes when you "Save" at an in-game menu (the cartridge battery save). RetroArch keeps this in memory and flushes it to a.srmfile in your Save Files directory. - Save states (
.state): a full snapshot of the emulator's memory that you trigger from the RetroArch menu. These are slot-based (.state,.state1,.state2…) and live in your Save States directory.
Cause: the four things that make a save "disappear" are — (1) the ROM was renamed, re-dumped, or is a different region, so RetroArch looks for a differently-named save file and finds none; (2) SaveRAM was never flushed to disk because RetroArch crashed or the PC powered off before it wrote the .srm; (3) you loaded or overwrote the wrong save-state slot; or (4) the save directory itself was moved or wiped (reinstall, cloud sync, portable build relocated). The fixes below go in recovery order: find it first, then recover unflushed SaveRAM, then lock in auto-backup so it can't recur.
Solutions
solution #1406
Your save is almost certainly still on disk under a name RetroArch isn't matching. Confirm the directories and the filename first — this recovers most "lost" saves.
- Find the real locations: Settings → Directory and note Save Files (
.srm) and Save States (.state). Open those folders in your file manager. - Renamed-ROM mismatch (the #1 cause): RetroArch names every save after the content filename. If you renamed the ROM, changed regions, or swapped a
.zipfor a.chd, the oldGameTitle (USA).srmno longer matchesGameTitle.chd. Rename the save file to exactly match the ROM's base name (keep the.srm/.stateextension) and reload. - Save states — cycle the slot: in the in-game menu (F1) → Save State Slot, step through slots 0–9 and try Load State on each. A state you thought was lost is often on a different slot than the one currently selected.
- "Sort into folders" surprise: if Settings → Saving → Sort Saves Into Folders is on, saves sit in a per-core or per-content subfolder, not the top-level Save directory — look one level deeper before concluding it's gone.
Reality check: if the .srm/.state file exists with a recent timestamp and a non-zero size, your progress is intact — this is a naming/location mismatch, not data loss, and step 2 fixes it.
solution #1407
The save folder is genuinely empty after a crash or hard shutdown? RetroArch holds SaveRAM in memory and only writes the .srm when content closes — if it never closed cleanly, the write never happened. You can't recover what was never written, but you can stop it recurring immediately, and rescue any partial state.
- Turn on periodic flushing now: Settings → Saving → SaveRAM Autosave Interval. The default can be 0 (off), meaning SaveRAM is only written on a clean exit. Set it to 10 seconds so the
.srmis flushed to disk continuously — a crash then costs you at most a few seconds, not the whole session. - Check for an auto save state: if Auto Save State was on, RetroArch wrote an
.state.autonext to your other states when content last closed. In the file manager, look for a.autofile; enable Auto Load State (S3) and reload the game to resume from it. - Don't overwrite a good save with an empty one: if the game is now showing "no save," do not let it start a fresh save and close normally — that flushes an empty
.srmover any file you're still trying to recover. Sort out the filename in S1 first, with autosave interval already raised.
Honest limit: SaveRAM that was only ever in memory at the moment of a crash is unrecoverable. Everything in S3 exists so that's the last time it can happen to you.
solution #1408
Spend two minutes here once and lost-progress stops being possible. These settings make RetroArch save continuously, snapshot on exit, and resume on launch. All are under Settings → Saving unless noted.
- SaveRAM Autosave Interval → 10 seconds. Flushes in-game saves to disk continuously (see S2) so a crash can't wipe a session.
- Auto Save State → On and Auto Load State → On. RetroArch writes a snapshot every time you close a game and silently resumes it next launch — a safety net even for games with no native save.
- Increment Save State Index → On (and optionally Save State Thumbnails → On). New states go to a fresh slot instead of overwriting the last one, so you keep a ladder of restore points instead of a single overwritable save.
- Sort Saves Into Folders / Sort Save States Into Folders → On. Keeps each game's saves isolated so two ROMs with similar names can never collide and clobber each other.
- The real backup — copy the folders out. The settings above protect against crashes; they don't protect against a reinstall, a wiped drive, or a portable build you move. Periodically copy your Save Files and Save States directories (from S1) to cloud storage or another drive. They're small, plain files — a one-line copy is your insurance.
Related fixes: if your controller stops registering and the game looks "stuck" rather than save-broken, see RetroArch doesn't detect my controller. If saves load fine but the picture is glitched after a driver change, see the clean GPU-driver guide.
Comments (0)
Sign in to_leave_comment