✅ 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 T7 Portable SSD 1TB, with WD Elements Desktop Hard Drive 14TB as a strong alternative.

A new PC is the easy part of this job. Every emulator you use is a free download, and reinstalling one takes minutes. What is not replaceable is the layer underneath: years of in-game saves, per-game settings and controller profiles, scattered across user folders most people have never opened.

As an Amazon Associate, we earn from qualifying purchases.

A clean move emulators to new PC workflow treats the job as a data migration, not a reinstall. You inventory where each emulator keeps its data, copy those folders in the right order, repair the paths that still point at the old machine, and prove every save loads before the old PC is wiped or sold. This guide maps the locations from each project’s own documentation.
This article contains affiliate links, and buying through them may earn a small commission at no extra cost to you.

Quick Answer

Move the data, not just the programs. Install fresh copies of your emulators on the new PC, then copy each emulator’s user folder — PCSX2’s memcards, Dolphin’s GC and Wii folders, RPCS3’s dev_hdd0, PPSSPP’s memstick, DuckStation’s data directory — from the old machine. Boot every emulator and load a save before you wipe or retire the old PC.

Step Zero: Inventory Before You Copy Anything

Ten minutes of inventory now prevents a failed copy later; the list becomes your verification checklist at the end.

  • List every emulator you actually use, including the one you only open for a single game.
  • Mark each one portable or installed. Portable builds keep data beside the program; installed builds keep it in your profile.
  • Note where your game library lives and which drive letter it uses.
  • Note your frontend, if you use one, and where its folder sits.
  • Check destination space. User folders are small; frontend media and a full library are not.

Portable vs Installed: Why Some Emulators Move in One Folder

Some emulators are built to travel. RPCS3 is portable by design on Windows: the program, its config folder and the dev_hdd0 virtual drive all live inside the one folder you extracted, so moving RPCS3 means moving that folder. Dolphin and PCSX2 both offer a documented portable switch: an empty portable.txt beside Dolphin’s executable makes it use a local User folder instead of the global one, and PCSX2’s documentation describes a portable.ini or portable.txt beside its executable for the same trick. DuckStation likewise documents a portable.txt that keeps its data beside the program. PPSSPP splits the difference: its memory stick defaults to a memstick folder beside the executable, and only falls back to Documents when it cannot write beside the program.

Installed builds are the opposite shape. A standard PCSX2 install keeps its data in Documents\PCSX2, Dolphin in Documents\Dolphin Emulator, and DuckStation in a data folder inside your user profile. Copying the program folder of an installed build moves the shell and leaves every save behind — the most common failed migration.

The rule: for portable builds, copy the whole folder. For installed builds, install fresh on the new PC and copy only the user folder into the matching location.

The Location Map: Where Each Emulator’s Data Lives

Copy these folders:

Emulator Copy these folders Default home on Windows
PCSX2 memcards, sstates, inis Documents\PCSX2; beside the program in portable mode
Dolphin GC, Wii, StateSaves, Config Documents\Dolphin Emulator; local User folder with portable.txt
RPCS3 dev_hdd0, config, savestates The RPCS3 folder itself
PPSSPP The PSP folder inside the memory stick (SAVEDATA, PPSSPP_STATE) memstick beside the program, or Documents\PPSSPP
DuckStation memcards, savestates, bios, settings files Data folder in your user profile; beside the program with portable.txt
RetroArch saves, states, config The RetroArch folder; paths set in Settings, then Directory

Two cautions belong with the map. PPSSPP’s documentation describes both the memstick beside the program and the Documents fallback, so open File, then Open Memory Stick, on the old machine and copy from the folder it shows you. DuckStation’s profile location has changed across versions, so confirm the active data directory in its settings.

The Move, in Order

Step 1: Close everything, then copy saves and settings first. With every emulator shut, copy the user folders from the map to your transfer drive.

Step 2: Install fresh builds on the new PC. Same versions as the old machine, if you can. Launch each once so it creates its default folders, then close it.

Step 3: Lay your copied folders over the new defaults. Replace the freshly created user folders with your copies, in the same locations. For portable builds, place the whole copied folder where it will live.

Step 4: Copy or re-point the games last. Game images are large and re-dumpable, so they move after the saves are proven safe. If the library keeps the same drive letter and layout, most emulators will find it untouched. If the letter changed, point each emulator’s game directory setting at the new location.

Step 5: Verify before you retire anything. Boot every emulator, load one game per system, and load an in-game save — not just a save state. Tick each emulator off the list only after that load succeeds.

What Does Not Move Cleanly

Some breakage after a move is normal and fixable, and none of it means your saves are gone:

  • Shader caches rebuild. Caches are compiled for the old machine’s graphics hardware. Expect stutter in the first session while new caches compile.
  • Save states stay version-locked. States are snapshots of one build’s memory. Move to the same build and they usually load; change versions mid-move and they may refuse. Verify with native in-game saves, plain data in the console’s own format.
  • Absolute paths break. Any setting that stored a full path with a drive letter — a game directory, a BIOS folder, a frontend entry — still points at the old letter.
  • Hardware-tuned settings follow you. Resolution scales and renderer choices made for the old GPU come along in your config. Harmless, but revisit them after the move.

Fixing Frontend Paths After the Move

