RetroArch save files vs save states on Android: protect both
Treat save files and save states as separate records. Save files are written by the emulated game or system and are usually the safer long-term choice; save states capture a core-specific running machine and can break after a core update. Close content cleanly, verify both configured directories, and restore a copy with the same core before relying on either.
Do this in order
- 01
Record the RetroArch build, core name and revision, content name, and whether the core reports save and state support.
- 02
Open Settings → Directory and record the exact Save Files and Save States locations instead of guessing an Android path.
- 03
Make an in-game save, close content normally, and confirm the save file timestamp changed.
- 04
Create a new save state in an unused slot and confirm the state appears in the configured state directory.
- 05
Copy both directories to a separate location while RetroArch is closed; keep core and content identity in the backup note.
- 06
Restore copies on the same core revision first, testing the in-game save before the state, and keep the previous backup after an update.
Decision and diagnostic table
| Record | Best use | Main risk |
|---|---|---|
| Save file / SaveRAM | Long-term progress written through the emulated system | Format and naming can still differ by core |
| Save state | Short-term snapshot and quick recovery | Tightly coupled to core and driver revision |
| Cloud or file backup | A second copy of both configured directories | Conflicting folder rules can create parallel files |
A state is not a newer save
A save state serializes internal emulator state that the original hardware never wrote as a normal save. Loading it can restore memory, timing, and storage state together, so it should not be treated as a universal replacement for an in-game save.
Prefer the game’s own save path for durable progress when the core supports it. Keep states as versioned convenience snapshots.
Prove where Android actually wrote the files
RetroArch exposes Save Files and Save States as separate directory settings. Android packaging and storage permissions vary, so a path copied from another device may be wrong or inaccessible.
The timestamp test proves the selected content and core are using the directory you plan to back up.
Restore in the least destructive order
Test on copies with the same RetroArch and core revision. Load the normal in-game save first; only then test a state in a spare slot. If the state fails after an update, preserve it with the older core rather than repeatedly overwriting newer progress.
Back up only progress and configuration you are entitled to keep. A saves folder may sit beside restricted game, BIOS, artwork, or music files; do not copy or share those files without permission.