What exactly are region/.mca files

region/.mca files are what Minecraft Java Edition uses to store the bulk of a world’s data. The game doesn’t cram the entire world into one big file; instead it manages it in chunks:

  • A chunk is a 16x16 unit of the world. World data is generated, loaded, and saved chunk by chunk.
  • Every 32x32 chunks (one “region”) is packed into a single file, with a name like r.0.0.mca or r.-1.2.mca — the r stands for region, and the two numbers are that region’s coordinates.
  • These files all live in the world save’s region/ folder, storing blocks, entities, block entities, and other data internally in NBT (Named Binary Tag) binary format.

So the region/r.x.z.mca files you see aren’t corrupted — they’re a normal part of a Java world. The more you explore and the larger the world grows, the more and larger the .mca files in region/ become — which is the main reason Java world saves grow in size. To learn about the overall location and structure of a world folder, see where Minecraft saves are stored.

Why this relates to “won’t open / import failed”

Understanding where .mca files sit is useful, because many “world won’t open” cases are actually structure-level problems rather than the .mca files themselves being broken:

  • For a Java world to be recognized correctly, level.dat must be in the save’s root directory, and the region/ folder must be at its proper level too. As soon as an extra folder layer gets wrapped around them, the game can’t find the world.
  • These kinds of file / packaging / structure issues can be diagnosed by TopoBlocks on-device by default, for free: it reads the directory hierarchy, level.dat, region/, and other structures, and tells you where the problem is. Simple structure fixes (such as removing an extra outer layer or moving files back to the correct level) are free, produce a new file that imports normally, and never overwrite your source files — the original version is always preserved for traceability.
  • To be honest about it: structure diagnosis/repair only solves file-level problems. If a crash is caused by non-file reasons such as incompatible mods, a mismatched game version, or insufficient device memory, a structure fix won’t help, and you’ll need to troubleshoot the specific cause.

How region/.mca differs from Bedrock’s db/

This is the easiest place to trip up: Java and Bedrock world formats simply aren’t interchangeable.

  • Java Edition: world data lives in the .mca files inside region/ (NBT binary).
  • Bedrock: world data lives in a LevelDB database inside the db/ folder, and the files look completely different. To learn how Bedrock stores it, see what Bedrock’s db/ (LevelDB) is.

Because the underlying formats differ, you cannot drop Java’s region/.mca straight into Bedrock, nor the other way around. To play the same map across editions, you need a format conversion — and TopoBlocks only supports Java -> Bedrock one-way; Bedrock can’t be converted back to Java. You get a compatibility score before converting, it’s paid per job with automatic refunds on failure, and prices are shown in-app. For a full comparison of the two formats, see how Java and Bedrock world formats differ.