RetroArch Save States: Slots, Rewind, and Fast-Forward

RetroArch keeps two kinds of progress. An in-game save writes to a memory card or cartridge SRAM. A save state freezes the whole emulator at that frame. Rewind and fast-forward are a third thing: they move time without writing a file. Mixing them up is how people lose a clear they thought was safe.

Save state versus in-game save

Use both.

• The in-game save is what survives a core update. It is the real progress on the cartridge or memory card.
• The save state is a shortcut. It is tied to that core version. Update the core, and an old state can fail to load. The in-game save still works.

Before a long session, save in the game menu once. Then use states for the risky minute: a boss, a race, a missed jump.

Default hotkeys

On a stock RetroArch install:

• Save state: F2
• Load state: F4
• Fast-forward hold: Space, on most builds
• Rewind: off until you enable it

Change them under Settings, Input, Hotkeys. If you set save and load to the same key, you will overwrite the state you meant to restore. Pick two keys you can hit without looking, and leave them alone.

States have slots. The Quick Menu shows the current slot. Saving always writes the current slot. Loading always reads the current slot. Move the slot before you save if you want to keep the previous one.

Turn rewind on without wrecking performance

Rewind stores a buffer of recent frames. Settings, Frame Throttle, Rewind. Enable it, then set the buffer. A 30 to 60 second buffer is enough for platformers. Larger buffers on N64, PS2, or Saturn cores cause stutter because the core is already expensive.

Rewind is the wrong tool for a 10-minute mistake. Load a state or the in-game save instead. Rewind is for the jump you missed one second ago.

Fast-forward

Fast-forward runs the core as fast as the CPU allows, up to the ratio you set. Use it on long RPG text and slow level-ups. Turn it off for anything that needs timing: fighting games, shoot 'em ups, and netplay.

A fast-forward toggle that stays on will desync a session with a friend, because you are no longer on the same frame clock. The general rules are in save states, rewind, and fast-forward. RetroArch is just the specific key map.

Where the files go

RetroArch writes states next to the save directory you set under Settings, Directory. If you move a ROM, old states stay behind and look "missing." Point the save directory at a folder you back up, not at a temp path.

RetroApp keeps states with the library entry so a rescan does not orphan them. The same rule applies: make one in-game save before you trust states alone.

Netplay

Do not load a state during a netplay match unless everyone loads the same state on the same frame. Rewind and fast-forward are local. They will desync the room. Play the match, then use states in single player. Live rooms are listed on netplay.