Migrate EmuDeck to a new SD card
Copy your EmuDeck folder to the new card, then point every emulator and shortcut at the new path so nothing opens to a missing directory.
Moving EmuDeck to a bigger card is not one copy operation. Three separate things reference the old location: the emulator folders themselves, the frontend’s ROM directory setting, and the Steam shortcuts that launch each emulator with an absolute path. Copy the files and skip the other two, and everything opens to an empty library.
What has to move together
| Piece | Where it lives | Breaks if you skip it |
|---|---|---|
| Emulator installs and configs | EmuDeck’s installation folder | Emulators start with default settings, or not at all |
| ROM library and saves | The folder you picked during setup | The frontend shows an empty list |
| Frontend ROM path | ES-DE’s settings | Games are there but invisible |
| Steam shortcuts | Steam ROM Manager’s parsed output | Old shortcuts point at the old card |
Do the move in order
-
Back up to a PC before touching either cardCopy the whole EmuDeck folder off the device. A second copy on a PC is what saves you when a card fails halfway through a transfer, which is also the moment people discover they had no backup.The backup on the PC opens and shows the same top-level folders.
-
Format the new card for the device it will live inSteam Deck formats removable cards as ext4, which Windows cannot read. If the card is moving to a Windows handheld instead, format it there — do not carry a SteamOS-formatted card across. Decide the target device first, then format.The new card mounts on the target device and accepts a test file.
-
Copy the folder, not the individual emulatorsKeep the same folder structure under the new location. Emulator configs reference paths relative to the EmuDeck root, so recreating the tree by hand with a different layout leaves broken references that look like random crashes.Directory depth and folder names match the backup.
-
Re-run EmuDeck so it rebuilds pathsRun the installer again and point it at the new location. This is what rewrites the emulator-side paths and shortcuts; copying files alone never does. Let it finish before opening any game.EmuDeck reports the new installation path without errors.
-
Reset the frontend ROM directoryIn ES-DE, open the settings and set the ROM directory to the new path. The frontend stores this as a single absolute path, so it does not follow the files on its own.ES-DE lists your systems with game counts, not zero.
-
Regenerate the Steam shortcutsRun Steam ROM Manager again and re-parse. Old shortcuts carry the old card's absolute path in their launch options, so they will keep failing even after the files moved.A game launched from a fresh shortcut opens from the new card.
The two failures people hit most
Everything is empty after the copy. The files moved but the frontend still points at the old path — redo step 5. Nothing is lost.
Shortcuts open then close instantly. The launch command still references the old mount point. Regenerating shortcuts fixes it; editing them by hand one at a time does not.
Related
Card not recognised at all rather than migrated? That is Steam Deck microSD not detected. Tuning the emulators after the move is covered in Steam Deck emulation settings, and the Windows handheld route is in ROG Ally emulation setup. If the new setup is missing BIOS files, start from EmuDeck BIOS requirements.