- Top Pick: Samsung T7 Portable SSD 1TB
- Runner-up: SanDisk 1TB Extreme microSDXC UHS-I Card
- Also consider: Lenovo Legion Go S (Ryzen Z2 Go, 16GB, 512GB)
A Windows desktop and a Windows handheld run the same emulators, so a two-machine setup feels like it should sync itself. It does not. Each emulator writes progress to its own folders, in its own formats, and a sync tool only copies files. It cannot tell a battery save from a memory card, or from a state only one build can read.
As an Amazon Associate, we earn from qualifying purchases.
The real work is the map: which folders each emulator writes to, which files travel cleanly, and which quietly break. Get it right and any sync method works. Get it wrong and you can overwrite a long save with an empty file from the other machine.
This article contains affiliate links, and we may earn a commission if you buy through them.
Quick Answer
To sync emulator saves between a Windows PC and a Windows handheld, sync the folders the emulators actually write to: RetroArch’s saves and states folders, PCSX2’s memcards, Dolphin’s GC and Wii folders, DuckStation’s memcards and PPSSPP’s SAVEDATA. Point one sync folder at each pair, keep both emulators on the same build, and keep a separate one-way backup, because sync also copies mistakes.
Start With the Map, Not the Tool
Every emulator below keeps its save data in a folder tree visible in Windows Explorer. A portable install, the kind most handheld owners use, keeps the tree beside the emulator’s own executable, the easiest layout to sync. An installed copy puts its data in Documents or AppData.
Two rules shape everything that follows. Sync folders, not individual files: a card image or save folder often has companion files, and copying half a set can corrupt a save. And match the setup on both machines first: same emulator, same version, same folder options. Most sync horror stories are two slightly different setups writing to different places, with the tool copying the wrong file over the right one.
RetroArch: Two Folders and One Setting That Must Match
RetroArch splits progress across two folders. In-game saves, the battery saves the games themselves write, are .srm files in the saves folder. Save states are .state files in the states folder. Settings, then Directory, shows the exact paths your copy uses. Sync both as a pair.
The setting that must match is under Settings, then Saving: Sort Saves into Folders by Core Name, and its twin for states. With sorting on, a Game Boy Advance save lands in a per-core subfolder, saves then mGBA; off, it sits in the root of saves. If the desktop sorts and the handheld does not, each machine writes to a different subfolder and the game never sees the other machine’s progress. Nothing is lost, but nothing syncs either. Set it identically on both; if you change it later, move existing files by hand, because RetroArch will not.
Leave Write Saves to Content Directory off on both machines: it parks saves beside game files, where sync pairs miss them.
PCSX2: One Card File Holds Everything
PCSX2 keeps PlayStation 2 progress inside virtual memory cards, in a memcards folder in its data directory. The standard images, Mcd001.ps2 and Mcd002.ps2, hold one slot each, and a single card file holds every save written to that slot. The card is the unit, so the memcards folder is the sync target.
That makes PCSX2 the simplest emulator to sync and the easiest to damage: a conflict on one card file puts every save on it at stake. Close PCSX2 fully on both machines before a sync runs, and never open a card image in a memory card editor while PCSX2 is running, because two writers to one card image is how cards corrupt. The folder-style card option works too: sync the whole card folder, superblock included, same type on both machines.
Dolphin: Two Systems, Two Places to Sync
Dolphin’s data lives in a single User folder, and File, then Open User Folder, takes you straight to it. Inside, GameCube and Wii progress sit in different places, and a complete sync needs both.
GameCube saves are under the GC folder. With a memory card image, slot A is one file, MemoryCardA.USA.raw, with the region in the name. With a GCI folder instead, each save is an individual .gci file inside a region folder, then Card A. The modes store progress in different shapes, so both machines must use the same mode and the same region card. GCI folders sync more gracefully: one game’s save changing does not rewrite a whole card image.
Wii saves live inside the Wii folder, Dolphin’s copy of the Wii’s NAND storage, each game in its own title folder. Sync it as a unit; it also carries system files the emulated Wii expects together. Dolphin states sit in a StateSaves folder in the same tree.
DuckStation and PPSSPP: Small Folders, Same Rules
DuckStation keeps PlayStation progress in a memcards folder; Tools, then Open Data Directory, reveals it. Cards are .mcd files, either one shared card for all games or a separate card per game, named after the title. Separate cards are friendlier for syncing: a conflict touches one game instead of a whole library. States live in a savestates folder beside it. Match the card mode on both machines.
PPSSPP treats a folder as the PSP’s Memory Stick: memstick beside the executable on a portable install, or in Documents under PPSSPP when installed. File, then Open Memory Stick, shows the active one. Inside its PSP folder, SAVEDATA holds in-game saves, one folder per game, and PPSSPP_STATE holds states. Sync the whole PSP folder. The trap is an inactive lookalike: if saves vanish after a copy, check the path inside the emulator, not in Explorer.
What Travels Cleanly and What Breaks
Battery saves and memory card images are the travellers: written in the game’s own format, they open on either machine, and usually in a later version or different emulator too. If you sync nothing else, sync those.
Save states are the fragile layer. A state is a snapshot of one build’s internal memory layout: update the emulator or a core on one machine only, and a synced state may refuse to load or load badly. States also break across cores for the same system. Sync them if you like, but never let a state be the only copy of your progress; before an update on either machine, save in-game and let that sync first.
Sync is faithful, not wise. A deletion on the handheld syncs to the desktop; a corrupt card image can replace the good copy. That is why the gear section’s backup is one-way and separate, on a drive sync never touches: sync keeps two machines equal, a backup keeps yesterday reachable.
The Sync Itself, Kept Short
With the map settled, the tooling is the easy part. Syncthing is the usual choice: it pairs folders directly between your own machines over your network, with no cloud account in the middle. Install it on both, pair the devices once, then create one shared folder per emulator location from the map above.
A cloud-drive folder works too, with one caveat: a cloud client copying a card image while the emulator still has it open can produce a half-written file, so close the emulator before walking away from either machine. Manual copying is the fallback; its virtue is that nothing changes on the other machine until you decide it should. Whichever route you take: finish playing, close the emulator, let the sync complete, then pick up the other machine. Playing the same game on both in the gap is how conflict copies are born.
Gear That Makes Two-Machine Play Easier
Four pieces earn their place: a backup drive, a card, the handhelds themselves, and a hub for desk transfers.
Samsung T7 Portable SSD 1TB
The backup drive: a one-way, dated copy of every save folder, kept off the sync mesh, so a synced deletion can never reach it.
Specs:
- Capacity: 1TB
- Model: MU-PC1T0T/AM
- Interface: USB 3.2 Gen 2, USB-C
- Read speed: up to 1,050 MB/s
- Write speed: up to 1,000 MB/s
SanDisk 1TB Extreme microSDXC UHS-I Card
The card that lives in the handheld’s reader, holding the library and the emulator folders that sync against it.
Specs:
- Capacity: 1TB
- Model: SDSQXAV-1T00-GN6MA
- Format: microSDXC UHS-I, SD adapter included
- Read speed: up to 190 MB/s
- Write speed: up to 130 MB/s
Lenovo Legion Go S (Ryzen Z2 Go, 16GB, 512GB)
The handheld half for most readers: a Windows 11 machine running the same emulator builds as the desktop.
Specs:
- Processor: AMD Ryzen Z2 Go, 4 cores / 8 threads, up to 4.3GHz
- Memory: 16GB LPDDR5x-6400, soldered
- Storage: 512GB M.2 2242 SSD
- Display: 8-inch IPS, 1920×1200, 48-120Hz VRR
- Battery: 55.5Wh
- Card reader: microSD
Lenovo Legion Go 2 (Ryzen Z2 Extreme, 32GB, 2TB)
The flagship half: the same Windows emulator builds and a bigger OLED screen, with room for the full library on the device itself.
Specs:
- Processor: AMD Ryzen Z2 Extreme
- Memory: 32GB LPDDR5X, soldered
- Storage: 2TB SSD
- Display: 8.8-inch OLED, 1920×1200, up to 144Hz
- Battery: 74Wh
- Item model number: 83N0000AUS
Anker 341 USB-C Hub 7-in-1
For desk work: card slots and USB ports make the manual-copy fallback painless, and pass-through charging powers the handheld through long transfers.
Specs:
- Model: A8346
- Ports: 2 USB-A, 1 USB-C data, 1 USB-C PD, HDMI, SD and microSD slots
- HDMI output: 4K
- Pass-through charging: up to 100W input, up to 85W to the device
How to Choose
Choose how much automation you trust. Daily play on both machines earns folder sync its setup time: pair the folders, match the builds, keep the backup separate. Weekly switching suits a manual copy of the same folders, slower and safer because nothing propagates until you copy it. Cloud folders sit between the two, provided you close emulators before leaving a machine. Start with one emulator, prove the pair works, then add the rest.
Who Should Skip
Skip syncing entirely if you play on one machine only; a dated backup gives you the protection without the conflict risk. Skip save states in your sync pairs if you update emulators often or run different cores on each machine, because states are the layer most likely to arrive broken. And skip it if your library came from anywhere but your own discs and cartridges; this guide assumes games you dumped yourself.
FAQ
Should I sync save states or only in-game saves?
Sync in-game saves freely: battery saves and card images travel cleanly. Sync states too if both machines run the same build and core versions, but treat them as a convenience, not a record; a state made before an update may not load after it.
Why does my game show no save on the handheld after syncing?
Almost always a layout mismatch, not a lost file. Check that both copies use the same folder options: RetroArch’s sort-by-core setting, DuckStation’s card mode, Dolphin’s card image versus GCI folder mode, and which memstick PPSSPP calls active. The save is usually in the other subfolder.
What happens if I play the same game on both machines before syncing finishes?
You create a conflict: two versions of the same save, each newer in its own timeline. Sync tools keep one and park the other as a conflict copy, or overwrite by timestamp. Recover by loading the conflict copy, checking which progress is real, and saving in-game from it.
Final Verdict
Syncing emulator saves between a Windows PC and a Windows handheld is a folder problem wearing a tool problem’s clothes. The folders are knowable: RetroArch’s saves and states, PCSX2’s memcards, Dolphin’s GC and Wii folders, DuckStation’s memcards, PPSSPP’s SAVEDATA. Pair them, match builds and settings on both machines, respect the fragile layer, save states, and keep a one-way backup sync can never reach. Progress then follows you from desk to couch.











