PlayStation games saved on tiny physical cards; emulators keep that same system inside card files, and this guide explains how they work alongside emulator save states.

The original PlayStation and PS2 libraries grew around removable memory cards, not internal saves. Each card stored a limited number of blocks, games picked their own format, and players carried one card from home to friend houses. Emulators reproduce that behavior faithfully with small files on disk, which sounds obscure until you start an RPG and want your progress back the next evening. The good news: modern programs handle cards automatically, and understanding a few folder names prevents lost hours of play.

How PS1 saves actually worked on real hardware

A PS1 memory card held roughly 128 blocks total, and each save used one block or many depending on the game. Games wrote a save the moment you chose a memory-card slot in their own menus; there was no universal system menu on the console. If the game slot ended up full, old saves had to be deleted from the PlayStation BIOS screen before a new one could write. Emulators model this exactly, including the BIOS memory-card viewer, so habit learned in software carries over to physical games if you ever pick up a used console.

Memory card files inside DuckStation

DuckStation stores cards under its memory cards folder, usually named MemoryCardA.mcd and MemoryCardB.mcd for slots one and two. First launch creates blank cards, and most players never need another file. In Settings, Controllers, and the memory card manager you can swap slots, copy individual saves, and erase blocks. To keep separate profiles for different players or regions, duplicate a blank card file in Windows Explorer, rename it clearly, and assign it from the card manager before booting a game. Fresh cards size up the moment a game writes its first save, so a zero-byte-looking file at rest is normal rather than broken. Pair these steps with the DuckStation setup walkthrough for BIOS, graphics, and audio defaults.

Memory cards in ePSXe

ePSXe follows the same two-slot idea with files such as memcard0.mcr and memcard1.mcr kept in the emulator’s memcards folder. The memory manager on the options screen lists blocks, names, and sizes; format a new card from that menu if a save fails to appear. Old save files imported from other tools use the common .mcr format, so a downloaded legal backup of your own existing data can be dropped into the folder and selected in slots. Keep BIOS and card files inside the program directory when running ePSXe from a portable USB stick; path trouble is the usual cause of a missing-save warning after a copy to another PC.

Save states versus memory card saves

Both methods live side by side, and they are not interchangeable. A memory-card save writes through the game’s own logic, so it works across emulator versions, cores, and even hardware. An emulator save state freezes the exact frame, graphics mix, and RAM contents; it refuses to load cleanly after a core update, a different region disc, or a cheat toggle changed mid-run. Rule of thumb: finish the night with an in-game card save whenever the campaign lets you. Use states around tough boss fights, puzzle rooms, or a run you need to interrupt in seconds, then return to card saves for long-term progress. Our save-states basics guide explains this tradeoff in detail.

Common card problems and fixes

• Save option greyed out: the card in slot A may be missing or unformatted; open the card manager and assign a file to that slot.
• Card full after a few RPGs: PS1 blocks were tiny, so copy wanted saves to a second card file, then clear the first; most games also support two-player cards in slot B.
• Save vanished after moving folders: the emulator kept pointing at an old path; reselect the card file in settings and run a test save.
• Corrupted save warning: try loading from a second card copy kept as backup; never overwrite a card until the new one saves successfully once.

What to play once the saves hold up

With cards and states working, long titles finally feel safe to start. JRPGs such as Final Fantasy VII, VIII, and IX, tactical epics like Suikoden II and Vagrant Story, and slow-burn adventures like Metal Gear Solid lean on multi-session saves, which is exactly the workflow cards support. Fast arcade titles can live on states alone. For a curated starting list, the ten classics in our PS1 essentials feature cover RPG, shooter, and platformer moods without touching the grey-area dump debate; stick to your own discs, homebrew releases, and public-domain files when building the folder.