Minecraft: Java EditionHow to Update a Minecraft Server to a New Version (2026)
Update a Minecraft Java server to 26.3 or any new version without losing the world: back up, swap the jar, update plugins and mods, and never downgrade.
Updated Oct 3, 2026 · 6 min read
On this page
- What you can change on an existing world vs what needs a new world
- What is the current Minecraft version?
- Step 1: Back up first
- Step 2: Check plugins and mods support the new version
- Step 3: Install the new server jar
- Step 4: Replace plugins and mods
- Step 5: Start once and read the console
- The gotcha: the world upgrade is one way, and 26.1 moved the folders
- Common problems after updating
- Updating on GamezServers
- FAQ
To update a Minecraft server, stop it, back up the whole server folder (above all world/), replace server.jar with the new version's jar (vanilla from minecraft.net, Paper from papermc.io, or the matching Fabric, Forge or NeoForge installer), then update every plugin or mod to a build for that version and start it. The world upgrades itself on first load, and that upgrade is one way: an older version cannot open it again.
What you can change on an existing world vs what needs a new world
| Change | Existing world? |
|---|---|
| Update to a newer release (26.2 to 26.3, 1.21.11 to 26.1) | Yes, the world upgrades on first load |
| New biomes and structures from the update | Only in chunks generated after the update. Explored land stays as it was |
| Go back to an older version | No. Restore the backup you took before updating |
| Plugins and mods | Only builds made for the new version. Old ones fail to load or crash the server |
| Data packs | Often need an update when the pack format changes (it jumped to 121.0 in 26.3) |
| Snapshots and pre-releases | Possible, but a world opened in a snapshot may never load in a release again |
The second row surprises people most. Updating does not add new features to land you already explored. Players find new biomes and structures by travelling into fresh chunks, or you reset the world if the group wants everything new.
What is the current Minecraft version?
As of October 2026, Java Edition 26.3 Wilderness Bound is the newest release, out since 15 September 2026 (Minecraft.net). Every 26.x release runs on Java 25. Paper builds for 26.3 are still marked beta, while Paper 26.2 has stable builds. Our Minecraft 26.3 server update guide covers what changed in detail.
Step 1: Back up first
Stop the server with stop so every chunk is saved, then copy the whole server folder somewhere safe. The parts that matter most:
| File or folder | What it holds |
|---|---|
world/ (or your level-name) |
The world, player inventories in playerdata, advancements and stats |
world_nether/, world_the_end/ |
The Nether and End on Paper servers older than 26.1 |
plugins/ or mods/ |
Plugins with their configs and data, or mods |
config/ |
Mod configs, and Paper's paper-global.yml |
server.properties, ops.json, whitelist.json, banned-players.json |
Settings, operators, whitelist and bans |
This backup is your only way back. Keep it until you have played on the new version for a few days.
Step 2: Check plugins and mods support the new version
Before touching the jar, open the download page of every plugin or mod you rely on (Hangar, Modrinth, SpigotMC or CurseForge) and check for a build that lists the new version. If a key plugin has nothing yet, wait. A server without its permissions or claims plugin is worse than a server one version behind.
Modpacks are stricter still. A CurseForge or Modrinth pack is built for one Minecraft version, so a modded server should stay on the pack's version until the pack author releases an update.
Step 3: Install the new server jar
How you get the new version depends on the server type:
- Vanilla: download the new
server.jarfrom minecraft.net and replace the old one. - Paper or Purpur: download the newest build for the new version and replace the jar. Paper often needs days or weeks after a release before builds leave beta.
- Fabric: run the Fabric installer for the new version, and update Fabric API along with your mods.
- Forge or NeoForge: run the installer for a loader build that matches the new Minecraft version. Most content mods are not cross version.
Then check Java. Minecraft 26.1 and newer need Java 25, and Java 21 is enough for 1.20.5 to 1.21.x. Too old a Java stops the server with UnsupportedClassVersionError.
Step 4: Replace plugins and mods
Delete the old plugin or mod jars and put the new versions in plugins/ or mods/. Keep each plugin's config folder unless its update notes say to regenerate it. Do not leave two versions of the same jar in the folder, because the server loads one at random and you may get the old one.
Step 5: Start once and read the console
Start the server and watch the console from the first line. The first start on a new version upgrades every loaded region and can take much longer than usual on a big world. Do not stop it halfway through. Look for:
- plugins that failed to enable,
- mods reporting missing dependencies,
- data pack errors after the world loads.
Join, check your base, spawn and Nether portal, then tell your players to switch to the new version in their launcher.
The gotcha: the world upgrade is one way, and 26.1 moved the folders
Every Minecraft version can read worlds from older versions, but none can read worlds from newer ones. The moment the new server saves your world, the old version can no longer load it. If a plugin turns out to be broken, rolling the jar back does not help: you need the backup from Step 1, and anything built since is lost.
Updating from 1.21.x to 26.1 or newer adds a second trap. Minecraft 26.1 moved each dimension into world/dimensions/minecraft/ (overworld, the_nether and the_end), and Paper 26.1 followed by retiring the separate world_nether and world_the_end folders (PaperMC, 26.1). After the upgrade, region files are no longer where old scripts, map renderers and backup tools expect them. PaperMC states plainly that an upgraded world cannot be downgraded. Back up before you cross that line, and check any external tool that reads world files.
Common problems after updating
- "Outdated server!" for some players: they are on a newer version than the server. Finish the update, or see the outdated server and outdated client fix.
- Server stops with
UnsupportedClassVersionError: Java is too old for the new version. 26.x needs Java 25. - Plugin commands stopped working: the plugin failed to enable on the new version. Check the console on startup and update it.
- Nobody can join a brand new 26.3 server: since 26.3 a freshly created
server.propertieshas the whitelist on. Runwhitelist add <name>orwhitelist off. - New biomes are nowhere to be found: they only generate in new chunks. Explore unvisited land.
Updating on GamezServers
On a Minecraft server from GamezServers, click Backup, then in Settings set Minecraft version to the new version (or leave it on latest) and press Update game. The server for your type is installed again, and your world, plugins, mods and configs stay. New servers already run Java 25. If you want to try a new version on a copy first, download a backup from the file manager before you update.
FAQ
Will updating my Minecraft server delete my world?
No. The world upgrades to the new version on first load. It cannot go back to the older version afterwards, so back up first.
How do I update a Paper server?
Back up, download the newest Paper build for the new version, replace the jar, update your plugins and start. Wait until your key plugins support the version.
Do players need to update too?
Yes. Players need the same version as the server, unless you run ViaVersion on a Paper server to let other versions join.
Can I downgrade my server after updating?
Not safely. Restore the backup you took before updating instead of loading the world in an older version.
Skip the setup. Your own Minecraft server.
Then $4.99/mo. Just trying it? $1.25 for 3 days