Java ↔ Bedrock conversion · Java & Bedrock · Beginner

How to Convert a Minecraft Bedrock (.mcworld) Save to Java Edition

Moving 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.

What you need

  • A Minecraft Bedrock world folder or an exported .mcworld archive.
  • A copy of Minecraft: Java Edition installed on your computer.
  • Access to the Java ↔ Bedrock Converter on our site.
  • Enough free disk space to hold a backup and the newly converted world.

Step by step

  1. 1Back Up and Export Your Bedrock World

    Always create a backup copy of your world before editing or converting files to prevent accidental data loss. In Minecraft Bedrock Edition, click the pencil icon next to your world, scroll down to the bottom of the Game settings tab, and select Export World to generate a .mcworld file. If you prefer to grab the raw folder directly, look inside your local com.mojang/minecraftWorlds directory, where each world is stored in a randomly named folder containing a level.dat file and a db subfolder.

    Tip: If you cannot recognize which folder in minecraftWorlds is the right one, open the levelname.txt file inside each folder to read the human-friendly world name.

  2. 2Load the World into the Java ↔ Bedrock Converter

    Open the Java ↔ Bedrock Converter tool on our site. Click the Open world folder or .zip button and select either your exported .mcworld file or the raw Bedrock world folder from your drive. Note that a .mcworld file is simply a standard .zip archive with a different file extension, so the browser reads it immediately without needing to be uploaded to a server.

    Tip: If your browser does not display the .mcworld file in the file picker window, change the file type filter at the bottom right of the dialog box to All Files.

  3. 3Configure Settings and Run the Conversion

    Once the tool detects your Bedrock level.dat and the db folder, set the target output format to Java Edition and select the game version you plan to play. Choosing the exact target version is important because Java Edition changed how block palettes and chunk heights are stored in recent updates. Click Convert to start translating the Bedrock LevelDB key-value pairs into Java Anvil .mca region files right inside your browser memory.

    Tip: Keep the browser tab active while converting very large worlds so your operating system does not throttle the background memory usage.

  4. 4Download and Extract into Your Java Saves Folder

    When the process completes, click the Download button to save the converted .zip archive to your computer. Locate your Java Edition directory—typically found at %appdata%/.minecraft/saves on Windows, ~/Library/Application Support/minecraft/saves on macOS, or ~/.minecraft/saves on Linux. Create a new folder inside the saves directory, and extract the contents of the downloaded .zip directly into it.

    Tip: Verify that the newly extracted folder immediately contains the level.dat file and the region subfolder, rather than another nested folder inside it.

  5. 5Launch Java Edition and Verify the World

    Open your Minecraft Java Edition launcher, make sure your profile matches the target version you selected during conversion, and boot the game. Click Singleplayer and select your newly converted world from the list. Upon loading, check your coordinates and surrounding chunks to confirm that your structures transferred properly.

How it works

Minecraft Bedrock and Java Editions store world data using completely different architectures. Bedrock relies on a modified LevelDB database stored inside the db subfolder, breaking chunk data into compact binary key-value pairs distributed across .ldb and .log files. Furthermore, Bedrock writes its data using Little-Endian byte ordering.

Java Edition uses the Anvil format, which groups 32x32 chunks together into distinct region files (.mca) stored inside the region, DIM-1/region (Nether), and DIM1/region (End) folders. Each chunk inside an .mca file is a GZip or Zlib compressed Named Binary Tag (NBT) structure that uses Big-Endian byte ordering. Even though both editions have a root level.dat file, Bedrock prepends an 8-byte header to its uncompressed Little-Endian NBT, while Java simply GZip-compresses a standard Big-Endian NBT tree.

When you run the Java ↔ Bedrock Converter, the browser decompresses the LevelDB records, parses the binary keys to determine chunk coordinates and dimension IDs, and translates Bedrock block states (like minecraft:stone_block_slab) into their modern Java equivalents. Finally, it rebuilds the chunk palettes, converts the byte order from Little-Endian to Big-Endian, and packs the data into newly generated .mca region files and a valid Java level.dat.

Common mistakes

  • Leaving the downloaded world double-nested inside the saves directory (for example, saves/MyWorld/MyWorld/level.dat), which prevents Java Edition from detecting the save.
  • Uploading only the Bedrock level.dat file instead of the entire folder or .mcworld archive; without the db subfolder, no terrain or chunks exist to convert.
  • Opening the converted world in an older Java Edition version than the one selected in the tool, which causes Java's DataVersion check to reject or corrupt the chunks.
  • Expecting custom Bedrock Behavior Packs, Resource Packs, or Marketplace add-on entities to carry over, as Java Edition does not natively read Bedrock add-on scripts or geometries.

FAQ

Will my inventory and player data transfer over?

Local singleplayer data stored under the ~local_player tag in Bedrock's level.dat is translated into the singleplayer Player tag in Java's level.dat. However, multiplayer inventories frequently reset because Bedrock tracks guests by XUID while Java uses UUIDs, so it is always safest to place your items into a standard chest before exporting.

Why did some specific blocks or redstone machines change appearance?

While 99% of vanilla blocks have a direct 1:1 translation, a few mechanics differ fundamentally between editions—such as Bedrock's movable block entities or waterlogged leaves. The converter maps these to the closest valid Java block state to prevent your game from crashing.

Are my world files uploaded to the internet during conversion?

No. Our converter runs entirely client-side using your web browser's local memory and processors, meaning your world files never leave your computer.

Converting a Bedrock save to Java Edition is as simple as exporting your .mcworld file, translating its LevelDB database into Anvil .mca regions using our browser-based Java ↔ Bedrock Converter, and extracting the result into your Java saves folder.

More java ↔ bedrock conversion guides

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 conversionHow to Unpack, Edit, and Repackage Bedrock .mcworld ArchivesA 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.BedrockBeginner5 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