Minecraft Updating a Minecraft Java server means swapping the server jar for a newer build, then confirming your plugins and mods still work on it. Take a backup before you start, because a world that has been opened on a newer version can not be reverted.
Before you update
- Wait for your server software. Spigot, Paper, Forge, and Fabric do not release on the same day Mojang does. Expect at least a couple of weeks for a stable build.
- Then wait for your plugins and mods. They can only update after the loader they depend on does, so allow a few more days on top of that. Datapack timelines vary a lot more.
- Back up your world. This is the step people skip and regret.
Plugin/Mod Updates
Check every plugin and mod your server uses for support on the version you are moving to. The download page is the fastest way to tell: if the author has released an update or widened the supported versions, download the new file and swap it out on your server. If the page has not changed, you will have to test it on a local server or during the update itself.
Updating Server Software
Option 1: the Edition Installer
The Edition Installer is the easiest path and covers Spigot, Paper, Forge, NeoForge, Fabric, and Vanilla. In the Game Control Panel sidebar, open Advanced > Server Actions, then use Install a Different Edition to pick your software and version.
It carries stable releases, so a brand new or experimental version may not be listed yet. If yours is missing, use Option 2.
Option 2: upload the jar yourself
Download the jar for your server software:
| Software | Where to get the jar | Issue tracker |
|---|---|---|
| Paper | The Paper downloads page. The latest stable build shows first, and experimental builds sit behind a banner asking if you’re looking for 1.XX.X. | GitHub Issues |
| Spigot | Spigot has no direct download. Build the jar yourself with Build Tools. Spigot tends to release slightly ahead of Paper, though we recommend Paper for its performance. | Issue Tracker |
| Forge / NeoForge | See Installing Forge and NeoForge, which covers versions the installer doesn’t list. | Forge, NeoForge |
| Fabric | See Installing Fabric, which covers versions the installer doesn’t list. | GitHub Issues |
| Vanilla | The bottom of the release announcement, normally under “Get the Release” > “Cross-platform server jar”. Read the Vanilla caveats first. | Issue Tracker |
Installing the jar works the same way for every one of them:
Stopyour server, then upload the jar to your server’s root directory (the first place you see when opening the File Manager) using SFTP or the File Manager.- Set the Server Jar File server option to the exact file name you uploaded, then
Startthe server. - Watch the console for errors from your plugins and mods. Once the server is up, join and test your plugins, datapacks, and configurations before opening it to the public.
Vanilla
The Vanilla server software is the way to play on release day, but it comes with real trade-offs:
- It lacks the performance work done by community developers, so it may crash more often than even an unconfigured Spigot/Paper server, especially when generating new chunks.
- Paper often adjusts the DFU (Data Fixer Upper) to perform better and fix minor bugs. We recommend waiting for Paper for this reason among others.
- Your server-side mods and plugins won’t run until you switch back to software that supports them. Datapacks still work if they’ve been updated.
- You can move a Spigot/Paper world onto Vanilla, but files need shifting around first. See Spigot to Vanilla world formats. You can switch back once Paper/Spigot release.
- If a Forge/Fabric server had mods that added items, blocks, or entities, you can not switch to Vanilla without losing that data and risking world corruption.
Frequently Asked Questions
Yes. Updating swaps the server software, it does not delete your world. Take a manual backup first anyway, because the update itself converts the world to the new format.
No. Once a world has been opened on a newer version it can not be reverted. Restoring a backup taken before the update is the only way back.
No. If the installer does not list the version you want, download the jar yourself, upload it to your server's root directory, and point the Server Jar File option at it.
Yes, with ViaVersion. See our ViaVersion article for setup.