Losing hours of game progress because of a corrupted save is frustrating, especially when an emulator suddenly stops recognising a file that worked perfectly the previous day. On a Mac, this can happen after an unexpected shutdown, an interrupted save, a software update or a problem with cloud synchronisation. Fortunately, a missing or unreadable save does not always mean your progress has disappeared permanently. RetroArch, Dolphin and PCSX2 store game data differently, but each offers ways to locate existing saves, restore backups and investigate compatibility problems. This guide explains how to recover corrupted game saves on macOS in 2026, including practical instructions for Apple Silicon and Intel Macs, without requiring advanced technical knowledge.
Game saves can become corrupted when an emulator cannot finish writing information to storage. This may happen if your Mac shuts down unexpectedly, the emulator crashes or a game is closed while its saving indicator is still active. Interrupted writing can leave a file incomplete, preventing the game from reading its contents. Low available storage, external drive disconnections and file permission problems can cause similar symptoms. However, not every loading error indicates genuine corruption. Sometimes the original data remains intact, but the emulator is looking in the wrong directory or attempting to open a file created with incompatible settings.
Understanding the difference between normal game saves and save states is essential before attempting recovery. In-game saves are created through a game’s own saving system and generally store progress in virtual memory cards, cartridge memory or other game-specific files. Save states are snapshots of the emulated system at a particular moment, including information about the running game. They are convenient for returning to an exact point, but often depend on the emulator version and its internal configuration. A save state that fails after an update may therefore be incompatible rather than physically damaged, while the game’s ordinary save may still work correctly.
Cloud storage can introduce another complication. If emulator files are stored in a synchronised folder, a conflict between two Macs or an incomplete upload might replace newer progress with an older copy. RetroArch also offers cloud synchronisation in supported configurations, making it important to understand which saves are being transferred. Before making changes, close the emulator completely and copy the affected files to a separate folder outside any synchronised location. Never experiment directly on your only copy. A backup created before troubleshooting preserves the original data and allows you to reverse unsuccessful attempts.
Finder is the simplest starting point for finding saved games on macOS. Open Finder, select Go from the menu bar and choose Go to Folder, or press Command + Shift + G. You can then enter a directory path without manually browsing hidden Library folders. For RetroArch, the safest approach is to open the application and check Settings > Directory, where the Save Files and Save States locations are displayed. Depending on the installation and configuration, these might be inside RetroArch’s application data directory, alongside the game files or in folders selected manually. Record both paths because ordinary saves and save states may be stored separately.
Dolphin normally keeps its user data in ~/Library/Application Support/Dolphin on macOS. Its GC directory contains GameCube memory card information, the Wii directory holds emulated Wii system data and StateSaves contains emulator snapshots. Dolphin also provides a command for opening its active user folder directly, which is particularly useful if a custom location has been configured. PCSX2 normally uses ~/Library/Application Support/PCSX2, with memcards for PlayStation 2 memory cards and sstates for save states. These are default locations rather than guarantees: portable installations and customised directory settings can change where information is stored.
Once you find the correct folder, duplicate the affected save files and keep the copies somewhere clearly labelled, such as Documents/Emulator Save Backups. Include the emulator name, game title and backup date in the folder name. Check whether the original file has a reasonable size and whether older copies exist. A zero-byte file is a warning sign because it contains no useful saved data, although normal file sizes vary between systems. You can also inspect older versions through Time Machine if your Mac was backed up before the problem occurred. Keep any recoverable files untouched until you have confirmed that the game can load them successfully.
RetroArch supports many console systems through separate emulator cores, so recovery depends partly on which core created the save. Start by opening Settings > Directory and checking the Save Files and Save States paths. Look for files matching the game name, including common extensions such as .srm for cartridge-style saves and .state or numbered .state files for snapshots. Some cores use different extensions or create additional folders. If the save exists but RetroArch does not recognise it, check whether the game filename has changed, whether the same core is selected and whether save sorting by core or content directory has been enabled.
If you have an older RetroArch backup, copy it into the relevant save directory while the emulator is closed, after preserving the current file under another name. Start the same game with the appropriate core and use its normal in-game Continue or Load option. For a save state, select the correct state slot through the Quick Menu before trying to load it. Avoid repeatedly saving over a damaged state, as this may eliminate an otherwise usable earlier copy. If the problem appeared immediately after a core update, an older compatible core version may help with an existing state, although compatibility is not guaranteed. Ordinary cartridge saves are generally more transferable between compatible cores than emulator snapshots.
Dolphin requires a different approach because GameCube and Wii games use distinct saving systems. GameCube progress may be stored in memory card images or individual GCI files, depending on the memory card configuration. Wii games usually store their progress inside Dolphin’s emulated Wii storage rather than as ordinary GameCube memory card files. First establish which system the affected game belongs to, then verify that Dolphin is using the same user directory as before. If you recently reinstalled the application or switched between installations, your original saves may still exist in another Dolphin directory rather than having been deleted.
For a GameCube game, open Dolphin’s memory card management tools and inspect the relevant card or GCI folder. When using a memory card image, Dolphin’s Memory Card Manager can display the individual game saves stored inside it and provides import and export functions. If a backup of the card exists, work with a duplicate and check whether its contents are readable. Where individual GCI backups are available, import the appropriate game save into a compatible memory card instead of replacing unrelated data. Make sure the card is assigned to the correct controller slot and that the game’s regional version matches the save. A European save, for example, may not be recognised by a North American release.
For Wii games, Dolphin can export and import supported save data through its Wii save management functions. An existing exported save can provide a straightforward recovery route when the current emulated Wii storage is damaged. Preserve the complete Wii folder before importing anything, since it contains more than one game’s data. Some Wii titles impose restrictions on save transfers, and importing a save does not guarantee that every game will accept it. If you have a Time Machine copy of Dolphin’s Wii directory from before the failure, restore it to a separate location first. You can then compare the backup with the current folder without immediately overwriting the entire emulated Wii system.
Dolphin save states should be handled separately from memory card and Wii saves. They are particularly sensitive to emulator changes and are not intended as a permanent replacement for saving through the game itself. If an older snapshot refuses to load, check whether it was created in a different Dolphin release and whether an earlier installation is still available. Test any older version using copies of your files, not your active save directory. A failed state does not necessarily affect progress already written to a memory card. Once normal saves are loading again, create a fresh in-game save and back it up before continuing.

