Troubleshooting guide

EmuDeck Migrate Saves: When a Save Exists but the Emulator Loads an Empty Slot

Category: Handheld Emulation

You are in Gaming Mode on your Steam Deck, EmuDeck is set up with your own ROMs, and you have reached the saves do not migrate step: a save file clearly exists in the old location, yet the emulator opens with an empty slot.

Confirm the save file and expected path

First, verify the save exists and note its exact filename and folder. In Desktop Mode, open the file manager and navigate to the emulator’s save directory under EmuDeck. Check that the file is not zero bytes and that its extension matches the emulator’s expected format. If the file is present but the emulator shows an empty slot, the emulator is likely reading a different path than the one you inspected.

Check where the emulator actually reads saves

Launch the emulator directly in Desktop Mode, not through Gaming Mode. Open its settings and locate the configured save directory. Compare that path character by character with the folder containing your save. A common cause is a mismatch between the portable and standard save folders, or a per-game save subfolder the emulator expects but does not find. If the paths differ, that explains why emudeck migrate saves appears to fail: the migration may have completed, but the emulator is pointed elsewhere.

Verification test

Copy the save into the path the emulator reports, then launch the same game and load the slot. If the save appears, the original location was wrong. Remove the copy afterward to avoid duplicates.

Rollback note

Before changing paths, back up the save folder. If the emulator still shows an empty slot, restore the backup and

Steam ROM Manager parser preview on a Steam Deck

Ask for help with both paths and the filename.


Back to the service page · Ask about this exact symptom