Don’t panic: .mcworld.zip is usually just an extension issue
When you see a world file turn into .mcworld.zip, the first instinct is usually “the file is broken.” In fact, most of the time it isn’t — a .mcworld is really just a ZIP archive with a renamed extension (to learn more, see What is a .mcworld file? How do you open it). When you download it, send it through a chat app, or pass it through certain unzip/cloud-storage tools, they “recognize” it as a ZIP and take it upon themselves to add .zip, so it ends up with a double extension like .mcworld.zip.
The world data inside is usually untouched. What actually keeps Bedrock from recognizing it is often just that extra outermost .zip.
How to rename it back to a single .mcworld
On iPhone / iPad:
- Open the Files app and find that
.mcworld.zip. - Make a backup copy first (long-press → Copy) in case you rename the wrong thing.
- Long-press the file → Rename, delete the trailing
.zip, and keep just a single.mcworld. - Open the corrected
.mcworld, and the system will use Bedrock to import the world.
If the system hides extensions by default and you can’t see .zip, you can first turn on “Show all extensions” in the file settings, or simply switch to the diagnosis method below and let the tool handle it for you. The idea is the same on Android and Windows: just remove the extra trailing .zip. For the exact import steps, see How to import a .mcworld into Minecraft.
Still won’t open after renaming? It’s probably the internal structure
If you’ve already renamed it back to a single .mcworld but it still fails to import, the problem usually isn’t the extension but the layout inside the archive: level.dat isn’t at the root, or the world is wrapped in an extra folder. This kind of “wrong structure” is the most common cause of Bedrock’s “import failed,” and renaming the extension alone won’t fix it. There’s also a case where an unzip tool extracted it as a regular ZIP and then repackaged it, scrambling the structure — this is covered in more detail in .mcworld archive won’t extract / unusable after extracting.
This is where you can use TopoBlocks: open the file for a free on-device diagnosis, and it will tell you whether it’s a structure-layout issue, a version issue, or something else. Simple structure/packaging repair is free and produces a new .mcworld you can import normally. One thing to note: structure repair only solves file- and packaging-level problems — it does not fix game crashes, mod conflicts, or cross-version incompatibility and other non-file issues; for more complex corruption, it goes through paid advanced repair, showing you the problem, the success probability, and the risks before you pay, with an automatic refund if it fails (prices are as shown in the app).
Whichever path you take, TopoBlocks never overwrites your original file — it outputs a new version, and the original .mcworld.zip, along with its records, is always kept and traceable. So even if you’re not sure which step is right, you can safely give it a try first.