PCSX2 emulates the PlayStation 2’s memory card system, making virtual memory cards the first place to investigate when progress disappears. On macOS, the standard directory is ~/Library/Application Support/PCSX2/memcards, although the active location can be changed through the emulator’s folder settings. Look for existing memory card files, commonly using the .ps2 extension, or folders if folder-based memory cards have been configured. Do not create or format a replacement card before checking the originals. A game reporting that no save exists could simply mean that the wrong memory card is inserted, the card is assigned to another slot or a different game region is being used.
PCSX2’s memory card management settings allow users to inspect and manage their available cards. Begin by confirming that the correct card is enabled in the intended slot. If the card is recognised, launch the game normally and attempt to load progress from its own menu. You can also start the PS2 system interface through PCSX2 and inspect memory card contents using the console’s browser. If the save appears there but not inside the game, investigate regional compatibility or game-specific restrictions. If the entire card is unreadable, replace it only with a verified backup after copying the existing file elsewhere. Formatting the damaged card would destroy information that might otherwise remain recoverable.
PCSX2 also stores emulator save states, normally in its sstates directory. These files depend on the game and the emulator’s internal state format, and compatibility can change between releases. If a save state stopped working after an update, first try loading a conventional memory card save. Where a state is the only remaining record of progress, keep the original file and investigate whether the PCSX2 version that created it is available. Avoid assuming that renaming the file will make it compatible. Once you successfully restore a state, save through the game’s normal memory card system as soon as possible. This creates a more durable recovery point for future PCSX2 versions.
Time Machine can restore earlier versions of emulator files if your backup history includes the relevant directory. Close the affected emulator, find its save folder in Finder and open Time Machine to inspect available backups. Restore the required file to a separate recovery folder where possible, then compare its date and size with the damaged copy. If you use iCloud Drive or another cloud storage service, check whether it provides file version history or deleted-file recovery for the specific location involved. These options are only useful when the files were actually included in the service’s backups or synchronisation. macOS does not automatically maintain recoverable historical copies of every emulator save.
If no working backup exists, professional file recovery software may help when the original save was deleted from a local drive, but it cannot reliably reconstruct data that has already been overwritten or permanently corrupted. Recovery from modern Mac internal SSDs can be particularly difficult after deletion because of storage management features such as TRIM. Avoid installing recovery utilities onto the same drive if doing so might overwrite the missing data. File repair tools advertised online should also be approached cautiously, especially those requesting access to entire emulator folders. Converting between recognised memory card formats can sometimes solve compatibility problems, but it cannot restore missing game progress without recoverable information.
The most dependable protection is a simple backup routine rather than relying exclusively on save states. Make regular in-game saves, maintain several separate save-state slots where supported and copy your emulator save directories before major updates. Include RetroArch’s save files and states, Dolphin’s GameCube and Wii data, and PCSX2’s memory cards in your Mac backup schedule. Keep at least one additional copy on an external drive or another independent storage location. Avoid running the same save folder simultaneously on multiple devices when cloud synchronisation is enabled. Finally, test an occasional backup by loading it in a controlled setup. A backup is only genuinely useful when you know it can restore your progress.