✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is Samsung T7 Portable SSD 1TB, with SanDisk 1TB Extreme microSDXC as a strong alternative.

Every emulator writes your progress to a file, but the format of that file decides whether your progress can follow you to a different emulator or a new device. Some save files are plain copies of what the original cartridge or memory card held, and they move almost anywhere. Others carry headers one program expects and another rejects, or are encrypted to a single console.

As an Amazon Associate, we earn from qualifying purchases.

This guide is about the save files themselves: the three families they fall into, what the extensions mean, and what converting between emulators involves. It is not about save states, which are version-locked snapshots of a running machine, and it is not about syncing, which moves files between devices without changing what they are.

This article contains affiliate links, and we may earn a commission when you buy through them at no extra cost to you.

Quick Answer

Most cartridge-era saves move freely: a battery save is a raw copy of the cartridge’s save memory, so renaming a .sav to .srm usually carries it between emulators. Memory card images move when both sides read the same card format. Console-side saves are the exception — PSP saves travel as folders, while 3DS saves are encrypted to your own console and only move through it.

The Three Families at a Glance

Nearly every save file belongs to one of three families, and the family predicts how portable it is.

Family Typical files What it mirrors Moves between emulators?
Battery save .srm, .sav The cartridge’s save chip Usually yes, rename and check size
Memory card image .mcd, .mcr, .gme, .ps2, .raw A whole memory card Yes, if formats match or an editor imports
Console-side save SAVEDATA folders, encrypted 3DS data The console’s own storage PSP yes; 3DS only through your own console

The pattern underneath is simple: the closer a format stays to what the original hardware wrote, the more portable it is. Trouble starts when an emulator adds a wrapper, or the console encrypted the data.

Battery Saves: A Copy of the Cartridge’s Own Memory

Cartridge games saved to a small memory chip on the board — battery-backed SRAM, EEPROM or flash, depending on the system and era. Emulators dump that chip’s contents to a file, and because the contents belong to the game rather than the emulator, the file is close to universal for that system.

The main split is naming. Standalone emulators such as mGBA and VBA-M write .sav files, while RetroArch standardises on .srm for every core, stored in its saves folder and named to match the game file exactly. Moving between the two is normally a rename: match the base name, change the extension, and the new emulator reads the same bytes.

Two quirks cause most failures. The first is size: cartridges shipped with different save capacities, so a valid file might be 32KB, 64KB or 128KB, and some emulators pad a smaller save out while stricter ones reject a file whose size does not match the game’s save type. The second is extra data: clock-equipped games such as the Pokemon titles on GBA append real-time-clock information past the end of the save in some emulators, which can trip up a stricter reader.

Memory Card Images: One File Holding Many Saves

Disc-era consoles replaced the cartridge chip with a removable card, and emulators reproduce the card as a single image file holding every game’s saves at once. Portability depends on whether two emulators agree on the card’s layout.

On PlayStation, the card is a 128KB image divided into blocks. ePSXe and Mednafen-style cores use .mcr, DuckStation writes .mcd as its native format, and .gme files from the old DexDrive hardware carry the same card data behind an extra header. DuckStation ships a Memory Card Editor that opens these formats and copies individual saves between cards — the clean way to convert. Inside RetroArch, the Beetle PSX core stores the card as an .srm whose contents are the same raw card image, so renaming between .mcr and .srm works too.

PlayStation 2 follows the same idea at a bigger scale: PCSX2 keeps 8MB cards as .ps2 image files, or as folder memory cards that store each game’s saves in its own directory, making single-game backups easier. GameCube in Dolphin uses a .raw card image named for its region, or a GCI folder mode that keeps each game’s save as a separate .gci file, which Dolphin’s built-in memory card manager imports and exports individually. Raw images carry the card’s serial number, which a few copy-protected saves check, so moving saves one by one as .gci files is usually cleaner.

Console-Side Saves: Folders, Then Encryption

Later handhelds stopped treating the save as part of the game and started treating it as part of the console’s storage, and portability changes completely.

The PSP is the friendly case. PPSSPP recreates the Memory Stick folder structure, with each game’s saves in a folder named by game ID under PSP/SAVEDATA — the same layout a real PSP writes. Copying that folder between PPSSPP and an actual PSP works in both directions, because both sides read the console’s own format. The one trap is regional: different regions of the same game use different IDs and keep separate, incompatible saves.

The 3DS is the hard case, and the one that teaches the rule. Digital 3DS games store their saves in a packed, encrypted format inside the Nintendo 3DS folder on the SD card, encrypted with a key unique to your console, held in its movable.sed. A save copied from someone else’s console is unreadable data on yours, and Azahar’s documentation is built around the same fact: the emulator needs system files from your own 3DS, and the practical route to your saves is exporting them in decrypted form on the console itself, with a homebrew save manager such as Checkpoint. The lesson stands: on modern systems the save belongs to the console, not to the game file.

Will My Save Move?

