The standard way to import a .mcworld on Android

Minecraft on Android phones is Bedrock, and it uses the .mcworld package file to import worlds. Importing is actually simple, and there’s no need to unzip anything manually:

  1. Transfer the file to your phone—use cloud storage, a chat app, a USB cable, or a browser download to save the .mcworld onto your phone.
  2. Find it in your file manager—open the system Files app or your usual file manager and locate that .mcworld.
  3. Just tap it—tap the file, and if an app picker pops up, choose Minecraft; the system parses and imports the world automatically.
  4. Confirm in the game—go back to Bedrock’s world list, where the new world usually sits at the top, and enter it to play.

A .mcworld is essentially a ZIP with a renamed extension, and Bedrock parses the level.dat, db/, and other files inside it on its own, so unzipping it manually tends to scramble the structure and cause import failures. To learn more about the file first, see What is a .mcworld file and how to open it, and for more general import instructions see How to import a .mcworld into Minecraft.

Import fails after tapping? It’s usually a structure problem

If tapping a .mcworld shows an error, hangs, or simply does nothing, the vast majority of the time the file isn’t “broken”—the ZIP structure is just nested wrong. The most common case is level.dat not sitting at the root of the package, or the world being wrapped in an extra folder, so Bedrock can’t find the world at the root.

In this situation you can use TopoBlocks to diagnose it for free on-device. It reads out the file type, version, structure, and any missing files, and points out where the problem is. The fix for these simple structure issues is free too: it moves files back to the correct level, generates a new .mcworld that imports normally, and then you just tap it to import.

To be clear: the diagnosis runs on your device by default, and whether diagnosing or repairing, it never overwrites your source file—it generates a new version each time and keeps the original for traceability. Only for deeper damage (not a simple structure problem) does it move to advanced repair, and before any payment it shows you the problem, the success probability, the risks, and the refund terms, with prices shown in the app.

A few honest notes

  • Structure repair only solves file and packaging issues. If the import really failed because of insufficient device storage, an outdated game version, or because the world itself depends on mods / behavior packs, those are outside the scope of structure repair and need to be diagnosed separately.
  • Java worlds can’t be imported directly on Android. Android only recognizes Bedrock’s .mcworld; a Java world needs a one-way Java Edition → Bedrock conversion first before you can play it. See Java to Bedrock (playable on iPhone).
  • Importing gives each person their own copy. Sending a world to a friend and each importing it means you each play your own copy, not together in real time. To share a world reliably, see How to share a Minecraft world with friends.