Updating Your Server to a New Minecraft Version Safely

A new Minecraft version arrives, players want it immediately, and the temptation is to swap the server JAR and restart. That’s how worlds get corrupted, plugins break and communities lose weeks of progress. Updating safely isn’t hard — it just follows an order. This guide walks through it.

Rule one: world upgrades are one-way

When a newer version loads your world, it converts chunks to the new format. Older versions can’t read upgraded chunks. If the update goes badly and you haven’t kept a backup, you can’t simply go back. Everything else in this guide follows from that fact.

Step 1: Wait for the ecosystem

On release day, your server software and plugins usually aren’t ready.

• Paper typically publishes experimental builds soon after a release, then stable builds once the team is confident. Wait for builds that aren’t marked experimental for a production server.
• Plugins need their own updates. Big plugins update quickly; smaller ones may take weeks or never update.
• Modpacks often take much longer, since every mod must update.

Check each plugin’s page (Hangar, Modrinth, SpigotMC) for support for the new version. Make a list: updated, not yet updated, abandoned. If an essential plugin isn’t ready, wait — or plan a replacement.

Step 2: Check the Java version

New Minecraft versions sometimes raise the minimum Java version. Minecraft 1.20.5 and newer require Java 21; 1.18 to 1.20.4 need Java 17. If your server runs an older Java, update it as part of the upgrade, or the new server JAR won’t start.

Step 3: Back up everything

Take a full backup immediately before updating:

• all world folders,
• the plugins/ folder (configs and data),
• server configuration files,
• any databases your plugins use.

Keep this backup until you’re sure the update is stable — at least a couple of weeks. See Minecraft server backups.

Step 4: Test on a copy

This is the step people skip and regret. Set up a copy of your server with the backup:

1. Put the new server JAR and updated plugins on the copy.
2. Start it and read the console carefully — plugin errors, warnings and deprecation notices all appear here.
3. Join and check: spawn, player homes and claims, economy balances, permissions, shops, and anything custom.
4. Explore a little and watch performance with spark.

Problems found on the copy cost nothing. Problems found on production cost your players’ trust.

Step 5: Tell your players

Announce the update ahead of time: when it’s happening, roughly how long the server will be down, and which client version players should use afterwards. Mention anything that’s changing — removed plugins, reset areas, new features.

Step 6: Update production

With the copy working:

1. Stop the server.
2. Take one more backup (a final snapshot right before the change).
3. Replace the server JAR and update plugins to the versions you tested.
4. Update Java if needed.
5. Start the server and watch the console.
6. Join and run the same checks you did on the copy.

What happens to existing chunks

Existing terrain keeps its shape after an upgrade. New biomes, structures and terrain features from the update only appear in newly generated chunks. Players who want to see new content need to explore beyond the areas already generated.

If you pre-generated your world inside a border, the new features won’t appear anywhere players can reach. Common approaches:

• Expand the world border and pre-generate the new ring, so fresh terrain includes the new content.
• Add a new resource world that gets reset each version.
• Reset specific regions far from builds, using a region editing tool, after backing up.

See pre-generating your world with Chunky.

Force-upgrading chunks

Chunks are normally converted as they’re loaded. You can start the server once with --forceUpgrade to convert every chunk up front. It takes a while on large worlds, but avoids conversion work later during play. Do this only on a backed-up world.

Letting older clients connect

If some players can’t update immediately (or you want to update the server later than players update clients), ViaVersion lets newer clients connect to an older server. ViaBackwards and ViaRewind do the reverse for older clients. They’re useful bridges, but mismatched versions can cause visual oddities and gameplay differences — treat them as a convenience, not a long-term plan.

When a plugin isn’t ready

• Wait, if the plugin is essential and actively maintained.
• Replace it with an updated alternative that does the same job.
• Remove it, if the feature isn’t critical — but check what data it held.
• Don’t force old plugins onto new versions and hope. They may work, fail silently, or corrupt data.

If something goes wrong

1. Stop the server before more players change anything.
2. Read the console and logs for the first error.
3. If you can’t fix it quickly, restore the pre-update backup — worlds, plugins, configs and databases together — and go back to the old version while you investigate on a copy.

That’s why the backup matters: a failed update becomes an hour of downtime rather than a lost world.

Modded servers

For modpacks, update only when the pack itself releases a version for the new Minecraft release. Mod and world changes can be significant — items from removed mods disappear from the world — so read the pack’s changelog, back up, test on a copy, and make sure players update their client pack to match. See installing a modpack on your Minecraft server.

Hosting help

On Kerit Cloud’s Minecraft hosting, every server has daily automated backups plus full panel access for manual backups before updates, and 24/7 Discord support can help with version and plugin questions.

Summary

World upgrades are one-way, so update in order: wait for stable server builds and plugin support, check the Java version, back up everything, test the update on a copy, tell players, then update production and verify. Expect new features only in newly generated chunks, use ViaVersion as a temporary bridge, replace plugins that won’t update, and keep the pre-update backup until you’re sure the new version is stable.