The Core Difference: Two Different Storage Formats

Java Edition and Bedrock are both called Minecraft, but the way world files are stored on disk is completely different:

  • Java Edition — packs chunks by region into region/r.x.z.mca files, internally a NBT (Named Binary Tag) binary structure; metadata like level.dat is also NBT.
  • Bedrock — stores the entire world’s chunks, blocks, entities, and other data in a LevelDB database inside a db/ directory (a collection of .ldb/.log files).

In other words, one “slices the world into .mca files by region,” while the other “stuffs everything into a key-value database.” To dig deeper into each, see What is Java’s region/.mca file and What is Bedrock’s db/ (LevelDB).

What the Format Difference Means

Precisely because the underlying structures differ, worlds can’t be moved directly between editions — you can’t copy Java’s region/ folder into Bedrock and expect it to open, and vice versa. Each game only recognizes its own format and can’t read the other’s data.

To move a world between editions, the only option is a format conversion that maps chunks, blocks, containers, structures, and so on one by one into the target format. And this comes with a direction limit of its own: TopoBlocks only offers verified one-way Java Edition to Bedrock conversion, and Bedrock can’t be converted back to Java. For the overall differences between the two editions in gameplay and ecosystem, see What is the difference between Java Edition and Bedrock.

Want to Convert or Troubleshoot Import Issues

If you just want to confirm which format your world is in, or figure out why an import failed, TopoBlocks diagnoses free on-device — the file type, version, and structure — after you open a .mcworld/.zip/Java world. By default it doesn’t upload anything and never overwrites your source files.

If you really do need to bring a Java world over to play on Bedrock, follow Java to Bedrock conversion: the conversion does not promise to be “100% lossless” — terrain, the vast majority of blocks, containers, and structures usually migrate, while Java-exclusive entities, behavior/resource packs, some redstone and command block behavior, and player data may be replaced with compatible equivalents or moved into the itemized report. You see a compatibility score before paying and get an itemized change report when it’s done, with automatic refunds on failure. Prices are shown in the app.