Your 140-hour world has vanished. Maybe the game crashed during a save. Maybe a mod update turned your town into a haunted void. Maybe your mate hosted co-op, overwrote the good world, and has gone mysteriously quiet on Discord. This guide to game save recovery is for the part after the swearing: what to check, what not to touch, and how to get your progress back without making the wreckage worse.
First rule: stop playing immediately
If a save has disappeared, corrupted, or rolled back, do not keep launching the game to see whether it magically fixes itself. Every new autosave can overwrite a usable copy. Cloud sync clients can also see an empty or broken local folder and enthusiastically spread that disaster to every machine you own. Cheers, technology.
Close the game, then close any launcher that might manage saves. Pause OneDrive, Dropbox, Steam Cloud, or another sync tool if it is actively changing files. Take a copy of the entire save folder before trying repairs, even if the files look wrong. Put that copy somewhere separate and label it with the date.
That first copy is your evidence locker. Recovery is much easier when you have not accidentally replaced the last surviving version with a fresh, equally broken one.
Work out what actually happened
A missing save and a corrupted save need different treatment. If the game no longer lists your character or world, the files may be in the wrong folder, under a different Windows account, or hidden behind cloud sync confusion. If the save appears but will not load, crashes on load, or places you in an earlier state, you are looking for an older version rather than simply locating a folder.
Also check whether this is a game problem or a launcher problem. A game launched through Steam, a mod manager, Game Pass, or a portable install may use different save paths. The game did not necessarily eat your save. It may just be looking in the wrong cupboard.
Guide to game save recovery: find the save folder
On Windows, many games store saves in Documents, AppData, Saved Games, or the game's installation folder. AppData is hidden by default, because apparently the place holding your 300-hour RPG campaign needed an invisibility cloak. Type `%appdata%` or `%localappdata%` into File Explorer's address bar to get there quickly.
On macOS, look in the Library folder inside your user folder, particularly Application Support, Containers, or Preferences. On Linux, saves commonly live in `.local/share`, `.config`, or inside the relevant Steam compatibility prefix if you are using Proton. Emulator saves can sit beside the ROM, in the emulator's own data folder, or in a separately configured path.
Once you find a likely folder, sort files by date modified. Look for familiar world names, character names, profile files, or folders with recent timestamps. Some games use a single large save file. Others split a world across a folder full of chunks, metadata, player inventories, and backups. Copy the whole set. Recovering only one file from a multi-file world can create a new flavour of corruption.
If the folder is empty, search your drive for the world name, the game's save extension, or a recognisable player name. Check the Recycle Bin too. It is not glamorous, but accidental deletion remains one of the few disasters with a pleasantly boring solution.
Check built-in backup files before downloading recovery tools
Many games quietly keep backups with names such as `.bak`, `backup`, `old`, `previous`, or a timestamp. Factorio, Minecraft modpacks, management sims, and emulator setups often have their own backup habits. Look in the save folder and any adjacent `backups` directory.
Do not overwrite the current save with a backup straight away. Rename the current folder first, then copy the backup into place. Launch the game once and verify that the world loads. If it does, immediately make another copy before continuing.
File recovery software is the next rung down the ladder, not the first. It can help after deletion, especially on a hard drive, but it is less reliable on SSDs because deleted data may be cleared quickly. Installing recovery software onto the same drive can also overwrite the very data you want back. Use another drive if you can.
Restore an earlier version if the save exists but is wrong
A save that loads badly is often the more painful case. You can see your world. It is just missing last night's build, has duplicated items everywhere, or crashes the moment you enter the base where the mod conflict happened.
Windows may have previous versions available through File History or a restore point, depending on how your PC was set up. Right-click the save folder, open Properties, and look for Previous Versions. On macOS, Time Machine may have a historical copy. Linux users may have snapshots through their filesystem or backup tool. These are worth checking, but they depend entirely on having configured them before the catastrophe. Past you either did the sensible thing or left present you a boss fight.
Steam Cloud can sometimes provide a useful copy, but it is not a proper version-history system. Its job is usually to keep the latest save in sync, not preserve every meaningful state forever. If a bad save syncs successfully, Steam may faithfully deliver it to your other device. That is synchronisation, not recovery.
When restoring an older version, keep the damaged save separately. An older save may load, but you might later need a newer file to recover screenshots, map data, or a specific player inventory. Treat every candidate as a branch, not a sacrifice.
For co-op worlds, fix the hand-off problem
Host-dependent worlds create a special kind of nonsense. One player owns the save, everyone else owns anxiety. When the host is away, changes PCs, or accidentally rolls back the world, the whole group is stuck negotiating through chat logs and half-remembered filenames.
The sensible approach is to keep a shared history and make hand-offs deliberate. One person takes control of the world, plays, then releases it for the next host. The important part is preventing two people from editing separate copies at once. That creates conflicting timelines, and neither one contains the iron farm everyone spent Sunday building.
Checkpoint64 is built for this exact mess: it watches supported save folders, keeps version history, and uses locked co-op hand-offs so a shared world has one active editor at a time. It also checks for changes every 30 seconds and uploads only what changed, rather than asking you to perform a weekly ritual with USB sticks and optimism. The free plan is actually free, while extra space is a pay-once option rather than another recurring bill lurking in your bank app.
The trade-off is simple: any automated backup system must be set up before the failure. It cannot time-travel into a folder that was never backed up. But once it is watching the right saves, rolling back a bad mod session becomes a few clicks rather than a forensic investigation.
Make the next recovery boring
The best save recovery story is the one where you restore yesterday's version, complain for thirty seconds, and get back to playing. Set up automatic backup for the games that matter most, especially modded games, long-running survival worlds, emulators, and co-op saves.
Before a major mod update, server migration, operating-system reinstall, or risky bit of save editing, create a named checkpoint. Keep at least one copy away from your main PC. If you play on a laptop and desktop, make sure both machines are not silently fighting over the same save folder.
And before your crew starts a shared campaign, decide who hosts, how hand-offs work, and where the authoritative save lives. That conversation takes two minutes. Rebuilding a vanished Valheim base takes considerably longer, mostly because everyone will insist they remember the roof differently.
Your save files are not disposable cache. They are the cartridge shelf holding your actual game history. Treat them that way, and the next corrupted world becomes an inconvenience instead of a eulogy.