Reduce any migration to these checks:

  • Same system, battery save: yes, almost always. Rename the extension, match the file name to the game, and confirm the size matches the game’s save type.
  • Same system, memory card: yes if both emulators read the same raw card layout, or after a pass through the destination’s card editor or manager.
  • Standalone to RetroArch, or back: yes for cartridge saves and PS1 cards. Expect to rename and to check sizes.
  • Console-side saves: PSP folders move as folders. 3DS saves move only through the console that created them.
  • Save states: no. States are internal snapshots tied to one emulator and often one version — the in-game save is the layer worth converting.

Storage That Keeps Save Files Safe

Save files are tiny — a whole library fits in megabytes — but they are irreplaceable in a way game files are not: you can always re-dump a cartridge, and you cannot re-play two hundred hours. Keep a working copy where you play, plus dated backups somewhere else.

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Check price on Amazon

  • Capacity: 1TB
  • Model: MU-PC1T0T/AM
  • Interface: USB-C, USB 3.2 Gen 2
  • Type: Portable solid state drive

The natural home for a full emulation library on a PC: games, BIOS files from your own consoles and the save folders live on one fast drive, so one backup routine protects everything at once. See it on Amazon

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

Check price on Amazon

  • Capacity: 1TB
  • Model: SDSQXAV-1T00-GN6MA
  • Format: microSDXC, UHS-I

Handheld libraries live on cards like this, and the save files ride along with the games. Moving the card between two devices running the same emulator is often the simplest migration of all — no conversion, because nothing about the files changes. See it on Amazon

WD My Passport Portable Hard Drive

WD My Passport Portable Hard Drive

WD My Passport Portable Hard Drive

Check price on Amazon

  • Type: Portable external hard drive
  • Interface: USB
  • Capacity: not stated

A cold archive for dated snapshots of your save folders. Keep one copy of every save you care about here, refreshed whenever you finish a long game, and a corrupted card or bad conversion can never cost more than the time since the last snapshot. See it on Amazon

Samsung BAR Plus Flash Drive 256GB

Samsung BAR Plus Flash Drive 256GB

Samsung BAR Plus Flash Drive 256GB

Check price on Amazon

  • Capacity: 256GB
  • Model: MUF-256BE4/AM
  • Read speed: up to 400 MB/s, as stated by the maker
  • Write speed: not stated

The sneakernet option: a pocketable stick for carrying a saves folder from a desktop to a handheld and back. Save files are so small the transfer is effectively instant, and the metal body survives the bag or keyring it lives on. See it on Amazon

Lenovo Legion Go S

Lenovo Legion Go S

Lenovo Legion Go S

Check price on Amazon

  • Processor: AMD Ryzen Z2 Go
  • Memory: 16GB LPDDR5x
  • Storage: 512GB SSD
  • Display: 8-inch, 1920×1200
  • Operating system: Windows 11

A full Windows handheld is where conversions happen: RetroArch and the standalone emulators sit side by side on the internal SSD, card editors are a right-click away, in the verified Z2 Go Windows configuration listed here. See it on Amazon

How to Choose

Start from the family your favourite systems belong to. Cartridge-based libraries are already portable; what they need is naming discipline and one backup copy. On memory-card systems, prioritise an emulator with a good built-in card editor and keep cards in the rawest format available, because raw images are what other tools read. On PSP or 3DS, accept that the console is part of the format: budget effort for exporting saves on the hardware itself, and store the exported results, not the raw encrypted folders. Back up in-game saves separately from save states, and date the folders so a bad experiment can be rolled back.

Who Should Skip

Skip this topic if you only ever play with save states — states do not convert, and no storage setup changes that. Skip it if you use exactly one emulator on one device and never plan to move: your saves are already where they need to be. And skip it for current-generation console saves, which live inside closed platform accounts.

FAQ

Can I rename a .sav file to .srm and use it in RetroArch?

Usually, yes. Both extensions hold the cartridge’s raw save memory, so rename the file to match your game file’s name exactly, place it in RetroArch’s saves folder, and load the game. If the save appears empty, check its size against the game’s save type before assuming the rename failed.

Why does my moved save show up as empty or corrupted?

The three usual causes are a size mismatch, where the destination expected a different save capacity; a name mismatch, where the save does not match the game file’s name; and a region mismatch, where the save belongs to a different regional release. Work through them in that order, and always test with a copy, never your only file.

Are save states convertible between emulators?

No. A save state is a dump of one emulator’s internal machine state, tied to that emulator and frequently to its exact version. Nothing converts them. That is why every workflow here starts from the game’s own in-game save.

Can I use my 3DS saves in Azahar without my 3DS?

No. Digital 3DS saves are encrypted with a key unique to the console that made them, so no file copied from elsewhere can be read. The supported route is to export the saves in decrypted form on your own 3DS first, then bring those exports to the emulator.

Final Verdict

Save portability is decided by how faithfully a format mirrors the original hardware. Battery saves are the cartridge’s own memory and travel with a rename; memory card images travel when both sides respect the same raw layout, with built-in card editors smoothing the rest; console-side saves travel only on the console’s terms — open folders on PSP, console-bound encryption on 3DS. Learn which family your library belongs to, keep in-game saves backed up and dated, and no emulator switch will cost you your progress.

Explore Our Guides & Free Tools