The simplest way to import a .mcworld on iPad

On an iPad with Minecraft Bedrock installed, importing a world is really just one step: open the built-in Files app, find that .mcworld file — it might be in Downloads, iCloud Drive, or something someone sent you over AirDrop — and tap it once. The system opens it in Bedrock, adds the entire world to your worlds list, and after a brief moment you can jump in and play.

A couple of things to confirm first:

  • Bedrock is actually installed on the iPad. Java Edition can’t import .mcworld; if you have a Java world and want to play it on iPad, you first need a Java → Bedrock conversion.
  • The file extension is .mcworld — there’s no need to manually rename it to .zip before importing. Bedrock on iPad recognizes this extension directly.

The import method is broadly similar across platforms. For the Windows Bedrock approach, see How to import a world on Windows Bedrock, and for the more general steps, see How to import a .mcworld into Minecraft.

Tapped it but got an import error? It’s usually a structure issue

If Bedrock throws an error after you tap the .mcworld, or nothing happens at all, in the vast majority of cases the file isn’t “broken” — the packaging structure is just wrong. The most common case is that level.dat isn’t placed at the root of the archive, or the world is wrapped in an extra folder, so the game can’t find the world data at the root.

For this you can use TopoBlocks: open this .mcworld on-device and it will diagnose the file type, version, and structure — free and on-device by default — and tell you exactly where it’s stuck. Fixing simple problems like the packaging structure is free and produces a new, importable .mcworld; then you go back to the Files app and tap it again. The whole process never overwrites your original file — every time it creates a new version, and the original, along with its hash, is preserved and traceable.

One thing to be clear about: a structure fix only solves file / packaging / layout problems. It does not fix game crashes, mod conflicts, or version incompatibility — those aren’t file-related causes. If the world imports and loads but crashes the moment you enter, the cause is usually something else. For more troubleshooting ideas, see What to do when a world fails to import.

Complex corruption and pricing

If the diagnosis finds something deeper than a packaging-structure problem — actual corruption in the file itself — you can go through advanced repair (¥9 per repair). Before you pay, it first shows the specific problem, success probability, risks, and the refund policy — whether it can be fixed and whether it’s worth fixing, you decide after seeing the full picture. Prices are as shown in the app, and failed repairs are refunded automatically. Diagnosis and simple structure fixes are always free and done on-device by default; if you later want to back up the world to the cloud, that also requires your explicit authorization before anything is uploaded.

For a systematic look at the full flow of opening, diagnosing, and repairing worlds, see the in-depth tutorial Import and repair worlds.