How to Update a Minecraft Server Without Losing Your World
Oct 18, 2026
Why updating can go wrong
A new Minecraft version is easy to install and easy to regret. Two things go wrong most often:
- The world can't go back. Once a newer version has opened and saved a world, an older version can't read it. There is no downgrade, only a backup.
- Mods and plugins are built for one version. A mod made for 1.21.1 often refuses to load on 1.21.4. The server then crashes on start, or starts without the mod and players find things missing.
So the safe order is always the same: back up, check every mod, update, start, and keep the backup until you are sure.
Before you change anything
- Stop the server and let it finish saving.
- Back up the world. Open the Backups page and press Back Up Now. Wait until it shows in the list. See how backups and restores work.
- Copy your mods or plugins folder somewhere safe. Backups cover the world; the files in
mods/orplugins/are what you reinstall if you go back. - Check each mod has a build for the new version. Search the mod's Modrinth page for the version you want. If a mod you rely on doesn't have one yet, the honest answer is to wait.
Updating by hand
Without any tooling, an update is a replacement of the server files with the world left in place:
- Download the new server jar (or run the new Fabric, Forge or NeoForge installer).
- Move the old jar aside instead of deleting it.
- Replace each mod or plugin with the build for the new version.
- Check the Java version. Newer Minecraft versions often need a newer Java. See fixing Java version issues.
- Start the server and read the console from the top, not only the last line.
It works, and it is also where people forget a step. Loader servers are the worst: Forge and NeoForge keep old versions under libraries/, and a leftover folder can make the server launch the wrong one.
Updating with Coalstack
Server Settings has an Upgrade Minecraft Version card on Coalstack Plus for Java servers. It does the steps above for you and keeps an undo until you say otherwise. It handles Vanilla, Paper, Fabric, Quilt, Forge and NeoForge servers. Purpur, Spigot, custom jars and Bedrock aren't supported yet, and the card says why.
- Stop the server, open Server Settings and pick a newer version. Only newer versions are offered.
- Read the check. Nothing is changed yet. Coalstack looks up each mod or plugin on Modrinth by its contents, so a renamed file still counts, and sorts them into four groups: works as it is, will be updated, no version for it yet, and not on Modrinth.
- Choose what happens to the awkward ones. Mods with no build for the new version are disabled by default (moved aside, not deleted). Mods Coalstack can't find on Modrinth are kept, because it can't tell whether they work.
- Upgrade. Coalstack takes a restore-tested backup first, and if that fails nothing is changed. It then downloads the updates, checks each against the checksum Modrinth publishes, and installs the new server. If a step fails, the file changes are undone for you.
- Start the server. It is left stopped so you decide when to start it.
Keep it, or undo it
After the upgrade the card offers Undo until you press Keep the upgrade. Play for a while first: join, walk around, test the mods that matter.
- Undo puts the old server files and mods back and restores the world from just before the upgrade. Anything players built since is lost, so decide early.
- Keep clears the undo files. The backup stays among your snapshots.
If the server won't start afterwards
An updated mod sometimes needs a library mod that wasn't installed before. Coalstack doesn't add those during the upgrade. If the server fails to start, Auto-fix downloads what is missing, and the error code reference explains the message in the console. If it still won't start, Undo gets you back to where you were.
Jars outside mods/ and plugins/, datapacks and resource packs aren't checked, so look at those yourself. The full reference is in the upgrade section of the docs.