Where Does Flycast Store Saves and Config?
Flycast splits emu.cfg config from VMU save data. The standalone paths on Linux, macOS, and Windows.
Last updated
Standalone Flycast uses two directories. Config (emu.cfg plus controller mappings) lives in the config dir, while BIOS files, VMU saves, and save states live in the data dir. The in app file browser shows both roots when you set content and home paths.
On Linux those are ~/.config/flycast and ~/.local/share/flycast, with legacy ~/.reicast honored when present. macOS defaults to ~/Library/Application Support/Flycast. Windows runs from the data folder beside the exe. VMU files look like vmu_save_A1.bin.
Where Flycast stores this, by platform
~/.config/flycast
emu.cfg and mappings here; VMU saves and states under ~/.local/share/flycast. Legacy ~/.reicast paths win if they exist. Flatpak installs sandbox both under ~/.var/app/org.flycast.Flycast.
~/Library/Application Support/Flycast
Default modern location; old installs may still use ~/.flycast, which Flycast prefers when found. VMU saves sit in the data side next to emu.cfg.
.\data
Folder beside flycast.exe holding BIOS files, VMU saves, and states. Launching from a frontend with a different working directory confuses this, so wrap it in a batch file that cds first if saves vanish.
Frequently asked questions
where are flycast vmu saves
In the data directory as vmu_save_A1.bin through D1 plus dc_nvmem.bin. Enable per game VMUs to split one set per title instead of sharing four files across the library.
flycast or retroarch core, where do saves go
Different spots. Standalone uses the folders above. The libretro core writes vmu_save files into RetroArch system/dc instead. Mixing the two without copying files explains most missing save reports.
Notice an outdated path? Let us know.