Save State Management: The Complete Guide for Retro Handhelds

Save states are one of the best features of emulation — quicksave anywhere, reload instantly, never lose progress. But they're also one of the most common sources of frustration when things go wrong. Accidentally loading an old state over hours of progress, losing saves when switching firmware, or discovering your states don't transfer to a new device — these problems are preventable with a little organization.

This guide covers how save states work, how to keep them organized, and how to protect yourself from losing progress across devices and firmware updates.

Save States vs. In-Game Saves

These are two different systems and understanding the distinction prevents most save-related headaches.

In-game saves (also called SRAM saves or .srm files) replicate what the original cartridge or memory card did. When a game says "saving..." at a save point, it writes to a virtual save file. These files are small, stable, and compatible across most emulators. If you save in Pokémon at a Pokémon Center, that save will work in RetroArch, standalone mGBA, and even on original hardware with the right tools.

Save states (.state files) are snapshots of the entire emulator's memory at a specific moment. They capture everything — your position, the frame you're on, which enemies are loaded, the state of the audio buffer, everything. They're instant and work anywhere in a game, but they're tied to the specific emulator core and version that created them. A save state made in RetroArch's Beetle PSX core won't load in PCSX-ReArch, and a state from PPSSPP 1.16 might not work in PPSSPP 1.17.

The golden rule: Use in-game saves as your primary save method. Use save states as a convenience layer on top. If you only use save states and never trigger an in-game save, you're one firmware update or accidental button press away from losing everything.

Save File Locations by Firmware

Knowing where your saves actually live on the SD card is essential for backups and transfers.

KNULLI: Saves are in /userdata/saves/ on your data partition, organized by system. Save states are in /userdata/saves/[system]/ alongside the .srm files. If you're using a dual SD card setup, saves live on the second card.

muOS: Saves are in /mnt/mmc/MUOS/save/ by default, with subdirectories per system. The exact path depends on your storage configuration.

Onion OS (Miyoo Mini Plus): Saves are in /mnt/SDCARD/Saves/CurrentProfile/saves/ organized by emulator core. States are in a parallel directory structure.

RetroArch (Android): Default save directory is /storage/emulated/0/RetroArch/saves/ for SRAM and /storage/emulated/0/RetroArch/states/ for save states. These can be customized in Settings > Directory.

Standalone emulators (PPSSPP, AetherSX2, Dolphin): Each app stores saves in its own Android data directory. PPSSPP uses /PSP/SAVEDATA/ and /PSP/PPSSPP_STATE/. AetherSX2 stores memory cards in its app data folder.

Organizing Your Saves

A clean save organization system takes five minutes to set up and saves hours of future headaches.

Name your save state slots intentionally. Most emulators offer multiple save state slots (typically 0 through 9). Don't just hammer slot 1 every time. Use slot 1 as your "current progress" slot, slot 2 as a "checkpoint before a hard boss" slot, and slot 9 as a "beginning of the game" backup. This way, you always have a fallback.

Use auto-save states carefully. Most RetroArch cores support auto-saving a state when you exit a game and auto-loading it when you resume. This is convenient but dangerous — if the auto-save triggers during a crash or glitch, it can save a corrupted state that auto-loads every time. Always keep a manual save state as backup.

Trigger in-game saves regularly. Every time you reach a save point in a game, actually use it. This creates a .srm file that's independent of save states and survives firmware changes, emulator updates, and device switches.

Backing Up Saves

The most reliable backup strategy uses the SD card itself.

Manual backup: Power off your handheld, remove the SD card, and copy the entire saves directory to your computer. Do this before any firmware update, before switching custom firmware, and periodically as general maintenance. A full saves folder for most people is under 500MB — it copies in seconds.

WiFi transfer (KNULLI and muOS): Both firmwares support network file access via SMB/Samba. Connect your handheld to WiFi, access it as a network drive from your computer, and copy the saves folder. No SD card removal needed.

Cloud sync for Android handhelds: If you're running RetroArch on Android (Retroid Pocket 5/6, AYN Thor, etc.), you can use Syncthing to automatically sync your saves folder to your phone or computer. Set it up once and your saves are backed up continuously over WiFi.

RetroArch cloud sync: RetroArch has a built-in cloud sync feature (Settings > Cloud Sync) that can push saves to a WebDAV server. If you run multiple RetroArch devices, this keeps your progress in sync across all of them. Setup requires a WebDAV endpoint — Nextcloud works well for self-hosters.

Transferring Saves Between Devices

Switching from a Miyoo Mini Plus to a Retroid Pocket 6? Upgrading from KNULLI to muOS? Here's how to keep your progress.

Same emulator, different device: Copy the save files (.srm and .state) from the old device's save directory to the same path on the new device. As long as both devices use the same RetroArch core (e.g., both use gpSP for GBA), saves transfer directly.

Different emulators, same system: In-game saves (.srm) usually transfer between different emulators for the same system. A Game Boy .sav file works in mGBA, Gambatte, and VBA-M. Save states do not transfer between different emulators — this is where in-game saves save you.

Linux firmware to Android: Copy the .srm files from the Linux firmware's save directory to RetroArch's saves directory on Android. In-game saves transfer cleanly. Save states won't — you'll need to load from an in-game save on the Android side.

PS1 memory card files: PS1 emulators use virtual memory card files (.mcr or .mcd). These are equivalent to in-game saves and transfer between PCSX-ReArch, Beetle PSX, and DuckStation. Copy the memory card file to the new emulator's memory card directory.

PSP saves: PPSSPP stores in-game saves in the SAVEDATA folder. These transfer to any other PPSSPP installation by copying the folder. PPSSPP save states are also usually compatible between versions on the same platform (Android to Android), but not always across platforms (Android to Linux).

Recovering from Save State Problems

State won't load after a firmware update: This is the most common issue. If you updated your custom firmware and your save states no longer load, your in-game saves (.srm files) are almost certainly fine. Launch the game, let it boot to the title screen, and load from the in-game save menu. You'll lose progress between your last in-game save and last save state, but the bulk of your progress is safe.

Accidentally loaded an old state: If you have multiple save state slots, check your other slots — your recent progress might be in a different slot. If not, check for a recent auto-save state. If you only had one save state and overwrote it, the progress between that state and your last in-game save is recoverable from the .srm file.

Save states are larger than expected: Some emulators compress save states, others don't. PS2 save states can be 30-50MB each. If you're running low on SD card space, clear out old save state slots for games you've finished.

Best Practices Summary

Always trigger in-game saves at save points — save states are a convenience, not a replacement. Use multiple save state slots so you have fallback points. Back up your saves directory before firmware updates. Keep your .srm files organized — they're your portable, cross-emulator insurance policy.

For setup guides on specific emulators mentioned here, see our RetroArch Setup Guide, PPSSPP Setup Guide, and AetherSX2 Setup Guide.