---
title: "Lost a save in RetroArch? Recover it — and set up auto-backup so it never happens again"
canonical_url: https://emudesk.com/issues/retroarch-lost-save-state-srm-recovery-autobackup
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.686Z
freshness_status: fresh
---

# 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 .srm file 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.