Short answer: the previous automatic backup of level.dat

level.dat_old is simply the previous automatic backup of level.dat. Every time the game successfully saves a world, it first keeps the current level.dat as level.dat_old, then writes a new level.dat. So the same world folder usually contains both files side by side:

  • level.dat — the world’s current metadata: name, game mode, seed, spawn point, game rules, version, and so on. For a closer look at what it stores, see What is the level.dat file.
  • level.dat_old — a copy of the previous level.dat, acting as a “roll back if a write goes wrong” safety net.

It is worth emphasizing: both of these files are only the world’s metadata. The actual block, chunk, and entity data lives in db/ (Bedrock) or region/ (Java Edition), not in level.dat / level.dat_old.

It can help when level.dat is corrupted — but only so much

If a save is interrupted partway through and level.dat gets written incorrectly, the world may fail to open. In that case level.dat_old is a ready-made fallback clue: as long as it is intact, replacing the corrupted level.dat with it (renaming it over) can often let the world reopen, at the cost of rolling back to the metadata from the last save.

But to be honest about its limits:

  • It keeps only one copy, and it gets overwritten on every save — it is not a multi-version history.
  • It is only metadata — if the chunk data in db/ / region/ is corrupted, swapping in level.dat_old will not save it.
  • It is not a full world backup — do not treat it as a reason to feel “already backed up.”

If you really want safety, keep a full copy

level.dat_old cannot solve problems like “the whole world is corrupted” or “the world was deleted by mistake.” When a world will not open or reports corruption, you can use TopoBlocks for a free on-device diagnosis: it reads level.dat / level.dat_old and the overall structure, and tells you whether the problem is in the metadata, the packaging layout, or deeper chunk data. For simple issues at the structure or packaging level, the basic repair is free and generates a new file that imports correctly, and it never overwrites your original file. For complex corruption, it first shows you the problem, the success probability, and the risks, and only proceeds to an advanced repair after you confirm (¥9 per attempt, automatically refunded on failure, with prices shown in the app). For how to tell what is going on, see What to do when a world file is corrupted and Can a deleted world still be recovered.

In the end, level.dat_old is just a “fallback clue from the last save.” If you truly want safety, you should export a separate full .mcworld offline copy or enable version history — each save is a new, traceable version, and restoring only creates a new copy without overwriting your current world.