Where Does Mupen64Plus Store Saves and Config?
Mupen64Plus splits config, SRAM, and states across XDG folders. The Linux, Windows, and macOS layout.
Last updated
Mupen64Plus keeps config in the config home and saves in the data home. On Linux that is ~/.config/mupen64plus/mupen64plus.cfg plus ~/.local/share/mupen64plus/save holding SRAM files (.sra, .eep, .fla) and numbered states. Both save dirs are settable via SaveStatePath and SaveSRAMPath.
Windows uses %APPDATA%\Mupen64Plus with screenshot and save subfolders. macOS uses ~/Library/Application Support/Mupen64plus. Frontend builds like RetroPie override the paths in their own configs, so the in app paths win over these defaults when they disagree.
Where Mupen64Plus stores this, by platform
~/.local/share/mupen64plus/save
SRAM and states together here by default. Config at ~/.config/mupen64plus/mupen64plus.cfg. RetroPie edits SaveStatePath and SaveSRAMPath to point at the ROMs folder instead.
%APPDATA%\Mupen64Plus\save
Same save subfolder pattern under Roaming. Config beside it. Filenames track the ROM name, so renaming ROMs orphans saves.
~/Library/Application Support/Mupen64plus/save
Same layout in Application Support. Note the lowercase p in Mupen64plus on Mac versus Mupen64Plus elsewhere when scripting paths.
Frequently asked questions
mupen64plus srm vs eep vs state files
SRAM style files (.sra, .eep, .fla) are the cart save and transfer between setups. States are full machine snapshots tied to the build. Keep in game saves for real progress; states for retries.
retropie moved my mupen saves to the roms folder, why
Its config sets SaveStatePath and SaveSRAMPath to the ROMs directory. That is intentional for that frontend. Standalone builds default to the data home above unless you set the same keys.
Notice an outdated path? Let us know.