Java ↔ Bedrock conversion · Bedrock · Beginner

How to Unpack, Edit, and Repackage Bedrock .mcworld Archives

A Minecraft Bedrock .mcworld file is simply a standard ZIP archive with a custom file extension used for easy one-click world importing across Windows, iOS, Android, and consoles. However, repackaging an edited world incorrectly will cause Minecraft to throw an import failure error. This guide shows you how to safely unpack, modify, and repackage .mcworld archives using the correct internal folder structure, or automate the process entirely inside your browser.

What you need

  • A Bedrock Edition world (.mcworld archive or raw world folder)
  • Your operating system's built-in file manager and ZIP extraction utility
  • Our browser-based Java ↔ Bedrock Converter (files are processed locally on your device and never uploaded)
  • A safe backup copy of your original world before making any changes

Step by step

  1. 1Back Up and Reveal the File Extension

    Before touching any world files, duplicate your original .mcworld file and store the copy in a safe backup folder. Next, configure your device's file manager to show file extensions so you can see the full file name. If you are starting from a raw Bedrock world folder from your device's storage (found inside the minecraftWorlds directory), duplicate that entire folder instead.

    Tip: On Windows, check the 'File name extensions' box under the View tab in File Explorer.

  2. 2Unpack the .mcworld Archive

    Rename your working file by changing the .mcworld extension to .zip, and confirm the extension change when prompted by your system. Use your device's built-in extraction tool to unzip the archive into a new folder. Because .mcworld is literally just a renamed ZIP archive, standard operating system tools can open it natively without needing any special software.

  3. 3Verify the Internal Bedrock Structure and Edit

    Open your extracted folder and inspect its contents. A valid Bedrock world must contain the level.dat file, levelname.txt, and the db folder (which holds the LevelDB chunk data) right here at the top level. You can now perform your edits, such as swapping in a custom world_icon.jpeg, adding behavior_packs, or modifying levelname.txt in a plain text editor.

    Tip: Never manually rename or delete the raw .ldb or .log files inside the db folder, as this will instantly corrupt the LevelDB database.

  4. 4Repackage Correctly at the Root Level (Manual Method)

    When you are ready to repackage, open your world folder so you are looking directly at level.dat and the db folder. Select all of these internal files and folders directly, right-click, and compress them into a new .zip file. Do not go up a level and zip the outer parent folder itself, because Bedrock's importer strictly expects level.dat to sit at the very root of the archive. Finally, rename your new .zip file back to .mcworld.

    Tip: If you use a Mac or iOS device, compressing manually may inject a hidden __MACOSX folder that can confuse Bedrock on other devices. Use Step 5 to avoid this.

  5. 5Package or Convert Automatically with Our Browser Tool

    To avoid root-folder nesting mistakes or cross-platform formatting issues, use our Java ↔ Bedrock Converter right in your browser. Click 'Open world folder or .zip' and select either your raw Bedrock folder, a mispackaged .zip, or even a Java Edition world folder. Choose Bedrock as your target output format and run the tool; it will automatically validate the level.dat and db directory structure and generate a clean, properly rooted .mcworld file directly on your device without uploading anything.

How it works

At its core, the .mcworld format is an ordinary DEFLATE-compressed ZIP archive. The custom extension exists purely so your operating system knows to hand the file directly to Minecraft Bedrock Edition when you double-click or tap it. When the game receives the file, its internal importer reads the root directory of the ZIP stream and looks immediately for a valid Bedrock level.dat header before extracting the contents into your local minecraftWorlds storage directory.

Unlike Java Edition, which stores chunk terrain inside the region folder as Anvil .mca files, Bedrock Edition uses a key-value database called LevelDB. All terrain, entities, and block data live inside the db subfolder as a collection of .ldb, .log, CURRENT, and MANIFEST files. Alongside the db folder, Bedrock uses level.dat (formatted in little-endian NBT with an 8-byte header) for global rules and player data, plus levelname.txt for quick display in the world menu.

