How to Update Your Minecraft Server
Updating a Minecraft server is a ten-minute job when it goes right — and a week of corrupted-chunk debugging when it goes wrong. The difference is a backup taken before you start, and updating plugins at the same time as the jar. Here's the safe path.
The golden rule
Back up, then update everything at once. The server jar, every plugin (or the whole modpack), and the configs move together as one unit. Booting a new Minecraft version with a single old plugin is the most common way an update turns into a crash loop.
Step by step
1.Back up everything first
Full backup of the world, plugins/configs, and server.properties. This is the only step that's truly non-negotiable. If anything below goes wrong, the backup is your rollback path. On a panel host, hit the backup button; self-hosted, use your normal snapshot routine.
2.Check what depends on the old version
List your plugins (or mods) and check each one's compatibility with the target version. For Paper servers, plugins usually publish a per-version build. For modded, check the modpack's own version list — the pack author handles mod compatibility for you, which is the main reason to update the pack rather than individual mods.
3.Download the new server jar
Vanilla: get the new jar from minecraft.net. Paper: the latest build from Paper's site. Forge/NeoForge: run the new installer with --installServer. Fabric: download the new loader. On a panel host this is a dropdown — pick the version and the panel swaps the jar.
4.Update plugins and mods at the same time
Swap in the new plugin jars (or the new modpack version) alongside the server jar. The cardinal rule: never boot a new Minecraft version with old plugins. Every post-update crash I've debugged traces back to one plugin that was one version behind.
5.Boot and watch the first load
The first boot of a new version converts the world — expect it to take longer than a normal start (minutes on a big world). Watch the console for conversion errors and plugin load failures. If a plugin fails to load, stop and fix it before players join; a server running with a missing plugin has silently missing functionality.
6.Verify, then let players in
Join yourself, fly around spawn, check a few builds and inventories, confirm commands and plugins respond. Only then announce the update. If anything's off, restore the backup and try again — a clean rollback beats a week of 'why is the end reset?' bug reports.
World conversion: the part that scares people
When you boot a newer Minecraft version on an old world, the game converts the chunk format forward automatically. The conversion happens once, writes every loaded chunk, and — critically — there is no undo. If it's interrupted (power loss, OOM kill), the world can be left half-converted.
This is why the backup-first rule is absolute: the backup is your undo. It's also why you shouldn't jump multiple major versions at once (1.18 → 1.22) — convert step by step, booting in between, so each conversion is smaller and any problem is easier to isolate. And give the first boot time — a big world converting to a new format can take several minutes before players can join.
Modded servers: update the pack, not the mods
For a modpack server, resist the urge to hand-update individual mods. Modpacks ship with a tested combination of mods, configs and scripts; a version bump changes all of them together. Update the pack version through your launcher or panel, and the installer handles the rest — the loader version, the mod set, and the config changes as one unit.
One exception: if you're on a pack the author has stopped updating, you may need to hand-patch a mod for a security fix. In that case, change only that one mod and back up first — and accept you're now off the tested path.
FAQ
Do I need to reset my world to update Minecraft?+
Usually no — Minecraft converts worlds forward automatically when you boot a newer version. But the conversion only runs once, and it rewrites chunk data to the new format. Always back up first: if the conversion fails halfway, the world is left in a broken state, and the backup is your only way back.
Will my plugins still work after updating?+
Not necessarily. Plugins are built for a specific Minecraft version (or a range). After an update, check each plugin's page for a compatible build and update them all at the same time as the server. Booting a new Minecraft version with old plugins is the #1 cause of post-update crashes.
How do I update a modpack?+
Update the pack version through your launcher or panel — the installer pulls the new mod set and loader version together. Don't hand-edit the mods/ folder. Modpacks change mods, configs and scripts between versions, and a manual patch will leave orphans that crash on boot.
What if the update breaks something?+
Roll back. Restore the pre-update backup (world + configs + plugins) and the previous server jar, then boot. This is exactly why the backup-first step is non-negotiable — a rollback is a five-minute restore instead of a week of debugging a corrupted world.
Should I update immediately when a new version drops?+
For vanilla, you can usually update right away. For modded servers and servers with many plugins, wait a week or two — plugin authors and mod developers need time to release compatible builds. Updating a modded server on day one means booting with a half-broken mod set.
Updates with automatic backup and rollback
CoalHost snapshots your server before version changes and restores in one click if the update goes sideways.
View Minecraft Hosting →