How to Move Retro Saves Between Devices Without Losing Progress

Moving retro saves between devices sounds simple until you try to do it in a hurry.

The save might be in the emulator folder. Or the app data folder. Or next to the ROM. Or named differently than you expected. A save state might only work with one emulator version. A ROM hack save might depend on the exact patched file.

That is why save migration is one of the most common ways retro progress gets lost.

Rebit does not change the old games, but it gives your legally owned library and save workflow a cleaner place to live. Start with cross-device retro gaming for the product overview, or cloud saves for retro games for save-safety habits.

First: know what kind of save you have

There are two major save types:

In-game saves are the saves the original game expects. These are often battery saves, memory-card-style saves, or system-specific save files.

Save states are emulator snapshots. They preserve an exact moment: position, memory, timing, and game state.

Both are useful, but they do not behave the same way.

In-game saves usually move more cleanly between setups. Save states are more fragile because they can depend on emulator core, version, game file, and timing.

For a focused explanation of why those two layers behave differently, read save states vs in-game saves.

The safest migration order

If you are moving progress between devices, use this order:

1. Make a normal in-game save.
2. Close the game cleanly if your emulator requires it.
3. Copy the in-game save file.
4. Copy save states only as extra backup.
5. Keep the original files until the new device has been tested.
6. Open the game on the new device.
7. Load the in-game save first.
8. Create a new save state on the new device.

Do not delete the old files until you have confirmed the new setup works.

Why save states can fail

Save states are powerful, but they are not universal save files.

They can break when:

• the emulator core changes
• the emulator version changes
• the ROM file differs
• the ROM hack version changes
• the file name or folder structure changes
• the state was created during an unstable moment

That is why long campaigns should not rely on save states alone.

Use states for convenience and recovery. Use in-game saves as the foundation.

ROM hacks need extra care

ROM hacks make save migration more delicate.

A patched game might require a specific base ROM revision. A newer patch version might change maps, scripts, encounters, or save compatibility. If you move only a save file without tracking the patched game version, you can end up with progress that technically exists but no longer works correctly.

Use this routine:

1. Keep the clean original dump separate.
2. Keep the patched output named clearly.
3. Note the hack version.
4. Test the first in-game save before a long run.
5. Keep backup states before updating the patched file.

For Pokémon hacks, read how to play Pokémon ROM hacks online legally and best Pokémon ROM hacks to play in browser.

Cross-device play is easier with a library

Manual save movement can work if you are disciplined, but it gets messy as your library grows.

A browser library helps because the game and save workflow are organized around your account instead of one device. That is the point of Rebit’s upload ROM and play online flow.

Once a legally owned game is in your private library, you can build a more repeatable routine:

• launch from the browser
• make the first in-game save
• create a manual state before risky progress
• return later from your account
• keep long campaigns easier to reason about

A practical device-switch checklist

Before switching devices:

1. Save inside the game.
2. Create a manual save state.
3. Stop at a clean point, not mid-transition.
4. Confirm the game file name and version.
5. Keep a backup of the original save.

After switching devices:

1. Launch the game.
2. Load the in-game save first.
3. Confirm your progress.
4. Create a fresh state on the new device.
5. Continue only after the save looks correct.

Which games need the most care?

Be extra careful with:

• RPGs
• ROM hacks
• tactical games
• long PS1 campaigns
• games with memory-card-style saves
• challenge runs
• games where one mistake costs a long replay

Short arcade games usually need less save management. Long campaigns need more.

Do not wait until something breaks

The worst time to learn where your saves live is after progress disappears.

Set the habit early:

• save in-game
• reload once
• create a manual state
• keep backups before major progress
• avoid overwriting the only good state

Retro games were not designed around modern device switching. A careful save workflow closes that gap.