That empty world-select screen has a special kind of cruelty. One bad drag-and-drop, a launcher sync hiccup, a mate clicking the wrong option, and 300 hours of builds, bosses and questionable storage systems vanish. You may be able to recover deleted game worlds, but the right move depends on what actually happened to the files - and how quickly you stop making things worse.
This is not the moment to launch the game repeatedly, start a new world with the same name, or install three sketchy ‘miracle recovery’ tools. Treat the drive like a crime scene. The less it writes, the better your odds.
First: work out what “deleted” means
A deleted world is not always deleted. Games are exceptionally creative at making a save look dead when it is merely in the wrong folder, on another Windows account, missing a mod, or replaced by a newer cloud copy.
Start by checking whether the world is absent from the game’s menu or whether its actual save folder has gone. Close the game fully first. If it uses a launcher, close that too. Then find the game’s save location and look for the world folder, database file, or profile directory.
If the files are still there, do not move them immediately. Copy the whole save folder somewhere safe - your desktop is fine for the next ten minutes, but another drive is better. A complete copy matters because many games split one world across several files: player data, map chunks, configuration, mods, thumbnails and backups. Rescuing only the file with the obvious name can produce a world that loads with everyone’s inventory missing. Fun.
Check the boring places before the scary ones
Look in the Recycle Bin first. It sounds insultingly basic, but folders deleted through File Explorer often sit there until the bin is emptied. Restore the folder to its original location if you are confident it is the correct one. Otherwise restore it elsewhere, compare it with the current save folder, and keep both copies.
Next, check the game’s own backup behaviour. Some games keep rotating backups alongside the active save; others stash them in a separate folder with timestamps or names such as `backup`, `old`, `previous` or `restore`. Mod managers and server tools may make their own copies too.
Also inspect cloud-sync conflicts. Steam Cloud, OneDrive, Dropbox and similar tools can help, right up until a blank or older state wins the argument. Look for conflict prompts, duplicate folders, files labelled with a device name, and save directories modified around the time things went wrong. Turn syncing off temporarily while you investigate. You do not want a healthy copy being ‘helpfully’ replaced by the wreckage.
How to recover deleted game worlds from local storage
If the save folder really has disappeared and it is not in the Recycle Bin, stop using the affected drive as much as possible. Deletion usually removes the directory entry first. The underlying data may remain until new files overwrite those sectors. Installing a huge game, recording gameplay, or downloading a recovery app on to that same drive can turn recoverable data into digital compost.
Use a reputable file-recovery utility, ideally installed on another drive. Scan the drive that held the saves, then search by the game’s known folder name, save extension, world name, or modification date. Recover results to a different physical drive where possible - never back on to the one being scanned.
Recovery tools are strongest when the deletion was recent and the drive has seen little activity since. SSDs complicate things. Modern SSDs often use TRIM, which may clear deleted blocks quickly. That does not mean you should give up, but it does mean local file recovery is less certain than it was on an old hard disk.
When you find candidates, restore the entire directory tree rather than cherry-picking. Then test the recovered copy with the game offline, or by temporarily moving the current save folder out of the way. If it loads, immediately duplicate it again before doing anything adventurous.
If a co-op mate overwrote the world
Co-op worlds fail differently. Perhaps the host loaded an older local copy. Perhaps somebody imported a modpack, generated a fresh map, then synchronised it over the shared folder. Perhaps one person had the only world because ‘the host has it’ seemed like a perfectly normal arrangement at the time.
In these cases, your best recovery source is often another player’s PC. Ask everyone who has played recently not to open the game or let cloud sync run. Each player should copy their relevant save folder and note when it was last modified. The newest file is not automatically the best one: a newer timestamp may simply record the moment the bad overwrite happened.
Compare the candidates by file size, dates and in-game progress. If you can, make a scratch copy of each and load them one at a time. For games that separate character data from world data, keep those pieces matched to the same session where possible. Mixing a month-old world with last night’s player data can produce odd results, from missing bases to characters spawning in places that no longer exist.
This is why casual groups eventually need rules, even if the rule is just: nobody touches the shared save folder without a backup. Co-op does not need a rented dedicated server to be safe, but it does need a source of truth.
Version history beats recovery software
Recovery software is emergency medicine. Version history is a seatbelt.
A proper save history captures changes while your world is still healthy, so you can choose a point from before the disaster rather than hoping deleted fragments survive a scan. That matters for more than accidental deletion. A mod update can corrupt a world. A power cut can interrupt a save. A speedrun practice session can overwrite the one file you meant to preserve. Cloud sync can faithfully distribute the wrong version to every machine in the group.
With version history, the recovery flow is pleasantly unglamorous: close the game, find the last known-good checkpoint, restore it, launch the game, and get back to arguing about whose fault the creeper incident was. You trade a small amount of storage for a dramatically smaller chance of losing a weekend.
Checkpoint64 is built for exactly this sort of save-file chaos. It watches supported save folders, keeps each changed version, and lets you restore an earlier state without rummaging through hidden directories. Its free plan is actually free; if you need more storage, you can pay once and keep it forever. No subscription ambush. No ‘powered by AI’ sticker slapped on a file copy.
Set up protection before the next disaster
The safest backup is automatic, frequent enough to catch a bad session, and separate from the drive holding the original. Manual copies are better than nothing, but they rely on remembering them precisely when you are tired, annoyed, or about to try a mod called something like ‘Definitely Stable Terrain Overhaul’.
For solo games, make sure the whole save directory is covered, not just a single file. Keep several historical versions rather than one mirror. A mirror only preserves the latest state, which is useless when the latest state is the problem.
For shared worlds, agree who can make the active changes and when. If you pass the world between players, use a handoff method that prevents two people from editing competing copies. Keep a simple log of who had the world last and what changed. It may feel excessive for a two-person farm in Stardew Valley. It will feel extremely reasonable after someone restores the cave layout from three months ago.
Modded games deserve extra caution. Back up the save before changing loader versions, adding or removing major mods, altering world-generation settings, or migrating a pack. Keep a copy of the mod list with the save. A world file without the matching mod setup is sometimes recoverable, sometimes haunted, and occasionally both.
When recovery is not possible
Sometimes the honest answer is that the data is gone. If the deleted files have been overwritten, an SSD has cleared them, every cloud copy has synchronised the same empty state, and no player holds an older version, there may be nothing left to restore.
Do not let that send you into random-file-tool roulette. Preserve whatever evidence remains - screenshots, seed values, exported schematics, map files, configuration files and clips - then rebuild from the pieces that still exist. For creative games, importing a blueprint or using a seed can make the restart less brutal. For campaign games, a save editor may help recreate progression, but use one carefully and keep copies before each change.
The useful habit is not paranoia. It is giving your future self a way out. Keep more than one version, keep it somewhere other than the live save folder, and make co-op worlds belong to the group rather than the one mate whose PC is currently making a suspicious clicking noise.