How to Convert a Java World to Bedrock Format

Why Convert Worlds

Maybe you built an incredible survival world on Java Edition and want to continue it on your phone. Maybe you are migrating a Java server to Bedrock to reach console players. Whatever the reason, you can convert java world bedrock format with the right tools, though some manual cleanup is usually needed afterward.

Java and Bedrock use different world formats (Anvil vs LevelDB), different block IDs, different entity data and different chunk encoding. Conversion tools handle the heavy lifting, but no tool produces a perfect 1:1 copy. Understanding what changes and what breaks will save you time and frustration.

Choosing a Conversion Tool

Three tools stand out for this task in 2026:

• Chunker (chunker.app): Web-based, free, maintained by Hive Games. Upload your Java world as a zip, choose Bedrock as the output, and download the converted world. Handles most block mappings, biomes, and terrain. Best for quick conversions without installing software.
• Amulet Editor: Desktop application (Windows, macOS, Linux) with a GUI and command-line interface. Supports fine-grained control over chunk selection, block remapping, and entity conversion. Best when you need to convert only part of a world or fix specific issues.
• MCC ToolChest PE: Windows-only tool that has been around for years. Converts worlds, edits NBT data, and manages inventories. Interface is dated but functional.

Preparing Your Java World

Before you convert java world bedrock format, clean up the source world:

• Remove unnecessary chunks. The smaller the world, the faster and more reliable the conversion. Use a tool like MCASelector to delete chunks outside your build area.
• Update the world to the latest Java version. Conversion tools work best with current format versions. Open the world in the latest Java Edition client and let it upgrade all chunks.
• Back up everything. Keep an untouched copy of the original world folder before converting.

Converting with Chunker

Chunker is the fastest path for most players:

1. Zip your Java world folder (the one containing level.dat).
2. Go to chunker.app and upload the zip.
3. Select the output edition (Bedrock) and target version.
4. Click convert and wait. Large worlds (several GB) may take 10 to 20 minutes.
5. Download the output, which is a .mcworld file you can open directly on Bedrock clients or extract into a server's worlds folder.

Host any Bedrock or crossplay server with zero config headaches. Astroworld Hosting supports Geyser, BDS, and every server type on every plan.

Converting with Amulet

Amulet gives more control when you need it:

1. Install Amulet from amuletmc.com.
2. Open your Java world in Amulet.
3. Use File, Save As, and select Bedrock as the output format.
4. Choose the Bedrock version that matches your target server or client.
5. Click save and let the conversion run.

Amulet also lets you select specific chunks to convert, remap blocks manually, and inspect individual blocks for errors after conversion. Use the 3D viewer to spot obvious issues before loading the world in-game.

What Converts Cleanly

• Terrain and biomes: Most overworld, nether and end terrain converts without issues. Biome data maps well between editions.
• Standard blocks: Stone, wood, ores, glass, wool and most building blocks convert perfectly.
• Chests and inventories: Items inside chests usually survive conversion, though some Java-only items may become unknown or be removed.

What Breaks or Changes

When you convert java world bedrock format, expect these issues:

• Redstone: Java and Bedrock have different redstone mechanics. Complex contraptions (zero-tick farms, quasi-connectivity designs) will not work on Bedrock without redesigning them.
• Command blocks: Commands use different syntax between editions. All command blocks need manual rewriting.
• Java-only blocks: Blocks that exist only in Java (e.g., certain fence gate states, waterlogged stairs in specific orientations) may convert to their closest Bedrock equivalent or become air.
• Entities: Mob AI, attributes and NBT data differ significantly. Villager trades, named mobs and leashed animals may lose their data. Armor stands may lose poses.
• Banners and maps: Custom banner patterns sometimes lose layers. Map art may need to be recreated.
• Player data: Player inventories, positions and achievements do not transfer. Players start with empty inventories in the converted world.

See crossplay in action: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.

Post-Conversion Cleanup

After loading the converted world on Bedrock, walk through your builds and check for:

• Missing or replaced blocks (look for barriers, air gaps or placeholder blocks)
• Broken redstone circuits
• Missing entities (villagers, item frames, armor stands)
• Lighting glitches (Bedrock recalculates light, which can take time on large worlds)

Fix issues manually in-game or use Amulet to batch-replace problem blocks. If you are running a server, do this cleanup before opening to players.

Going the Other Direction

All three tools also support Bedrock-to-Java conversion. The same caveats apply in reverse. For a broader comparison of the two editions, including world format differences, see our Java vs Bedrock guide.