Upgrade a Minecraft world to a new version safely
Moving a world to a newer Minecraft version converts it permanently, so the order of operations matters. Back up, check your plugins and mods, test on a copy, and know where the new terrain will leave a seam.
6 min read · Updated Oct 21, 2026 · By GuavaHost Team
Back up first, and mean it
Take a snapshot on the Backups page before you change anything. Not after you have changed the version and it looked fine, before. Backups: creating, restoring and scheduling covers how, and off-site backups is the add-on if you want a copy that is not on the same machine.
For a copy on your own computer, open the Files tab, select your world folder and download it. Having the pre upgrade world in two places costs ten minutes and saves the project if the upgrade goes badly.
Why the upgrade is one way
Every chunk and every level file in a Minecraft world carries a data version, a number that says which release wrote it. When a newer server loads an older world it runs each chunk through a converter, updates the format and saves it back at the new number.
That rewrite is permanent, because there is no downgrade converter in the game. An older server opening a newer world will either refuse or load it and quietly mangle things, and neither is something you want to discover on a live world.
So the rule is simple: going up keeps your world, going back down means restoring the backup. That is the only reverse gear there is, and it is why you never roll a server back a version with the world still in place. Changing your Minecraft Java server version explains the Version page and what it does to your files.
Check your plugins and mods before you touch the version
This is where upgrades actually fail. The world usually converts fine; what keeps a server offline for a weekend is a plugin with no build for the new version.
On a plugin server (Paper, Spigot, Purpur), open the Files tab, list your plugins folder, and check each plugin for a build on the version you are moving to. Anything that has not been updated in a long time is a decision you make now, not later: "I will find a replacement eventually" is how servers stay broken. Plugins that store data, like permissions, land claims and economy, usually carry across fine, while plugins that touch world generation or block behaviour are the risky ones.
On a modded server (Forge, Fabric, NeoForge), be blunt with yourself: a modded world generally does not move between Minecraft versions. Every mod needs a build for the new version, and a missing mod takes its own blocks out of your world, which shows up as holes in your builds. On a modpack, the right move is almost always a fresh world on the pack's new version. Installing modpacks and installing Fabric or Forge mods cover the mechanics.
Check Java too. The version change in the panel handles most of it, but choosing a Java version lists which Minecraft version needs which Java if your server comes back with a Java error.
Test on a copy
You do not have to guess. Make a copy and upgrade that first.
Download your world folder from the Files tab, then set up a test server on the new version: a second GuavaHost server on a small plan, or one on your own computer. Upload the world there and set level-name to its folder, which uploading a Minecraft world covers step by step, install the new builds of your plugins, start it, and read the Console from the top. Every error there is one you would have had on your live server.
Then fly around your main builds and check your redstone, your farms and your chest contents. Spend twenty minutes on this and the live upgrade becomes boring, which is what you want from an upgrade.
Do the upgrade
- Take the backup, if you have somehow read this far without doing it.
- Stop the server with Stop and wait for Offline. Changing the version under a running server is asking for a half written world.
- Open the Version page under Minecraft tools and select the version and server type you want.
- Start the server and watch the Console. The first start after an upgrade is slower, because chunks are converted as they load.
- Join and look around spawn and your main base. Check your plugins loaded and your permissions still work.
- Leave it a day before you delete that pre upgrade backup.
If the server will not start, read the console from the first error rather than the last: reading server logs and crash reports covers how. If players get an outdated server or client message, that is a client version mismatch rather than a world problem, and fixing the outdated server message explains it.
Chunk conversion, and the seam new generation leaves
Two separate things happen to terrain, and people mix them up.
Conversion affects chunks that already exist, rewriting them into the new format. Your builds, chests and signs come across. Occasionally a chunk that was already subtly damaged fails to convert cleanly, which shows up as an error ticking that chunk: exception ticking world and corrupt chunks is the guide for that.
New generation affects chunks that do not exist yet. When a release changes world generation, new terrain follows the new rules and the boundary with the old is visible: cliff walls, biomes that stop mid forest, caves that end at a flat face. Releases that changed world height or cave generation produced the most obvious examples.
You have three honest options:
- Live with it. Walk out past the seam and the new world is fine. Most servers do this.
- Hide it. Put a world border just inside the explored area so nobody generates new terrain next to the old, which setting a world border and pre-generating chunks covers and which helps performance anyway.
- Delete the unexplored edge. Tools exist that trim chunks nobody has built in, so the new generation starts further out. That means editing world files, so take a backup and never do it on a running server.
What does not work is hoping the game will blend them.
Special cases worth knowing
- The Nether and the End are separate folders, usually
world_netherandworld_the_endon a plugin server. They convert the same way, and a generation change can leave a seam in them too. - Datapacks have a pack format number tied to the game version, so an old pack is rejected or ignored by a newer server. Installing datapacks covers checking them.
- Resource packs you force on players also have a format number, so update the pack if players suddenly see missing textures: forcing a resource pack covers the setting.
- Players on older clients cannot join a newer server, which is a different problem from the world. ViaVersion and cross version play is about making several client versions work at once.
- Never upgrade a world you care about to a snapshot. The format can change again before release.
Common questions
Can I go back to the old version after upgrading my world?
Not with the same world, because the chunk conversion is one way and the game has no downgrade path. You go back by restoring the backup you took before the upgrade, which is the only reason that step is not optional.
Will my builds and chests survive the upgrade?
Yes, in the normal case. Existing chunks are converted, so blocks, chests, signs and inventories come across intact, and the visible change is at the boundary with terrain that has not been generated yet. On a modded server a missing mod takes its own blocks out of your builds, which is a mod problem rather than a world one.
Do I have to upgrade at all?
No. A server on an older version keeps working, and plenty of communities stay put because their plugins and farms work. Upgrade when players want the new content, or when a plugin you rely on stops supporting your version.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.
- minecraft
- java
- version
- world
- upgrade
Host a Minecraft Java server From $3.99/mo, with instant setup and DDoS protection.
Still need help? Our team is online 24/7 to answer questions.