First things first: a .mcworld that won’t unzip isn’t necessarily broken

A .mcworld is essentially a ZIP archive with a different extension, holding a complete Bedrock world save (level.dat, db/, and so on). So you can simply make a copy, rename the copy to .zip, and try opening it with an extraction tool — if you want to understand what this file actually is, see What is a .mcworld file and how to open it.

If it still won’t extract after renaming, or it opens but won’t import into the game, don’t jump to the conclusion that “the file is broken.” The most common scenarios usually aren’t real corruption at all:

  • Wrong packaging method — it was originally packed with a non-standard compression method that some extraction tools don’t recognize.
  • An extra wrapping folder — the archive root contains another nested folder, so level.dat isn’t at the root and the game can’t find the world.
  • Truncated download/transfer — the file didn’t transfer completely, which looks like a “corrupted archive.”

Most of these are structure or packaging issues, not the data itself being damaged.

Use the free on-device diagnosis to tell “structure issue” from “real corruption”

Instead of switching tools and re-extracting on guesswork, let TopoBlocks point out the problem first. Drag the .mcworld or .zip into the app. Diagnosis is free, runs on-device by default, and uploads nothing. It will tell you whether this is a structure issue or genuine corruption, and list the file type, version, structure, and any missing items.

  • If it’s a structure issue (packaging method, an extra wrapping folder, level.dat not at the root), the simple structure fix is free and produces a new, importable .mcworld. Among these, “an extra wrapping folder” is the number-one cause of import failures — see What to do when a world is missing level.dat for details.
  • If it’s deeper, complex corruption, it goes through Advanced Repair (¥9 per fix). The price is shown in-app, and before you pay it displays the issue, success probability, and risks, with automatic refunds on failure — to be honest: not all corruption can be 100% recovered, which is exactly why you see the probability first and then decide.

It’s worth emphasizing that structure repair addresses file/packaging/structure problems; if what you’re hitting is a non-file cause like a game crash, mod incompatibility, or version mismatch, structure repair won’t help and you’ll need to troubleshoot separately.

How repair guarantees it won’t damage your original file

This is a product red line: repair always produces a new file and never overwrites your source. The original .mcworld and its hash are both preserved and traceable, so even if the repair result isn’t ideal, your original stays untouched.

So the correct order is: keep the original safe → free on-device diagnosis → free fix for structure issues, or review the report first for complex corruption → import the newly generated file. To learn more about how “won’t open / corrupted” problems are handled systematically, see How to repair a corrupted .mcworld world.