How to Upgrade a Minecraft Java World to 26.1 or 26.2 Safely

Minecraft Java Edition 26.1 changed the directory layout used by saved worlds. The game still uses Anvil .mca region files, but dimensions, player records, maps and other saved data now live in different folders. Opening an established world therefore performs a real migration, even though Minecraft handles most of the work automatically.

This guide targets the stable Java 26.1 and 26.2 releases. As of August 3, 2026, 26.3 is still being tested through snapshots and 26.4 is not a released Java version. Never use a snapshot as the only copy of a world you care about.

What changed in the Java 26.1 world folder?

The main change is organization, not the replacement of Anvil with a new compression engine. After a successful migration, the default dimensions are stored beneath a common dimensions directory:

• The Overworld moves from the world root to dimensions/minecraft/overworld/.
• The Nether moves from DIM-1/ to dimensions/minecraft/the_nether/.
• The End moves from DIM1/ to dimensions/minecraft/the_end/.
• Each dimension keeps its related region, entities and poi data together.
• playerdata, advancements and stats move beneath players/.
• Maps, the scoreboard, command storage and several other files are reorganized into namespaced locations.

Do not move these folders by hand before the first launch. Let the target Minecraft version read the old layout, migrate it and save the new layout itself.

Choose the correct target version

For an important survival world, upgrade to the latest stable release supported by your mods, plugins and datapacks. Java 26.2 includes fixes that can make upgrades from versions before 26.1 faster, so it is the sensible stable target when the rest of the server stack supports it.

Pack versions must match the exact release. Java 26.1 uses data pack version 101.1 and resource pack version 84. Java 26.2 uses data pack version 107.1 and resource pack version 88.0. Do not replace a pack version with a guessed value such as “65+”.

Step 1: Audit the world before changing anything

1. Write down the current Minecraft version, mod loader, server software and Java runtime.
2. List every mod, plugin and datapack that can write world data.
3. Update them only to releases that explicitly support the target Minecraft version.
4. Start the old version one final time and check its log for existing datapack, registry or chunk errors.
5. Make sure the computer or server has enough free disk space for the original world, a complete backup and a separate test copy.

Fixing an existing error before migration is much easier than deciding whether the upgrade caused it afterward.

Step 2: Make a complete cold backup

In singleplayer, select the world, choose Edit, then choose Make Backup. Minecraft creates a ZIP in its backups directory. Keep that ZIP unchanged.

For an additional manual copy, close Minecraft completely and copy the entire world folder. On Windows, Java saves are normally under %APPDATA%.minecraftsaves. On macOS they are normally under ~/Library/Application Support/minecraft/saves, and on Linux under ~/.minecraft/saves.

For a dedicated server, stop the server cleanly and wait for the Java process to exit. Copy the complete world directory or every configured dimension directory. A live copy made while chunks are still saving is not a reliable backup.

Step 3: Create a separate migration copy

Extract or duplicate the backup under a different folder name, such as Important World 26.2 Test. Keep the original world and its backup outside the test workflow. When the Select World screen shows both entries, open only the clearly named test copy.

If the game asks for confirmation because the world was created in an older version, verify the selected name before continuing. The first load can take longer because Minecraft may move saved data and apply data fixes before writing the world again.

Step 4: Let Minecraft finish the migration

Do not force-close the game while the world is opening or while the saving indicator is active. Once the test copy loads, remain in the world for several minutes, save and quit normally, then open it a second time. A successful second launch is a useful check that the newly written layout can be read cleanly.

The Optimize World option can reprocess saved chunks in a copy, but it is not a substitute for a backup. Use it only after the normal migration works and only when you understand that it may take a long time on a large world.

Step 5: Verify more than the spawn area

A world reaching the title screen does not prove that every dimension and player record survived. Test a representative sample:

• Join with the expected player and confirm inventory, Ender Chest, position, advancements and statistics.
• Open ordinary chests, barrels, shulker boxes and containers holding named or component-heavy items.
• Read signs and books, inspect maps, armor stands, item frames and command blocks.
• Travel through an existing Nether portal and an End portal, then revisit old builds in all three dimensions.
• Load farms, villages and areas with many entities or block entities.
• Cross the edge between old terrain and newly generated chunks and look for missing sections or abrupt corruption.
• Run datapack functions and plugin features that store custom data.

On a server, read the full startup and shutdown logs. Search for data-fixer failures, unknown registries, missing dimensions, datapack validation errors and failed chunk reads. Do not ignore repeated warnings just because players can join.

Dedicated server migration

Build a staging server with a copy of the production configuration and the migrated world. Block public access while testing. Confirm that the proxy, permission system, economy, claims, inventories and cross-server data all behave normally before replacing the production world.

The vanilla server supports a documented --forceUpgrade option for processing existing chunks. Use it only on the staging copy and only with the options documented by the server implementation you actually run. Do not copy Paper, Fabric or cache-erasure flags from an unrelated guide. A normal upgrade is safer than an invented command line.

How to roll back safely

1. Close the upgraded game or stop the server completely.
2. Move the failed test copy aside rather than merging it with the backup.
3. Extract the untouched backup into the saves directory or restore the original server world folder.
4. Start it with the exact Minecraft, loader, mod and plugin versions recorded before the upgrade.
5. Verify the restored world before allowing normal play.

Never open the upgraded 26.1, 26.2 or snapshot copy in an older release and treat that as a rollback. Older versions cannot understand every newer block, entity, component or registry entry. Restore the pre-upgrade backup instead.

Testing a 26.3 snapshot

Snapshots are development builds. Create a third disposable copy, enable snapshots in the launcher and keep it separate from both the stable migrated copy and the original backup. Snapshot testing is useful for reporting compatibility problems, but a world that has entered a snapshot should not become the only production copy.

Frequently asked questions

Does Minecraft 26.1 replace Anvil region files?

No. The official change is primarily a reorganization of the saved-world directory and namespaced data. Region data still uses .mca files.

Can I skip 26.1 and open a 1.21 world in 26.2?

Generally yes, because the target release applies its data fixes and 26.2 includes upgrade improvements for some pre-26.1 worlds. Mods, plugins and datapacks still need their own compatible versions, so always test a copy first.

Why are my old DIM-1 and DIM1 folders gone?

After migration, the Nether and End are stored under dimensions/minecraft/. Confirm their contents in-game before deleting or reorganizing any leftover files.

Is 26.4 the current Minecraft Java release?

No. At the time this guide was updated, 26.2 was stable and 26.3 was in snapshot testing. Treat claims about a released 26.4 as unverified until Mojang publishes official release notes.

Version and storage details were checked against the official Java 26.1 release notes, Java 26.2 release notes and the current official snapshot changelogs.