N64 Save Converter
Open an N64 save and download it for the emulator or device you use. EEPROM (.eep), SRAM (.sra), FlashRAM (.fla) and Controller Pak (.mpk) saves go into or come out of RetroArch's single .srm. SRAM and FlashRAM can be byte-swapped for an EverDrive 64, and paks converted to and from DexDrive .n64.
Or drop them here. They are read on this device and never uploaded.
Which N64 save formats does it convert?
An N64 cartridge saves to one chip: EEPROM, SRAM or FlashRAM. Some games save to a Controller Pak instead. RetroArch keeps all of them in one .srm file.
| Format | Files | Used by |
|---|---|---|
| EEPROM | .eep (512 B or 2 KB) | Project64, Mupen64Plus, EverDrive 64 |
| SRAM | .sra (32 KB) | Project64 and Mupen64Plus (word-swapped), EverDrive 64 (big-endian) |
| FlashRAM | .fla (128 KB) | Project64 and Mupen64Plus (word-swapped), EverDrive 64 (big-endian) |
| Controller Pak | .mpk (32 KB) | Project64, Mupen64Plus, EverDrive 64 |
| RetroArch save | .srm (290 KB) | RetroArch Mupen64Plus-Next and ParaLLEl N64 |
| DexDrive pak | .n64 | InterAct DexDrive, older save sites |
How to convert an N64 save
Open your save
Drop the .eep, .sra, .fla, .mpk, .srm or .n64 file. If it is an .sra or .fla, say whether it came from an emulator or from an EverDrive 64 or cartridge dump.
Check what was found
The converter names the format it found and lists the saves inside, with any problem it spotted in the file.
Pick the format you need
Press the button for the emulator or device you are moving the save to. The new file downloads straight away.
Copy it into place
Put the downloaded file where your emulator or device keeps its saves, using the name the game expects.
Why do EverDrive 64 saves need a byte swap?
Project64 and Mupen64Plus store SRAM and FlashRAM with the bytes of each 4-byte word reversed, because they keep it the way the emulated memory is laid out. An EverDrive 64 and a cartridge dump keep the console's own big-endian order. EEPROM and Controller Pak saves are the same everywhere.
The converter swaps SRAM and FlashRAM when you pick an EverDrive output, and swaps them back when you open an EverDrive file. Its checks compare the result with savefileconverter.com's output on real F-Zero X and Pokemon Snap saves.
What is inside a RetroArch N64 .srm?
RetroArch's Mupen64Plus-Next and ParaLLEl cores write one 290 KB file: 2 KB of EEPROM at the start, four 32 KB Controller Paks, 32 KB of SRAM and 128 KB of FlashRAM. A game uses one or two of those parts. Unused parts are blank, and empty paks are formatted.
Other save converters
- PS1 Save Converter: Memory cards (.mcr, .mcd, .srm), PSP and Vita .VMP, DexDrive .gme, PS3 .PSV and single saves.
- PS2 Save Converter: PCSX2 .ps2 cards, EMS .psu, Action Replay .max, CodeBreaker .cbs and PS3 .PSV.
- GBA Save Converter: Raw .sav, RetroArch .srm, GameShark .sps and .gsv, Action Replay .xps, with resizing.
- DS Save Converter: Raw .sav, DeSmuME .dsv and Action Replay .duc / .dss, with trimming and padding.
- GameCube Save Converter: Single .gci, GameShark .gcs and MaxDrive .sav saves, and whole Dolphin .raw cards.
- Game Boy Save Converter: GB and GBC .sav and .srm, with the MBC3 real-time clock carried across.
- SNES Save Converter: .srm and .sav for emulators and flash carts, Retron 5 saves, resizing.
- Genesis Save Converter: Gens and Kega Fusion, RetroArch Genesis Plus GX, Retrode, MiSTer and MegaSD saves.
- Saturn Save Converter: Mednafen .bkr and .bcr, Beetle Saturn, Yabause and plain memory images, plus single .BUP saves.
- Dreamcast Save Converter: VMU images, Nexus .DCI saves and .VMS with .VMI pairs.
Frequently asked questions
Does a Project64 save work in RetroArch?
Yes. Open the .eep, .sra, .fla or .mpk and press RetroArch .srm. Project64 and RetroArch store the data the same way, so it only needs placing at the right offset.
How to tell a 4 Kbit .eep from a 16 Kbit one
The size tells you: 512 bytes is 4 Kbit and 2 KB is 16 Kbit. When reading a RetroArch .srm, the converter picks the size from where the data ends.
Does it read the notes on a Controller Pak?
Yes. The list shows each note's name, and the pak's ID and page-table checksums are checked. The pak itself is copied byte for byte.