First, decide: is it an “empty shell” or is the data really gone?

When the import reports success but you enter to find nothing, the cause usually falls into one of two categories, and the fixes are completely different:

  • You imported the wrong level / an empty shell (most common). The archive structure is wrong — world is wrapped in an extra nested folder, or level.dat and db/ are not in the archive root. The game never reads the real world data, so it loads it as a freshly created empty world, and what you see is blank. This is really a packaging/structure problem, not lost data.
  • Chunk data is missing or corrupted. The db/ (LevelDB) data that actually stores blocks and terrain is incomplete, so large areas can’t be read. Whether it can be recovered depends on the extent of the damage.

To tell which one it is, you don’t have to guess. Open the file with TopoBlocks: the free, on-device-by-default diagnosis checks the file type, version, structure, and missing files, and the report tells you directly whether the structure level is wrong or the chunk data itself has a problem.

If the structure level is wrong (simple fix is free)

This is the most common case of “import succeeded but it’s empty,” and also the easiest to solve. A .mcworld is essentially a ZIP with a renamed extension. Bedrock requires key files like level.dat to be in the archive root; the moment there is an extra folder wrapped around them, the game can’t read the world and falls back to creating an empty one.

For this kind of simple structure fix, TopoBlocks is free: it straightens out the levels, repacks, and generates a new .mcworld that imports correctly, and it never overwrites your original file — the original is preserved along with its hash and stays traceable. Re-import after the fix and your original world content comes back. For the same “extra nested folder” problem, see How to fix a world that won’t open due to nested folders and the in-depth tutorial Import and Repair.

If chunk data really is missing: an honest take on how far it can go

If diagnosis shows it’s not a structure problem but missing or corrupted chunk data in db/, we have to draw an honest distinction:

  • A “can’t read it” caused by structure/packaging can usually be fixed and verified for integrity.
  • But chunk data that has been fully deleted or overwritten cannot be restored out of thin air by any tool — we won’t exaggerate on this.

Complex damage can go through advanced repair (¥9 per attempt): before you pay, it shows the problem, the success odds, and the risks, with an automatic refund on failure, and prices are as shown in the app. The structure fix only addresses file/packaging problems and does not fix non-file issues like game crashes, mods, or version incompatibility. To learn more about missing chunks and holes, see What to do about a world with missing chunks or holes; if it won’t open at all and even importing fails, see What to do when a world won’t open.