✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is Samsung 990 PRO 2TB NVMe SSD, with Samsung T7 Portable SSD 1TB as a strong alternative.

Save states are the fastest insurance in PCSX2: one keypress freezes the whole emulated PlayStation 2 mid-frame, and another brings that exact moment back. They are also the easiest way to lose a long run, because a state is a snapshot of the emulator itself, not a normal game save, and it ages badly.

As an Amazon Associate, we earn from qualifying purchases.

This guide is a field manual for using them properly. It covers the three hotkeys that run the system, the ten slots each game gets and the backup copy hiding behind them, where the files live and how they are named, why states refuse to load after updates, and the routine that keeps your real progress on a memory card where it belongs.

This article contains affiliate links, and we may earn a commission when you buy through them at no extra cost to you.

Quick Answer

PCSX2 gives each game 10 save state slots. Press F1 to save a state to the current slot, F2 to move to the next slot (Shift+F2 goes back), and F3 to load. States live as compressed .p2s files in the sstates folder, are tied to your PCSX2 version and BIOS, and should back up, never replace, memory card saves.

Three Keys Run the Whole System

Everything starts with the default hotkeys, which you can confirm or rebind under Settings, then Hotkeys.

  • F1 saves a state into the currently selected slot, overwriting whatever was there.
  • F2 moves the selection to the next slot. Shift+F2 moves it back one slot.
  • F3 loads the state in the currently selected slot.

An on-screen message names the slot and the game every time you save, load or cycle, so watch it before you press F1 out of habit: saving into the wrong slot is the most common self-inflicted loss. If you prefer menus, System, then Save State and Load State list the same slots directly, each with its screenshot and timestamp. Players on compact keyboards without a proper F-row should rebind these three actions early, because a missed F-key press during a boss fight usually means reaching for the wrong slot at the worst moment.

Ten Slots and the Backup Behind Them

Each game gets 10 slots, numbered 0 to 9, and the set belongs to that game alone: states are matched to the disc by its serial and checksum, so one title never sees another title’s slots. Ten sounds generous until a long role-playing game fills them with boss attempts, branching choices and one slot you are afraid to touch.

The safety net is quieter. When you save over an occupied slot in current builds, the outgoing state is kept as a backup copy of that slot rather than being destroyed outright. That gives you exactly one generation of undo: overwrite a good state by accident, notice immediately, and the previous version is still recoverable. It is not a version history, though. Save over the same slot twice and the older backup is gone too, which is why the routine below still treats slots as disposable.

Where States Live: the sstates Folder

States are plain files you can copy, move and back up. Open Tools, then Open Data Directory in PCSX2 and look for the sstates folder; on a standard Windows install it sits inside Documents, PCSX2, sstates, and portable builds keep it beside the executable. Memory cards live in the neighbouring memcards folder.

Every filename tells you what the file is. A state is named from the game’s serial, then the disc checksum in brackets, then the two-digit slot number, with a .p2s extension. A role-playing game in slot 3 is therefore one recognisable file, and sorting the folder by name groups a whole library game by game.

A .p2s file is a zip archive, and its contents explain both its size and its fragility. Inside are the machine’s memory images, the graphics and sound processor states, an internal structures file, a small version identifier and the screenshot PNG you see in the load menu. Compression keeps that far smaller than the raw snapshot, but a single state still runs to megabytes rather than the kilobytes of a card save block, and ten slots across dozens of games adds up quietly. High internal resolutions make the graphics portion heavier, and HD texture packs inflate a game’s footprint further, although the replacement textures live in their own folder, not inside the state.

Why States Refuse to Load

Three different checks can stop a state, and telling them apart saves guesswork.

Version. The version identifier inside every state is stamped by the build that wrote it. When PCSX2 releases change the state format, the identifier’s major version moves, and a newer or older build will refuse the file outright with an unsupported-version error. PCSX2’s own advice in that message is the recovery path: load the state in a build that accepts it, make a memory card save, then carry the card forward. Nightly builds move this target more often than stable ones.

BIOS. A state also records the checksum and description of the BIOS it was created with, dumped from your own console. Load it under a different BIOS and PCSX2 warns that the state may be unstable instead of blocking you. Treat the warning seriously: some games are picky, so keep one BIOS selected for a whole playthrough.

The disc. Because the filename and the state both carry the game’s checksum, a different pressing or region of the same title is a different game as far as states are concerned, and its slots stay separate.

Finally, a state written while the game itself was mid-save can freeze a corrupted moment in place. That risk is the practical reason for the routine that follows.

The Safe Routine: States for Moments, Cards for Progress

  1. Use states inside a session: before a boss, a gamble, a long unskippable cutscene or a risky jump.
  2. Rotate slots instead of hammering one. Leave the earliest slot of a session untouched as your anchor.
  3. At every real save point the game offers, save to the virtual memory card as well. That save is the one that survives updates.
  4. Before updating PCSX2, finish your session on a card save, then copy the whole memcards and sstates folders somewhere safe.
  5. Back up the memcards folder on a schedule. It is small, and it is the only part of the setup that is genuinely irreplaceable.

When a State Fails: The Recovery Ladder

