
World file format explained · Java · Intermediate
The Minecraft 26.x World Folder Layout: How the New dimensions/ Directory Works
Minecraft Java Edition 26.x introduces a major structural overhaul to save folders by retiring the legacy DIM-1 and DIM1 directories alongside root-level Overworld data. All vanilla and custom dimensions now live inside a unified dimensions/ directory organized by namespace. This guide explains the logic behind the new layout and shows you how to safely inspect, migrate, or reset dimensions using our browser-based tools.
What you need
- A Minecraft Java Edition 26.x world folder or .zip archive
- A modern web browser to run the local world tools (your files remain on your device and never upload)
- A complete backup copy of your world folder before moving or editing any files
Step by step
1Back Up and Inspect Your World Version
Before making any changes to your save files, duplicate your entire world folder or compress it into a backup .zip file. Open our NBT Inspector tool and choose Open world folder or .zip -> level.dat. Expand the Data compound tag and inspect the Version sub-compound to confirm the Name tag reads 26.x (you can also check the exact DataVersion integer here, as it varies by specific 26.x sub-release).
Tip: Never modify region files while the world is simultaneously open in the game client.
2Locate the New dimensions/ Hierarchy
In your world folder, look for the root dimensions/ directory. Unlike older versions where Overworld chunks sat directly in the root region/, poi/, and entities/ folders, 26.x moves all three vanilla dimensions into dimensions/minecraft/. Inside dimensions/minecraft/, you will find individual folders named overworld/, the_nether/, and the_end/, each containing its own region/, entities/, poi/, and data/ subfolders.
Tip: If you use data packs or mods that add custom dimensions, they follow the same pattern under dimensions/<namespace>/<dimension_name>/.
3Verify Migrated Chunks in the Region Map
When you open an older world in 26.x, the game automatically moves files from the root folders, DIM-1, and DIM1 into their respective dimensions/minecraft/ paths. To verify a clean migration, open our Region Map & Pruner tool and select Open world folder or .zip -> dimensions/minecraft/overworld/region. Confirm your builds appear on the grid, then switch the active directory to dimensions/minecraft/the_nether/region and dimensions/minecraft/the_end/region to check your other dimensions.
4Clean Up Leftover Legacy Directories
Sometimes interrupted upgrades or manual file merges leave empty or duplicate legacy DIM-1, DIM1, or root region/ folders behind. Compare the modification timestamps and file counts between the legacy folders and the new dimensions/minecraft/ subfolders. Once you confirm through the Region Map & Pruner tool that all active .mca files are present in the new namespace paths, you can safely delete the old empty DIM-1 and DIM1 directories to keep your save tidy.
Tip: If both the legacy folder and the new 26.x folder contain .mca files with the same region coordinates (such as r.0.0.mca), load each into the Region Map & Pruner first to see which one holds your most recent progress.
5Reset a Dimension Using the New Path
Resetting the Nether or the End is much cleaner under the 26.x layout because every dimension is completely self-contained. To reset the Nether completely, simply delete or rename the dimensions/minecraft/the_nether/ folder while the game is closed. If you only want to prune specific explored areas while keeping your Nether hub, use our Region Map & Pruner tool via Open world folder or .zip -> dimensions/minecraft/the_nether/region, select the unwanted region tiles, and export the cleaned folder.
How it works
For over a decade, Minecraft Java Edition used an inconsistent folder hierarchy for world saves. The Overworld stored its region/, entities/, and poi/ folders directly in the root of the save directory, while the Nether and the End used hardcoded legacy folders named DIM-1 and DIM1 based on ancient numeric dimension IDs. When custom dimensions were introduced in 1.16, they were placed inside a new dimensions/<namespace>/<dimension_name>/ structure, leaving vanilla worlds split across two completely different storage conventions.
Minecraft 26.x unifies this system by treating the three vanilla dimensions identically to data-driven dimensions. Every dimension now resides under dimensions/<namespace>/<path>/, which means the Overworld is explicitly defined at dimensions/minecraft/overworld/, the Nether at dimensions/minecraft/the_nether/, and the End at dimensions/minecraft/the_end/. Each of these dimension folders acts as a self-contained unit housing its own terrain chunks (region/), entity storage (entities/), points of interest like villager job sites and portals (poi/), and dimension-specific data trackers (data/, such as raids.dat).
Global world state that applies across all dimensions remains in the root directory of the world save. This includes level.dat (which holds the world seed, game rules, and WorldGenSettings), player inventories in playerdata/, advancement and statistic JSON files, and global data storage in the root data/ folder (such as scoreboard.dat and map items). By separating global metadata from dimension-specific chunk storage, the game engine avoids path special-casing and makes dimension management much more predictable.
Common mistakes
- Deleting the root data/ folder when trying to reset the Overworld; the root data/ folder holds global scoreboards, command storage, and filled map files for the entire server, not just the Overworld.
- Dropping downloaded region (.mca) files into the root of the world folder instead of dimensions/minecraft/overworld/region/, causing the game in 26.x to completely ignore them and generate fresh terrain.
- Restoring a pre-26.x backup of DIM-1 directly into a 26.x world folder without moving its contents to dimensions/minecraft/the_nether/, which results in the restored Nether never loading.
- Editing or moving files inside dimensions/ without creating a full backup first, or while the world is actively paused in singleplayer.
FAQ
Why are there still files in the root data/ folder if dimensions have their own data/ subfolders?
The root data/ folder stores global information shared across the entire save, such as maps (map_#.dat), scoreboards, and command storage, while the data/ folder inside a specific dimension only tracks events bound to that dimension, such as active village raids.
What happens if I open a 26.x world in an older version of Minecraft?
Downgrading is unsupported and dangerous; older versions do not look inside dimensions/minecraft/overworld/ for Overworld chunks, so an older game version will treat the world as empty and generate brand-new terrain in the root folder.
Where are custom data pack dimensions stored in 26.x?
They remain in the exact same place as before: dimensions/<your_namespace>/<dimension_id>/, right alongside the dimensions/minecraft/ folder.
The Minecraft 26.x world layout replaces the legacy root Overworld folders, DIM-1, and DIM1 with a unified, self-contained dimensions/minecraft/ namespace hierarchy for cleaner file management.