Bedrock: open it and it imports
.mcworld is Minecraft Bedrock’s packaged world file. As long as your device has Bedrock installed, importing is almost a “single tap”:
- Get the file — save the
.mcworldonto this device via AirDrop, a cloud drive, an email attachment, and so on. - Open it —
- iPhone / iPad: tap the
.mcworldin the Files app, and the system launches Bedrock and imports it automatically; - Android: just open it in a file manager;
- Windows 10 / 11: double-click the file to trigger the import.
- iPhone / iPad: tap the
- Enter the world — once the import finishes, you’ll see it in the game’s world list and can play it directly.
The whole process doesn’t change the original .mcworld; Bedrock copies the world into your saves list.
Why Java Edition can’t import directly
.mcworld is a Bedrock-only format, and Java Edition can’t import it directly. If you have a .mcworld but want to play it in Java Edition, there’s currently no direct path; if you have a Java world and want to play it on your phone (Bedrock), you first need a Java to Bedrock conversion. The conversion is one-way, outputs an importable .mcworld, and comes with a compatibility score and an itemized change report — we don’t promise it’s 100% lossless.
Import failed? It’s usually a structure problem
When opening it does nothing or shows an error, the vast majority of the time it isn’t a “broken file” but a wrong archive structure — level.dat isn’t in the archive’s root, or the world has an extra folder wrapped around it. In that case, you can use mcworld.app’s free on-device diagnosis and, if needed, do a simple structure repair to produce a new file that imports correctly — all without overwriting your original file (each run creates a new version and keeps the original for traceability). Diagnosis is free, and you pay based on the result; prices are as shown in the app. For more detailed troubleshooting, see the in-depth tutorial Import and Repair.