The most critical mechanical rule of a .mcworld archive is path depth. If your ZIP archive's internal path looks like MyWorld/level.dat instead of just level.dat at the root, the Bedrock engine fails to find the world header during its initial scan and aborts with a generic 'Level import failed' message. Using our browser tool ensures the ZIP central directory is always written with level.dat and db/ at depth zero.

Common mistakes

  • Zipping the outer parent folder instead of selecting the internal files (level.dat, db, levelname.txt) directly, which buries the world data one folder too deep.
  • Accidentally naming the file world.mcworld.zip because file extensions are hidden in your operating system's file manager.
  • Packing a Java Edition world (which contains a region folder and big-endian level.dat) into a .mcworld file without running it through the Java ↔ Bedrock Converter first.
  • Deleting the MANIFEST or CURRENT files inside the db directory while trying to clean up or reduce world file size, which renders the LevelDB terrain unreadable.

FAQ

Why does Minecraft say 'Level import failed' when I open my new .mcworld file?

Nine times out of ten, the files were zipped inside a parent folder. Rename the .mcworld to .zip and open it: if you see a single folder instead of seeing level.dat and the db folder immediately, unpack it and re-zip only the inner contents, or run the folder through our Java ↔ Bedrock Converter.

Can I import a .mcworld file directly onto a console?

Consoles do not allow you to open .mcworld files from a file browser directly. To get a custom .mcworld onto a console, import the .mcworld file on Windows, iOS, or Android first, upload that world to a personal Realm, and then download the world from the Realm on your console wearing the same account.

Are my world files uploaded to a server when I use the Java ↔ Bedrock Converter?

No. All of our tools run entirely locally inside your web browser using your device's own memory and processor. Your world files never leave your computer or phone.

To successfully edit and repackage a Bedrock .mcworld archive, Always back up your world first, extract it as a standard .zip, and ensure level.dat and the db folder sit directly at the root level when compressing it back—or let our browser-based Java ↔ Bedrock Converter package it cleanly for you.

More java ↔ bedrock conversion guides

Java ↔ Bedrock conversionHow to Convert a Minecraft Bedrock (.mcworld) Save to Java EditionMoving a world from Minecraft Bedrock Edition to Java Edition requires translating the entire underlying database structure. Using our browser-based Java ↔ Bedrock Converter, you can easily transform a Bedrock world folder or .mcworld archive into Java-compatible Anvil files. Because the tool runs locally in your browser, your save files are processed quickly and never leave your computer.Java & BedrockBeginner5 steps
Java ↔ Bedrock conversionHow to Keep Your Player Inventory and Ender Chest After Java ↔ Bedrock ConversionConverting a Minecraft world between Java and Bedrock editions often leaves you spawning at the world origin with an empty inventory. This happens because the two editions track singleplayer identity using completely different internal tag structures and database keys. By mapping your UUID data and LocalPlayer tags in the browser-based NBT Editor, you can safely transfer your inventory, Ender Chest, and exact coordinates without uploading any files.Java & BedrockIntermediate5 steps
Java ↔ Bedrock conversionHow to Trim a Huge World Before Converting Between Java and BedrockConverting a multi-gigabyte Minecraft world between Java and Bedrock editions can easily exceed your web browser's memory limit. Because our tools process everything locally on your device without uploading files, the smartest approach is to prune unexplored chunks first. Combining the Chunk Trimmer with the Java ↔ Bedrock Converter reduces conversion time from hours to seconds while keeping all your builds completely intact.Java & BedrockIntermediate5 steps
Java ↔ Bedrock conversionJava vs Bedrock World Conversion: What Transfers and What Gets LostConverting a Minecraft world between Java Edition and Bedrock Edition is more than just changing a file extension; it requires translating two fundamentally different game engines. This guide explains exactly what happens to your blocks, entities, inventories, and redstone mechanics during conversion, and how to use our browser-based Java ↔ Bedrock Converter safely. Because all processing runs locally in your browser without uploading files, you can quickly test and inspect your converted worlds with complete privacy.Java & BedrockIntermediate4 steps