Three dimensions, one save

A lot of people assume the “Nether” and “End” are separate saves, but in reality a single Minecraft world packs all three dimensions—Overworld, Nether, and End—into one world file, sharing the same level.dat metadata (name, seed, spawn point, and so on). The difference is how each edition organizes them:

  • Java Edition keeps them in separate folders: the Overworld in region/, the Nether in DIM-1/, and the End in DIM1/. Each folder holds r.x.z.mca chunk files split by region (NBT binary). To learn more about these .mca files, see What is a chunk.
  • Bedrock has no such folder split—instead it writes every dimension into the same db/ (LevelDB), relying on an internal “dimension identifier” in each chunk record to tell whether it belongs to the Overworld, Nether, or End.

So the “Nether/End” isn’t a separate file—it’s the part of the same world that’s tagged and stored separately. To find out exactly where these saves live on your device, see Where are Minecraft saves.

Dimension data keeps accumulating as you explore

Dimension data is only written once you’ve been there: the first time you enter the Nether or reach the End, the corresponding chunks are generated and saved. That’s why it’s normal for your world file to grow after visiting the Nether or End—just like the Overworld, it keeps accumulating explored chunks. It also means a world that has never visited the Nether may have no DIM-1/ folder or Nether chunk data at all, and that does not mean the save is corrupted.

Dimensions and “the world won’t open”

Sometimes a world fails to import or throws a load error because some dimension’s chunk data is missing or corrupted (for example, the End portion can’t be read). You can check this with TopoBlocks’s free on-device diagnosis: it reads the save structure, verifies whether each dimension is readable and complete, and tells you exactly where the problem is. By default the diagnosis runs on your device and nothing is uploaded.

If the issue turns out to be at the file/packaging/structure level, a simple structural repair produces a new, properly importable world file and never overwrites your original—the original version and its hash are both preserved and traceable. Complex corruption goes through advanced repair (¥9 per run; before paying, you see the problem, the success likelihood, the risks, and the refund terms, with the price as shown in the App).

To be honest about the limits: structural diagnosis and repair only solve file, packaging, and structure problems. They can’t fix crashes caused by non-file issues like mod conflicts, version incompatibility, or insufficient device memory. For more troubleshooting approaches, see What to do when a world won’t open.