How to Import a World in Bedrock on Windows

Importing a world in Bedrock on Windows: just double-click

On a PC with Minecraft Bedrock (the Windows 10/11 Store edition) installed, importing a world is actually very straightforward: find the .mcworld file in File Explorer, double-click it, and the system opens it in Bedrock and adds the world to your world list. Once the import finishes, open the game’s Play → Worlds and you’ll see it there, ready to load.

A .mcworld is essentially a ZIP archive with a changed extension; inside is a complete Bedrock world save (level.dat, db/, etc.). As long as the structure is correct and the edition matches, double-clicking to import is the easiest approach. For a more systematic look at importing on different platforms, see How to import .mcworld into Minecraft.

Won’t import? It’s usually a folder-structure issue

When double-clicking does nothing or it says it can’t import, in the vast majority of cases the file isn’t “broken”—the ZIP folder structure is wrong. The most common cause is that level.dat isn’t placed at the root of the archive, or the world is wrapped in an extra folder, so Bedrock can’t find the world at the root.

You can handle this with TopoBlocks: open the .mcworld, and by default it diagnoses on-device, for free—file type, edition, structure, and missing files—telling you exactly where it’s stuck. If it confirms a folder-structure issue, the simple structure repair is also free: it removes the extra outer layer, moves the files back to the correct location, and produces a new .mcworld that imports correctly, while never overwriting your original file—the original, along with its hash, is preserved and traceable. Only for more complex corruption does it fall back to advanced repair (¥9/repair), and before any payment it shows you the problem, success probability, risks, and refund terms; prices are shown in-app. For the full diagnose-and-repair flow, see Open and repair worlds.

If your world is Java Edition

There’s one kind of “import failure” that has nothing to do with structure: what you have is a Java Edition world. Java and Bedrock world formats aren’t interchangeable, so Bedrock on Windows can’t import a Java world directly. To play it in Bedrock, you first need a one-way Java Edition → Bedrock conversion—Bedrock can’t be converted back to Java.

Conversion is pay-per-use with an automatic refund on failure, and prices are shown in-app; it also does not promise “100% lossless”: before payment you get a compatibility score. Terrain and the vast majority of blocks usually migrate fine, while Java-only entities, behavior/resource packs, and some redstone behaviors may be replaced with compatible equivalents or written into an item-by-item report. For how-to details see Java to Bedrock (playable on iPhone) and the in-depth tutorial Java to Bedrock. The whole process likewise never overwrites your source file, generating a traceable new version every time.