Compatibility field guide

Know what can make a save differ.

A valid save file is not automatically compatible with every emulator. Keep your source until the destination game loads correctly.

RetroArch

RetroArch hardware saves commonly use `.srm`; save states are different and intentionally excluded. Core changes can change expected save size or naming. Confirm the same core and game revision, and close RetroArch before restoring so it does not overwrite the file on exit.

mGBA and VisualBoyAdvance

`.sav` battery saves are often portable, but flash/EEPROM type and size can differ for some games. Export through the emulator first when it provides a native export command.

DuckStation and PCSX2

Memory cards may be per-game or shared images. A `.mcr`, `.mc`, or `.raw` file can contain multiple saves, so replacing it can replace the whole card. The preflight names existing destinations; inspect replacements carefully.

Dolphin

GameCube `.gci` files are individual saves, while raw memory-card images hold multiple saves. Wii NAND saves are not included in v0.1. Use Dolphin’s own import/export tools for NAND content.

DeSmuME and melonDS

DeSmuME `.dsv` and general `.sav` files can differ in footer metadata and expected size. Prefer the emulator’s conversion/export option when moving between emulator families.

PPSSPP and folder saves

Some systems store a save as a directory with several files. v0.1 inventories recognised save files, not arbitrary directory packages; use the emulator’s documented whole-folder copy workflow for these.

If detection says “review”

The extension is recognised but the folder path did not identify a supported emulator. You can still bundle it. Before restore, compare the source and target emulator documentation, game region, revision, filename, and expected save size.