Few things sting like losing a save. When Snes9x states refuse to load or a game’s battery save is gone next session, the cause is almost never corruption — it is almost always location. Snes9x writes both kinds of save to one specific folder, and if that folder is somewhere Windows will not let it write, the saves silently never happen. This guide explains where saves are supposed to live, how to check the path Snes9x is actually using, and how to recover from the most common failure. For a fresh, official copy of the emulator see our download page; more fixes are in the troubleshooting hub.
Where Snes9x saves are supposed to go
By default, both save systems write to a folder called Saves in the same folder as snes9x.exe (the config defaults are literally .\Saves for both savestates and SRAM). Battery saves — the game’s own save feature — are stored as .srm files, written when the ROM is unloaded or you quit, and loaded automatically the next time you play that game. Save states (freeze files) live in the same folder, named .000 to .099: Snes9x 1.63 gives you 10 quick slots per bank (Shift+F1–F10 to save, F1–F10 to load) across 10 banks — up to 100 states per game. If you go looking for your saves anywhere else, you will not find them.
The Program Files trap
The classic failure: you extracted Snes9x into C:\Program Files or another protected location. Modern Windows blocks ordinary programs from writing there, so Snes9x cannot create or update the Saves folder — in-game saves appear to work during the session, then are missing next time, and state saves fail outright. The fix is simply to move the whole Snes9x folder somewhere your account owns: a folder on your desktop, in Documents, or something like C:\Games\Snes9x. Copy your existing Saves folder along with it so anything that did get written comes too.
Check the Saves path in settings
The Saves location is a setting, and it can be changed — which means it can also be changed by accident, or left pointing at a folder from an old setup. Open Snes9x’s settings and check the directories for savestates and SRAM: both should point at a folder that (a) exists and (b) you can write to. If the path names a drive or folder that no longer exists, browse to your real Saves folder and set it explicitly. After changing it, save a state and load it straight back as a smoke test.
States that exist but won’t load
If the state files are visibly present in Saves but refuse to load, check which slot and bank you are in — with 10 banks, the state you want may simply be in a different bank than the one you are browsing. Also keep in mind that save states are snapshots of a specific emulator build’s internal format; a state created by a very old Snes9x version may not load in 1.63 (the documented freeze format changed in the past and old formats were not kept compatible). Battery .srm saves are far more portable than states — another reason to use the game’s own saving for anything you care about long-term.
The .oops recovery file
One more resident of the Saves folder is worth knowing: if you quit Snes9x without saving after playing for a long time, it writes an .oops auto-recovery freeze file there. If you closed the emulator by accident mid-session, look for that file before assuming the session is lost — loading it can put you back where you were.
A reliable saving routine
To keep this from recurring: keep Snes9x in a writable folder, confirm the Saves path once, and use both systems for what they are good at — .srm battery saves as your durable progress, states as quick bookmarks. Our save states and .srm guide explains the two systems in full. If instead the game itself will not open at all, see ROM won’t load, and if the emulator opens to a black window, see the black screen fix.
Related files you will find in the Saves folder
While you are in there, two other file types belong to the same system. Games with a real-time clock use .rtc files alongside the .srm, and your cheat lists are stored as .cht files that Snes9x reloads automatically when the same game is loaded again. None of these should be deleted during troubleshooting unless you have a backup — “cleaning up” the Saves folder by removing unfamiliar extensions is a quiet way players lose clock data and cheat setups. It is also worth knowing that the save files are keyed to the game: if you replace a ROM with a differently named file — a re-dump with a new filename, for example — Snes9x will look for saves under the new name and your old .srm will sit unused in the folder. Renaming the save files to match the ROM’s new name is the standard way to reunite them.
Back the folder up
Once saving works, protect it: the entire Saves folder is small and self-contained, so copy it somewhere safe whenever you finish a long session in a game you care about. A copied folder also makes moving to a new PC painless — install Snes9x, drop your Saves folder next to the new executable (keeping the same game filenames), and your battery saves and states come with you. A dated backup copy also gives you an undo if a state ever gets saved over by accident: with banks and slots it is easy to overwrite the wrong slot, and the only real protection is a folder copy made before it happened. Treat the quick test as your routine after any settings change: save a state, load it back, save in-game, restart the game, and confirm both are exactly where you left them.