Do not delete the world folder because the launcher no longer lists it. Minecraft world metadata, player state, and region terrain are stored separately, so a damaged level.dat does not automatically mean the entire world is lost.
Back up the broken world before touching it
- Close every game, launcher, server, or tool that could write the world.
- Copy the whole world folder, including level.dat, level.dat_old, region, playerdata, and the DIM folders.
- Work only on the copy and record which file failed and what error appeared.
Try level.dat_old first
Java Edition commonly keeps a previous metadata file as level.dat_old. On a duplicate world, preserve the broken level.dat as level.dat.broken, copy level.dat_old to a new level.dat, and test the duplicate. Keep both originals so you can reverse the attempt.
level.dat
level.dat_old
level.dat.brokenWhen the world is missing from the list
Verify that you are looking at the actual world root: level.dat should sit directly inside the folder, not inside an extra nested directory. If the launcher still cannot read the folder after a copy-based level.dat recovery, inspect the logs and test the world with the same Minecraft version that last saved it.
Repair datapack or dimension metadata
Some load failures come from datapacks, custom dimensions, or mod-specific metadata rather than the core NBT tree. Remove or restore those components only on a duplicate and match the mod or datapack versions that created the save.
Recover player data separately
If the recovered world loads but your character is empty, inspect the server UUID file or a prior level.dat Player compound separately. Player recovery is a different task from repairing global world metadata.
Open a level.dat backup
Use the editor to inspect a backup or recovered copy without uploading the world file.
When the region files are the real problem
If the world opens but one area crashes, disappears, or contains broken terrain, the region/*.mca files may be the failing layer. Replacing level.dat will not repair a corrupted chunk. Restore region files from a backup or use a region-aware recovery workflow on a duplicate.
Frequently asked questions
Does a corrupted level.dat mean the region files are lost?
Not necessarily. level.dat stores global metadata while region files store chunk terrain. Back up both, then test metadata recovery separately from any region repair.
Can I use level.dat_old on the live world immediately?
Use a duplicate first. Keep the original level.dat and level.dat_old untouched until you have confirmed that the recovered copy loads and contains the expected world state.
What if level.dat_old is also damaged?
Look for a whole-world backup, hosting snapshot, or older server backup. You can inspect a damaged copy, but do not overwrite the only source while experimenting.
Should I delete unknown tags to make the file load?
Not without a backup and version context. Unknown tags may belong to mods or custom dimensions. Isolate the change on a duplicate and remove only data you can identify with confidence.