Why an extra folder stops the world from opening

When Bedrock imports a world, it looks for level.dat, db/, and similar files directly at the root of the archive. A correctly structured .mcworld, once extracted, should have these at the top level:

  • level.dat — world metadata
  • db/ — the actual world data
  • levelname.txt, the cover image, and other supporting files

But when people tidy things up on a computer, or repack the world the wrong way, they often accidentally wrap the whole world in an extra folder — the archive root contains only a single MyWorld/ folder, and you have to open it before you see level.dat. Now the game can’t find level.dat at the root, decides this isn’t a valid world, and import fails or reports that the world can’t be found. This is also one of the most common causes behind “Minecraft says the world was not found”.

How to confirm and fix it

The most direct check: rename the .mcworld to .zip, extract it, and see whether level.dat appears right at the top level. If the top level holds only one folder and you have to go one level deeper to find the files, there’s an extra wrapper.

With TopoBlocks you don’t have to wrestle with archives by hand:

  1. Free on-device diagnosis — open the file and, by default, it checks the file type, version, and structure for free on your device, telling you exactly which level level.dat sits at and whether there’s an extra outer folder.
  2. Simple structure fix (free) — once it’s confirmed as a nesting issue, one tap removes the extra outer folder, moves level.dat and db/ back to the root, and generates a brand-new .mcworld that imports normally.
  3. Import verification — open the new file on a device with Bedrock and confirm it shows up in your world list.

Two lines here that never change: diagnosis and this kind of simple structure fix are on-device and free by default; the fix never overwrites your original file — it generates a new version, and the original is preserved with its hash for traceability. If your problem looks more like “level.dat is simply gone,” see What to do when a world is missing level.dat.

What an “extra folder” fix can’t solve

To be honest about the limits: the simple structure fix only addresses file-level / packaging structure problems. If the import failure is actually because the file is genuinely corrupted (not just mis-nested), the game version is incompatible, the device is out of storage, or a mod is causing trouble, that’s outside what “remove the outer folder” can fix.

  • Genuine corruption can go through the advanced repair (¥9 per fix). Before any payment we show the problem, the success probability, the risks, and the refund policy; failures are refunded automatically, and prices are as shown in the app.
  • Version incompatibility, device storage, mods, and other non-file problems need separate troubleshooting — a structure fix can’t help there.

For a systematic look at troubleshooting import failures, see What to do when importing a world fails, or the in-depth tutorial Open, diagnose, and repair worlds.