Back Up and Transfer Save Files Between Retro Handhelds

Updated 6 November 2026 · Standard formula, shown below

This guide shows you how to back up your save files from one retro handheld (like the Anbernic RG35XX, Miyoo Mini Plus, or PowKiddy) and transfer them to another. You’ll need a computer with a microSD card reader (or a USB cable if your handheld supports data transfer) and a way to read the card—most handhelds use a microSD card. The process works for save files from emulators like RetroArch, standalone emulators, and built-in game saves.

What You’ll Need

Your source handheld (the one with the saves)
Your target handheld (the one you want to transfer to)
A computer with a microSD card slot or a USB card reader
A microSD card (the one from the source handheld, or a spare for copying)
A USB cable if your handheld supports data transfer (some do, some don’t)
Optional: a card reader for the target handheld’s card if it’s different

Step-by-Step

Power off both handhelds. Never remove a microSD card while the device is on—you risk corrupting the save data.
Remove the microSD card from the source handheld. Most retro handhelds have a slot on the side or bottom. Use your fingernail or a small tool to gently push the card in until it clicks, then pull it out.
Insert the card into your computer. Use a microSD-to-SD adapter if needed. If your computer doesn’t have a card reader, use a USB card reader.
Locate the save files. Open the card’s root folder. Look for folders like saves, retroarch, .retroarch, sdcard, or roms. Save files are often in a subfolder like saves or savefiles. They usually have extensions like .srm, .sav, .state, or .rtc.
Copy the entire saves folder (or the specific save files) to your computer. Create a folder on your desktop called “Handheld Saves Backup� and paste the files there. This is your backup.
Eject the card safely from your computer (right-click and select “Eject� on Windows, or drag to Trash on Mac). Remove the card.
Prepare the target handheld. Power it off, remove its microSD card, and insert it into your computer.
Find the corresponding folder on the target card. The structure may differ. Look for the same folder names as step 4. If the target uses a different emulator frontend (e.g., RetroArch vs. a standalone emulator), the save location might be different.
Copy your backed-up save files into the target card’s save folder. Important: Keep the same folder structure. For example, if your source had saves/GameBoy/game.srm, copy it to saves/GameBoy/game.srm on the target. If the target has a different folder structure, you may need to create the same subfolders.
If the target uses a different emulator core or system, you may need to rename the save file. For example, a save from a Game Boy Advance emulator might be named game.srm, but the target’s emulator might expect game.sav. Check the target’s existing save files for naming conventions.
Eject the target card safely and insert it into the target handheld.
Power on the target handheld and test the game. If the save doesn’t appear, double-check the file path and naming.

Common Mistakes

Not backing up first. Always copy the saves to your computer before altering the target card. If something goes wrong, you still have the original.
Putting saves in the wrong folder. Many handhelds have multiple folders like saves, savefiles, or retroarch/saves. Putting a save in the wrong one means it won’t be recognized.
Ignoring file extensions. A save from one emulator might be .srm, while another uses .sav. If the target expects a different extension, rename it.
Copying the entire card instead of just saves. This can cause conflicts if the target has a different firmware or folder structure.
Removing the card without ejecting. This can corrupt the card and lose data.

Tips

Use a consistent folder structure. If you’re moving between two handhelds that both run RetroArch, copy the entire retroarch folder (or at least the saves subfolder) to preserve paths.
Check for save states vs. battery saves. Save states (usually .state) are snapshots of the emulator’s memory and are tied to the specific emulator core and version. They may not work if the target uses a different core. Battery saves (.srm or .sav) are more portable.
If the target uses a different firmware (e.g., GarlicOS vs. OnionOS), the save folder may be in a different location. Look for a saves folder in the root, or inside the retroarch folder.
Test with one game first. Transfer a single save, test it, and if it works, transfer the rest.
Keep a backup of your backup. Store the backup folder in two places (e.g., cloud storage and an external drive).

Troubleshooting

Save doesn’t appear in the game. Check the file name and extension. The game’s ROM file name must match the save file name (e.g., Pokemon.gba and Pokemon.srm). Also, verify the save is in the correct folder for the emulator you’re using.
Save appears but is corrupted or empty. This often happens when the save was created on a different emulator core. Try using a different save file (e.g., if you have both .srm and .state, use the .srm).
The target handheld doesn’t recognize the card. Ensure the card is formatted correctly (FAT32 is common for retro handhelds). If the card was from a different device, it might have a different file system. You may need to reformat it, but that will erase all data—so back up first.
I can’t find the saves folder. Some firmwares hide folders. Enable “show hidden files� on your computer. On Windows, go to File Explorer > View > Hidden items. On Mac, press Cmd+Shift+. (period).
The save transfer works but the game doesn’t load it. Some games have multiple save slots. Make sure you’re loading the correct slot in the game’s menu.

Frequently Asked Questions

Can I transfer saves between different emulator cores (e.g., from mGBA to VBA-M)?

Yes, usually, if the save is a battery save (SRAM). The file content is the same, but the extension may differ. Rename the file to match the target emulator’s expected extension.

Do save states transfer between different devices?

Sometimes, but they are less reliable. Save states are tied to the specific emulator core and its version. If the target uses a different core, the state may crash or be ignored. It’s safer to use in-game saves (battery saves).

What if my handheld doesn’t have a microSD card slot?

Most retro handhelds do have a microSD slot. If yours doesn’t, you may need to use a USB cable to connect to a computer and access the internal storage. The steps are the same, but you’ll copy from the internal drive.

Can I transfer saves wirelessly?

Some handhelds with Wi-Fi (like the Miyoo Mini Plus with OnionOS) support FTP or network transfer. You can use an FTP client on your computer to upload saves. Check your device’s documentation for details.

Will transferring saves work if the target handheld has a different operating system (e.g., from stock firmware to GarlicOS)?

Yes, as long as you place the saves in the correct folder for the new OS. The save file itself is not OS-specific; it’s the folder path that changes. Consult the new OS’s documentation for where saves are stored.

What if the save file is larger than the card’s free space?

That’s unlikely, as save files are usually a few kilobytes. But if you have many saves, ensure the target card has enough free space. If not, delete unnecessary files or use a larger card.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.