WindowsLinuxAndroid

Where Does ePSXe Store Memory Cards and Save States?

ePSXe keeps memory cards in memcards and states in sstates. The desktop layout plus the Android base folder.

Last updated

ePSXe stores PlayStation memory cards as files in its memcards folder, one per slot, selectable in the GUI. In game saves write there the way a real card worked. Save states (F1 to save, F3 to load, F2 for slot) land separately in sstates, about 1.5 MB each compressed.

On desktop both folders sit beside the emulator files. Android builds use an ePSXe base folder you pick under scoped storage, holding memcards, sstates, cheats, patches, bios, and isos together. Loading a state swaps in temp cards, so recover temp.000 and temp.001 from the memcards dir before loading another state.

Where ePSXe stores this, by platform

Windows
.\memcards

Beside the exe with sstates next door. Point the GUI at chosen card files per slot. After a state load, rename temp.000/temp.001 out before they get overwritten.

Linux
./memcards

Same side by side layout as Windows. Cards convert from VGS, Bleem, and other formats through the GUI. States are version tied; cards carry forward.

Android
/storage/emulated/0/epsxe/memcards

Shared storage base folder you select on Android 11 and up, or private app storage that vanishes on uninstall. Keep the shared folder for migratable saves and BIOS scanning.

Frequently asked questions

epsxe save state loaded but memory card is old, why

By design ePSXe restores state cards as temp.000 and temp.001 instead of overwriting your configured cards. Copy those out of memcards and point the GUI at them to keep post state progress.

where are epsxe android saves after the scoped storage change

In the ePSXe base folder you picked, under memcards and sstates. Pick the old epsxe folder to inherit previous saves. Private app storage works but deletes with the app and hides from file managers.

Notice an outdated path? Let us know.