- Top Pick: Samsung T7 Portable SSD 1TB
- Runner-up: WD Elements Desktop 14TB External Hard Drive
- Also consider: WD Red Plus 8TB NAS Hard Drive
Every emulator update promises better compatibility, and most deliver it. The failures are rarely about the new build being bad. They happen because an update quietly moves, converts or orphans the files that hold your progress: a memory card left behind in an old folder, a save state the new version refuses to load, a per-game config the new build reads differently.
The fix is boring and it works every time: treat the emulator’s user folder as the thing that matters, and the program as replaceable. Copy the user data somewhere safe first, then prove your saves still load after the update, before you delete anything. This guide maps the folders that matter for PCSX2, Dolphin, RPCS3 and RetroArch, across Windows, Steam Deck and Android.
As an Amazon Associate, we earn from qualifying purchases.
This article contains affiliate links, and buying through them may earn a small commission at no extra cost to you.
Quick Answer
Back up the emulator’s user folder before you touch the update button. Copy PCSX2’s memcards and sstates folders, Dolphin’s GC, Wii and StateSaves folders, RPCS3’s dev_hdd0 savedata, and RetroArch’s saves and states folders to separate storage. Then update, boot one game per system, confirm an in-game save loads, and keep the backup until you have played normally for a few sessions.
The Golden Rule: Copy the User Folder First
Emulator programs are free to download again. Your saves are not. A memory card file represents hours of progress, and it exists in exactly one place unless you copy it. So before any update, close the emulator completely, find its user folder, and copy the whole thing to separate storage. Name the copy with the emulator, its version number and the date.
Keep two generations of backups, not one. The copy takes minutes; rebuilding a lost card takes a whole playthrough.
Backup Map: Where Each Emulator Keeps What Matters
You do not need to copy game images or the program itself. You need the folders holding saves, states and settings:
| Emulator | Copy these folders | Default home |
|---|---|---|
| PCSX2 | memcards, sstates, inis | Documents\PCSX2; ~/.config/PCSX2 |
| Dolphin | GC, Wii, StateSaves, Config | Documents\Dolphin Emulator |
| RPCS3 | dev_hdd0, config, savestates | The RPCS3 folder itself |
| RetroArch | saves, states, config, system | RetroArch folder; set in Settings > Directory |
Portable builds change the answer. A portable PCSX2 keeps those folders beside its executable, and Dolphin switches to a local User folder when a portable.txt file sits next to the program. RPCS3 is portable by design on Windows: everything lives in the folder you extracted it to. On a Steam Deck, Flatpak builds hide their data under ~/.var/app/ followed by the app ID, which catches many people who look in the usual Linux places.
What Actually Breaks When You Update
Save states are the fragile part. A state is a snapshot of a running build’s memory, and projects treat it as version-locked: RPCS3’s own wiki warns that updates bringing major changes can make save states incompatible with older or newer builds, Dolphin ties states to its version, and PCSX2 versions its states as well. In-game saves are different. A memory card image or savedata folder is plain data in the console’s own format, and it loads in any build.
Settings can migrate too. New builds sometimes convert an old config file on first launch, and that conversion is a one-way door: rolling back afterwards may not restore the original file. RetroArch adds its own wrinkle, because cores are separate programs. A renamed or replaced core can orphan the per-core config and remap files you built for the old name, and a core update can change how that core writes states.
One harmless effect scares people: shader caches rebuild after an update, so the first session stutters while new caches compile. That is not lost data. Give it a few minutes before judging the new build.
Know Your Build: Portable, Installed or Store-Managed
The safe update route follows the install type. A portable build keeps program and data in one folder, so updating means extracting the new build somewhere fresh and copying the user folders across. An installed build puts data in your Documents folder or a system config directory, so the program can be replaced freely while the data stays put.
The classic disaster is mixing routes: extracting a portable build, pointing it at nothing, and concluding the update ate your saves. It did not. The old folder still exists; the new build is simply looking somewhere else.
Updating on Each Platform
On Windows, several emulators update themselves. RPCS3 is a rolling release with a built-in updater that offers the newest build at launch. Dolphin offers update channels in its settings, and current PCSX2 builds can check for updates too. Let them, once your backup exists. For manual updates, extract the new build to a new folder rather than overwriting the old one, then copy the user folders across or point the new build at the old locations.
RetroArch separates the frontend from its cores. The frontend updates like any other program, while cores update in place when you run Update Installed Cores in the Online Updater. Copy the cores folder into your backup first if you depend on one core’s exact behaviour.
On the Steam Deck, Discover updates Flatpak apps in place and their data under ~/.var/app/ stays untouched, but back it up before a major update anyway. On Android, store updates keep the app’s data folder, while a sideloaded update must be signed the same way as the installed build or the install fails outright. A backup stored outside the app folder survives every outcome.
After the Update: Verify Before You Delete Anything
Boot one game per system you play. Load an in-game save from the memory card or savedata folder, not only a save state, because the in-game save is the thing you cannot replace. Check your controller profile still maps correctly, play a few minutes, and save again so the new build writes a fresh save.
Keep the pre-update backup until several normal sessions have passed.
The Rollback Plan
A rollback only works if the old build still exists. Rename the old install folder with its version number instead of deleting it, and keep the previous installer file for installed builds. With a portable build, rolling back is just launching the old executable.
If a save state refuses to load in the new build, roll back, load the state in the old build, save in-game at the next save point, then update again and continue from the in-game save.
When Skipping an Update Is the Right Call
Updates are optional, and sometimes waiting is the smart move. If you are deep into a long game and leaning on save states, finish it on the build that already works. If the changelog names none of your games and your library runs well, there is no prize for updating first. And skip the big version jump the night before a trip: update when you have an evening to verify.
Backup Storage Worth Using
A backup habit needs somewhere for the copies to live. These five cover the main shapes of that storage, from a fast pocket drive to a desktop archive.
Samsung T7 Portable SSD 1TB
The working backup drive: fast enough that copying whole user folders never feels like a chore, so the habit actually sticks. Keep it as the first copy, and let slower storage hold the archive.
Specs:
– Capacity: 1 TB
– Model: MU-PC1T0T/AM
– Interface: USB 3.2 Gen 2
– Speeds: up to 1,050 MB/s read, 1,000 MB/s write
– Encryption: AES 256-bit hardware encryption
WD Elements Desktop 14TB External Hard Drive
The set-and-forget archive. Fourteen terabytes swallows dated backup generations for every emulator you run, plus full game libraries, on a drive that lives on the desk.
Specs:
– Capacity: 14 TB
– Model: WDBWLG0140HBK-NESN
– Interface: USB 3.0
– Form factor: 3.5-inch desktop drive, AC adapter included
See the WD Elements Desktop on Amazon
WD Red Plus 8TB NAS Hard Drive
For households that emulate on several machines, a NAS drive turns backups into a shared, always-on target. This one is built for NAS enclosures running around the clock, with CMR recording that behaves predictably in RAID.
Specs:
– Capacity: 8 TB
– Model: WD80EFZZ
– Interface: SATA 6 Gb/s
– Speed: 5640 RPM, CMR recording, 128 MB cache
– Form factor: 3.5-inch internal drive for NAS bays
SanDisk 256GB High Endurance microSDXC Card
The Steam Deck and handheld option: a card rated for constant rewriting, sized for years of dated save backups, and small enough to live in the device it protects. A full-size SD adapter is included for moving copies to a PC.
Specs:
– Capacity: 256 GB
– Model: SDSQQNR-256G-GN6IA
– Ratings: Class 10, U3, V30
– Read speed: up to 100 MB/s
– Includes: microSD to SD adapter
See the SanDisk High Endurance card on Amazon
UGREEN USB 3.0 SD Card Reader
The humble shuttle between machines. When a backup lives on a microSD card from a handheld and needs to reach a desktop or NAS, a dual-slot reader makes the copy a drag-and-drop job.
Specs:
– Model: 40752
– Interface: USB 3.0, up to 5 Gbps
– Slots: SD and microSD, UHS-I
– Compatibility: Windows, macOS, Linux, Chrome OS
See the UGREEN card reader on Amazon
How to Choose
Match the backup target to where you play. A second drive in the same PC is the fastest copy and protects against bad updates, but not against losing the machine. An external drive you can carry between a desktop and a Steam Deck covers most setups. A NAS suits several machines and several players.
Capacity is rarely the problem: user folders are small, so dated generations cost little. Back up saves generously and every time; back up game images selectively, since you can dump your own discs and cartridges again. Two copies on two devices is the standard worth holding.
Who Should Skip
If you play one emulator on one machine, save only at in-game save points, and already sync that emulator’s user folder to storage you control, the full ritual is more than you need: one dated copy before a major update is enough. And skip the extra hardware entirely if a drive you own has room. The habit matters far more than the gear.
FAQ
Will updating PCSX2 delete my memory cards?
No. Cards live in the memcards folder inside the user folder, which a program update does not touch. People lose cards by extracting a portable build into a fresh folder and never copying memcards across. The backup-first rule prevents exactly that.
My save state will not load after an update. What now?
Roll back to the build that wrote it, load the state there, then save in-game to the memory card or savedata folder. In-game saves are version-proof; states are not. After that, update again and continue from the in-game save.
Does RetroArch update its cores by itself?
No. Cores change only when you run Update Installed Cores in the Online Updater or download a core again. Copy the cores folder into your backup first if you depend on a particular core build.
Is it safe to update in the middle of a long game?
In-game saves travel across versions safely, so the risk is low if you save at save points. If your progress lives mostly in save states, either finish the game on the current build or convert that progress into an in-game save before updating.
Final Verdict
Updates are worth taking, because compatibility work is the whole point of these projects, but they should never be a leap of faith. One dated copy of the user folder turns every update into a reversible experiment: back up, update, verify an in-game save, and play on.











