First, separate the two: a “packaging issue” vs. “real corruption”

When a Bedrock world won’t open, many people’s first thought is “the save is broken.” But in reality, most of the time it’s just the wrong packaging or structure, not data that’s actually destroyed. A Bedrock world’s real data lives in the db/ directory (a LevelDB database), alongside metadata files like level.dat. The game usually fails to recognize a world because:

  • level.dat isn’t at the root of the archive, or there’s an extra folder wrapped around everything;
  • the world was packaged the wrong way, so Bedrock can’t detect the world structure;
  • the LevelDB data inside db/ is itself damaged (this is the only thing that counts as real “corruption”).

Open your .mcworld / .zip / world folder with TopoBlocks, and it will diagnose the file type, version, structure, and missing files on-device and for free by default, telling you which category you’re actually in first — don’t rush to spend money, get clear on the problem first. To understand what db/ actually is, see What is db/ (LevelDB) in Bedrock.

Structure/packaging problems: the simple fix is free

If the diagnosis says the structure layout is wrong (the most common case), you’re in luck: the simple structure fix is free. It moves level.dat and other files back to the correct location, removes any extra outer folder, and then produces a new world file that imports normally — open it on your Bedrock device and you’re in.

The whole process never overwrites your source file — the original save, hash and all, is preserved and traceable, so even a bad fix can be rolled back anytime. For more on this kind of “the file is broken and won’t open” troubleshooting, What to do when a .mcworld file is corrupted has a fuller explanation.

Real db/ corruption: advanced repair, see the odds before you pay

If the diagnosis points to corruption of the db/ (LevelDB) data itself, that’s complex damage and goes through advanced repair (¥9 per run, price shown in-app). Here we have to say it honestly: not every kind of damage can be restored 100% — LevelDB corruption varies in severity, and so does how much can be saved.

So before you pay, advanced repair first displays the problems it diagnosed, the estimated success odds, and the risks, and you decide whether to repair. A failed job refunds automatically, and likewise it never overwrites the source file — it only generates a new version.

One last reminder: structure repair only solves file, packaging, and structure problems. If your world is the “crashes/force-closes the moment you enter” kind, the cause may be a version incompatibility, a mod, device memory, or another non-file problem — that’s outside the scope of structure repair and needs targeted troubleshooting. And if the world was actually deleted by mistake rather than corrupted, whether you can get it back depends on whether you have a backup — see Can a deleted Minecraft world be recovered.