LaunchBox is documented by its developers as a portable application: nothing goes into the Windows registry, and its settings and library live inside the LaunchBox folder. Whether it survives a move untouched depends on how your games were added. Games and emulators kept inside the LaunchBox folder, or on the same drive, are recorded with relative paths and simply work after the folder is copied. Games kept on a different drive were recorded with full paths including the drive letter; if the new machine assigns a different letter, either change the letter to match or edit the affected paths. Keeping the same root folder names makes that a small find-and-replace instead of a rebuild.

ES-DE takes the other common shape: its configuration and library metadata live in its own application data folder under your user profile, while the games directory is a separate setting. Copy the data folder across so your lists and settings survive, then confirm the games directory points at the library’s new home.

Gear That Makes the Move Easier

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Check price on Amazon

  • Specs:
  • Capacity: 1 TB
  • Model: MU-PC1T0T/AM
  • Interface: USB 3.2 Gen 2, up to 1,050 MB/s read and 1,000 MB/s write
  • Security: AES 256-bit hardware encryption

The transfer drive for the whole job: fast enough that copying a full library is an errand, not an afternoon, and it doubles as the off-machine copy of your user folders after.

See it on Amazon

Crucial X9 Pro Portable SSD 1TB

  • Specs:
  • Capacity: 1 TB
  • Model: CT1000X9PROSSD902
  • Interface: USB-C, USB 3.2 Gen 2, up to 1,050 MB/s read and write
  • Rating: IP55, with 256-bit AES encryption support

A second, different portable SSD is the belt-and-braces copy: user folders ride on this one while the library rides on the first, so one failed drive cannot take both halves.

See it on Amazon

WD Elements Desktop Hard Drive 14TB

WD Elements Desktop Hard Drive 14TB

WD Elements Desktop Hard Drive 14TB

Check price on Amazon

  • Specs:
  • Capacity: 14 TB
  • Model: WDBWLG0140HBK-NESN
  • Interface: USB 3.0
  • Form: mains-powered desktop enclosure

The retirement archive. Before the old PC is wiped, its entire emulator layer — user folders, frontend folder and library — goes onto this drive, which then sits unplugged as the last-resort copy.

See it on Amazon

Sabrent USB-C NVMe Enclosure (EC-PNVO)

Sabrent USB-C NVMe Enclosure (EC-PNVO)

Sabrent USB-C NVMe Enclosure (EC-PNVO)

Check price on Amazon

  • Specs:
  • Model: EC-PNVO
  • Interface: USB 3.2 Gen 2, 10 Gbps over USB-C
  • Compatibility: M.2 NVMe SSDs, 2230 to 2280 sizes
  • Design: tool-free flip-open aluminium enclosure; SSD not included

If the old PC’s boot drive is an M.2 NVMe SSD, this enclosure turns it into a fast external drive for the move, and a rescue route for anything forgotten afterwards.

See it on Amazon

UGREEN USB 3.0 SD Card Reader

UGREEN USB 3.0 SD Card Reader

UGREEN USB 3.0 SD Card Reader

Check price on Amazon

  • Specs:
  • Model: 40752
  • Interface: USB 3.0, up to 5 Gbps
  • Slots: SD and microSD, UHS-I

Handhelds and single-board setups keep libraries and saves on memory cards. This reader lets the new PC pull a card’s saves into the migration instead of treating the handheld as an island.

See it on Amazon

How to Choose

Choose the method by the shape of your setup. Mostly portable builds: copy whole folders and be done. Mostly installed builds: fresh installs plus user-folder copies, and budget time for path repairs. A library too big to copy comfortably: move only the user folders and frontend data, keep the games on their existing drive, and keep its drive letter and layout identical. Whatever you choose, sequence it saves first, games last, and never combine the move with a version change.

Who Should Skip

Skip the full migration if the old PC is staying in service as a second machine; a network copy of the user folders, done later at leisure, is safer than a deadline move. Skip whole-folder copying if your installs are a mix of portable and installed builds you cannot tell apart — inventory first, because guessing wrong is how saves get left behind. And skip the transfer-drive shopping if your user folders already live in a verified synced backup; then only the installed builds’ settings and frontend paths need attention.

FAQ

Can I just copy the whole emulator folder for every emulator?

Only for portable and self-contained builds such as RPCS3, or Dolphin and PCSX2 running with their portable marker files. Installed builds read their data from Documents or your profile folder, so the copied program folder arrives empty of saves.

Do my save states survive the move?

The files travel, but states are locked to the build that wrote them. Moving to the same version usually keeps them loadable; changing versions during the move can orphan them. Always verify with native in-game saves, which are version-proof.

My frontend shows every game as missing. What broke?

Paths, almost always. Entries recorded with a drive letter still point at the old machine’s letter. Either assign the library drive its old letter or update the paths in the frontend; the games themselves are fine.

Should I update my emulators while I move?

No. Two changes at once make failures impossible to attribute. Migrate on the same versions, verify every emulator loads a save, and only then update, with the old PC still intact as your fallback.

Final Verdict

Moving emulators to a new PC is a folder problem, not a software problem. The programs are free and reinstall in minutes; the user folders — PCSX2’s memcards, Dolphin’s GC and Wii, RPCS3’s dev_hdd0, PPSSPP’s memory stick, DuckStation’s data directory — are the actual collection. Inventory them, copy them first, repair the paths that name the old machine, and make every emulator prove it can load a save before the old PC is wiped.

Explore Our Guides & Free Tools