Work down the rungs in order and stop at the first one that gets you playing again.

  1. Try the backup copy of the slot you overwrote or the state that misbehaves; one generation back is often close enough.
  2. Fall back to the memory card save from the same session and replay the gap. This is why the routine above exists.
  3. Roll the emulator back. Install the older PCSX2 build that wrote the state, load the state there, play to the next in-game save point and save to the card. Then return to your current build and continue from the card.
  4. Check the BIOS selection if the load produced a mismatch warning or odd behaviour; reselect the BIOS the playthrough started with and try again.
  5. Delete the dead state once your progress is safe on a card, so you never load it by accident from the menu.

Gear That Makes State Habits Easier

Samsung 990 PRO 2TB NVMe SSD

Samsung 990 PRO 2TB NVMe SSD

Samsung 990 PRO 2TB NVMe SSD

Check price on Amazon

Fast storage shortens the pause while a state is written and read, and 2TB swallows a big state library without housekeeping.

  • Specs:
  • Interface: PCIe 4.0 x4, NVMe 2.0
  • Maker-stated speeds: up to 7,450 MB/s read and 6,900 MB/s write
  • Endurance rating: 1,200 TBW
  • Model: MZ-V9P2T0B/AM

See it on Amazon

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Check price on Amazon

A pocket drive for the second copy of your memcards and sstates folders, kept away from the PC they came from.

  • Specs:
  • Interface: USB 3.2 Gen 2
  • Maker-stated speeds: up to 1,050 MB/s read and 1,000 MB/s write
  • Encryption: AES 256-bit hardware encryption
  • Weight: 2.08 oz
  • Model: MU-PC1T0T/AM

See it on Amazon

Keychron K4 Wireless Mechanical Keyboard Version 2

Keychron K4 Wireless Mechanical Keyboard Version 2

Keychron K4 Wireless Mechanical Keyboard Version 2

Check price on Amazon

A compact board that keeps a real F1 to F12 row, so the state hotkeys stay under your fingers without a function-layer hunt.

  • Specs:
  • Connection: Bluetooth and wired USB-C
  • Layout: compact board with dedicated F-row
  • Battery: 4,000 mAh, maker figure
  • Keycaps: Mac and Windows sets included
  • Model: K4-A3

See it on Amazon

Zerone 128MB Memory Card for PS2

Zerone 128MB Memory Card for PS2

Zerone 128MB Memory Card for PS2

Check price on Amazon

A physical card for the console side of the workflow, handy when you still move saves between a real PlayStation 2 and PCSX2.

  • Specs:
  • Capacity: 128 MB
  • Form factor: PlayStation 2 memory card slot
  • Compatibility: stated by the maker for PS2 and PS2 Slim consoles
  • Colour and packaging: not stated

See it on Amazon

Sony DualSense Wireless Controller, White

PCSX2 accepts modern pads natively, and the DualSense gives you spare buttons to bind save and load state to the controller.

  • Specs:
  • Connection: Bluetooth and USB-C
  • Features: haptic feedback and adaptive triggers
  • Weight: 280 g
  • Model: CFI-ZCT1W

See it on Amazon

How to Choose

Choose your habits before your hardware. If you play one game at a time on a stable build, the defaults plus a card routine are enough. If you run nightly builds, treat states as disposable: save to a card at the end of every session and keep dated copies of the memcards folder. If you move between machines, put the portable build and both folders on fast external storage so states and cards travel together, matched to the same build. Decide where your backups live before you need them, because the recovery ladder works far better with a copy of the folders than without one.

Who Should Skip

Skip heavy state use if you are mid-playthrough on a nightly build you update daily; the version stamp will eventually strand your slots, so lean on card saves instead. Skip states entirely for RetroAchievements hardcore runs, where loading them is restricted anyway. And if you only play short arcade sessions, the default three keys and an occasional card save are all you need; the full routine is for long games where losing progress actually hurts.

FAQ

Do PCSX2 save states work after updating the emulator?

Often, but not always. Minor updates usually keep the state format, while format changes bump the version stamp and make older states refuse to load. The fix is to load the state in the build that wrote it, save to a memory card, and continue from the card in the new build.

How many save states can I keep per game?

Ten slots per game, numbered 0 to 9, plus the single backup copy kept when you overwrite a slot. If you need more, copy .p2s files out of the sstates folder into your own archive and copy them back when you want them.

Are save states tied to my BIOS?

Partly. A state records the checksum of the BIOS used to create it, and loading under a different BIOS produces a stability warning rather than a block. Staying on one BIOS dumped from your own console for a whole playthrough avoids the issue.

Can I move save states to another PC?

Yes, by copying the .p2s files into the other machine’s sstates folder. They still need a PCSX2 build whose state version matches and the same game pressing, while memory card saves move between builds and machines without that restriction.

Final Verdict

PCSX2 save states are superb session tools and poor archives. Learn F1, F2 and F3, rotate your ten slots, respect the backup copy’s single-generation limit, and let memory cards carry anything you would be upset to lose. Do that, and an unsupported-version error becomes a minor detour through the recovery ladder instead of the end of a playthrough.

Explore Our Guides & Free Tools