- Top Pick: Samsung 990 PRO 2TB NVMe SSD
- Runner-up: Keychron K4 Wireless Mechanical Keyboard Version 2
- Also consider: Nintendo GameCube Controller, Super Smash Bros. Black Edition
Dolphin gives you two ways to keep progress in a GameCube or Wii game, and they look more interchangeable than they are. The game can save to a virtual memory card or the emulated Wii system memory, in formats the game itself understands. Or you can press a hotkey and freeze the entire emulated console mid-frame, mid-animation, mid-sentence, in a file only Dolphin understands. That second option, the save state, is one of the most useful tools in the emulator and the one behind almost every lost-progress story involving it.
As an Amazon Associate, we earn from qualifying purchases.
This guide covers how the slots and hotkeys work, what the undo keys rescue you from, why states are tied to your Dolphin build in a way memory card saves are not, and how states interact with netplay, tool-assisted movies and cheats. Everything here assumes games dumped from discs you own.
This article contains affiliate links, and we may earn a commission when you buy through them at no extra cost to you.
Quick Answer
Dolphin save states freeze the whole emulated GameCube or Wii at any moment: Shift+F1 to Shift+F8 saves to slots 1 to 8, F1 to F8 loads, and F12 undoes a load. States are session tools that break across Dolphin versions, so always pair them with normal in-game saves, which stay portable and safe.
What a Dolphin Save State Actually Captures
When you save a state, Dolphin serialises the complete condition of the virtual machine: CPU registers, the console’s RAM, graphics and audio chip state, timers, the disc drive’s position, and the working state of the emulated memory card or Wii system memory. Loading the state pours all of it back in, and play resumes at the exact instant you froze, even where the game offers no save point at all. That total recall is the feature’s power and its fragility in one package.
State files live in the StateSaves folder inside Dolphin’s user directory, named after the game, so a library of states stays organised per title and can be copied or archived like any other files. Dolphin also offers save state to file and load state from file in its Emulation menu, for states you want outside the slot system — a boss attempt you intend to keep for months, for example.
Slots and Hotkeys: The F-Key System
Dolphin’s default layout is built around the function keys. There are eight numbered slots per game. Shift+F1 through Shift+F8 saves to slots 1 to 8, and F1 through F8 loads the matching slot. The Emulation menu mirrors the same actions for mouse users, and every one of these bindings can be remapped in Dolphin’s hotkey settings if your keyboard buries the F-row behind a function modifier, as many laptop and compact keyboards do.
Two further hotkeys matter more than any slot. F12 is undo load: if you load the wrong slot, or load a state by accident, F12 returns you to where you were before the load. Shift+F12 is undo save: if you overwrite a valuable state with a careless save, it restores the state your save replaced. Together they convert the two most common save state accidents from disasters into shrugs, and they are worth memorising before the slots themselves. Because loading is a single unmodified keypress, treat F1 to F8 with respect — a stray press during a boss fight is exactly what undo load exists for, but needing it mid-fight is still a scramble.
The Golden Rule: States Serve the Real Save
Here is the fact that organises everything else: a save state is written for the Dolphin build that created it, and Dolphin’s own documentation warns that older save states may not work between versions. When the emulator’s internals change — and Dolphin updates constantly — a state recorded by an older build can refuse to load or load incorrectly. The failure arrives at the worst moment: you update mid-game, reach for your state, and find your only record of twenty hours is a file the new build cannot read.
The game’s own save has no such problem. A GameCube memory card save, stored by Dolphin as a .raw card image or individual .gci files, and a Wii save in the emulated NAND, are data the game wrote in its own format. They load in any Dolphin version, travel between PCs, and survive every update. So the golden rule: states are for inside a session, saves are for between sessions. Use states for a boss attempt, a tricky jump, a branching choice. Use the game’s save points for quitting, updating Dolphin, changing PCs and anything that must still exist tomorrow. Before updating Dolphin, always land on a real in-game save first; treat the update as a wall your states may not cross.
Save States, Netplay, Movies and Cheats
States collide with three other Dolphin features, and each collision follows from the same determinism. Dolphin’s netplay keeps every player’s machine in lockstep, frame by frame, from a shared starting point. Loading a personal state on one machine changes that machine without changing the others, and from that frame onward the session is two different games sharing inputs — a desync with no recovery except restarting together. States are therefore not a mid-netplay tool.
Tool-assisted speedruns lean the opposite way. Dolphin records input movies, and state loading is part of how those movies are built frame by frame: attempt a segment, load back, refine. The catch is consistency — a movie and its states belong to the settings and build they were created with, so changing graphics backends or options mid-project can invalidate the work. Cheats interact too: a state captures the machine with whatever Action Replay or Gecko codes were active, so loading states around cheat changes is a classic route to odd behaviour. The pattern across all three: a state is a photograph of one exact configuration, and it behaves best when the configuration stays put.
Safe Habits That Prevent Lost Progress
Four habits cover nearly every bad outcome. First, the double-save habit: whenever you reach a real save point after a stretch of state-assisted play, use it. States got you there; the in-game save banks it. Second, reserve states for moments inside a session — attempts, experiments, practice — and rotate slots deliberately instead of hammering one, so a bad save overwrites your least valuable state rather than your only one. Third, before updating Dolphin or moving PCs, quit through an in-game save and confirm it loads; states can come along in the StateSaves folder, but as a bonus, never as the plan. Fourth, after loading an old state to retry a section, remember it also restored the memory card’s condition at that moment — so once you succeed, save in-game promptly.
Recovering From a Bad State
When something goes wrong, work the ladder from least to most drastic. Wrong slot loaded: press F12, undo load, and you are back before the mistake. Valuable state overwritten: Shift+F12, undo save, restores what your save replaced. State refuses to load after an update: this is the one with no trick — the state belongs to the old build, and the recovery is your in-game save, which is why the golden rule exists. If you kept the old build around, its states still load there, and you can play to a save point and bank progress properly. And if a state loads but the game behaves strangely, suspect configuration drift: cheats toggled since the state was taken, or settings changed mid-game. Return to a real save and treat that state as suspect.
Hardware That Makes State-Heavy Play Smoother
States are written and read constantly, so the hardware around Dolphin matters. These five picks support state-heavy play, fast loading and safe backups.
Samsung 990 PRO 2TB NVMe SSD
A fast internal drive shortens game loading and the constant state writes of a long session, and gives a large library room to live beside its StateSaves folder.
Specs:
– Interface: PCIe 4.0 x4, NVMe M.2 2280
– Sequential read: up to 7,450 MB/s
– Sequential write: up to 6,900 MB/s
– Capacity: 2TB
Keychron K4 Wireless Mechanical Keyboard Version 2
State play lives on the F-row, so a keyboard with a full, reachable function row matters; the K4 keeps F1 to F12 in a compact frame, by cable or Bluetooth.
Specs:
– Layout: compact near-full-size with full F-row
– Connectivity: Bluetooth and wired USB-C
– Switches: Gateron G Pro mechanical
– Model: K4-A3 variant
Nintendo GameCube Controller, Super Smash Bros. Black Edition
For games where you retry the same jump forty times, the original pad removes control differences from the experiment; this wired reissue plugs into a GameCube controller adapter for Dolphin.
Specs:
– Connection: wired, GameCube connector
– Compatibility: GameCube, Wii models with ports, adapter use on PC
– Edition: Super Smash Bros. Black Edition
– Cable length: not stated
Samsung T7 Portable SSD 1TB
Backing up the Dolphin user folder — states, memory cards and settings together — takes seconds on a fast portable drive, and it is cheap insurance.
Specs:
– Interface: USB 3.2 Gen 2
– Read speed: up to 1,050 MB/s
– Write speed: up to 1,000 MB/s
– Capacity: 1TB
SanDisk 256GB High Endurance microSDXC
For Dolphin on a handheld PC, the card holding your games and StateSaves folder gets written constantly; a high-endurance card is built for that write load.
Specs:
– Capacity: 256GB
– Speed class: Class 10, U3, V30
– Read speed: up to 100 MB/s
– Endurance: rated for continuous recording workloads
How to Choose
Choose your state discipline by how you play. Session players working through long games need the double-save habit and little else: states for attempts, in-game saves for banking, one update rule. Retry-heavy players — boss rushes, hard platformers, speedrun practice — should spread work across several slots, learn the undo keys cold, and use save state to file for attempts worth keeping. Netplay players should treat states as off-limits mid-session and save only through the game itself. And anyone mid-game on an old Dolphin build should bank progress in-game before updating, then let states rebuild on the new build.
Who Should Skip
Skip the discipline if you never touch states; in-game saves alone are a complete, safe way to play everything Dolphin runs. Skip states specifically if you play netplay where session rules govern saving, and if your speedrun category bans mid-run states — follow the category. And if your keyboard makes the F-row genuinely painful and you will not remap the hotkeys, the Emulation menu covers the occasional state.
FAQ
Do Dolphin save states work after updating Dolphin?
Often not. States are written for the build that created them, and Dolphin’s documentation warns older states may fail between versions. Before updating, save in-game; card and Wii saves carry across versions.
Can loading a save state delete my in-game save?
It can roll it back. A state captures the emulated memory card’s condition too, so loading an old state returns your in-game progress to that moment. Save in-game promptly after retrying a section from a state.
How many save state slots does Dolphin have?
Eight numbered slots per game, on F1 to F8 for loading and Shift+F1 to Shift+F8 for saving, plus save state to file for states kept outside the slots.
Can I use save states during Dolphin netplay?
No. Netplay depends on every machine staying in lockstep from a shared start. Loading a personal state changes only your machine and desyncs the session.
Final Verdict
Dolphin save states are a superb session tool and a poor archive. The F-key slots make attempts cheap, the undo keys forgive the two common accidents, and none of it replaces the game’s own save, the only record guaranteed to survive Dolphin’s next update. Pair the two systems as described — states for the moment, saves for the record — and the feature gives you its convenience without its famous heartbreak.











