How to Update Your Minecraft Server to a New Version

A new Minecraft version brings fresh content, but updating a live server too fast can break plugins, mods, or your world. This guide gives you a safe order to follow so an update goes smoothly.

Step 1: Back up everything first#

Before you touch anything, take a full backup of the server folder, especially the world folders and your config files. New versions can change how the world generates at the edges, and a backup is your safety net if something goes wrong. Never update without one.

Step 2: Check that your plugins and mods are ready#

This is the step people skip and regret. If you run plugins, confirm each one supports the new version before you update. The same goes for mods on a Fabric or Forge server. A single incompatible plugin can stop the server from starting.

If a key plugin has not updated yet, wait. There is no rush to be on day one of a release when your server depends on community software.

Step 3: Get the right server jar#

Download the new server jar for the version you want:

• Vanilla servers get the new jar from Mojang.
• Paper, Spigot, or Purpur servers download the matching new build.
• Fabric or Forge servers update the loader to the new Minecraft version.

Replace your old jar with the new one, keeping the same file name so your start command still works.

Step 4: Update plugins and mods#

Swap each plugin or mod for the version that matches your new Minecraft version. Do this at the same time as the jar so nothing is left behind on an old version.

Step 5: Start and watch the console#

Start the server and read the console carefully. Look for any plugin or mod that fails to load and note the version it complains about. Fix or remove the offender, then start again.

java -Xms6G -Xmx6G -jar server.jar nogui

Step 6: Test before you reopen#

Join the server yourself and check the important systems: spawn protection, permissions, economy, and any custom features. Confirm the world loads correctly and players can move around. Only reopen to your community once it looks healthy.

Handling major version jumps#

Skipping several versions at once is riskier than moving one step at a time. If you are far behind, consider updating through the intermediate versions, testing at each stop. Big jumps are also where world generation changes are most visible at chunk borders.

A note on snapshots#

Snapshots and pre releases are for testing, not production. They can corrupt worlds and rarely have plugin or mod support. Keep them on a separate test server, never your main one.

Make rollbacks painless#

The reason backups matter is simple: if an update goes wrong, you want to restore in minutes. A host that keeps automatic off site backups makes this effortless. Prism Nodes includes daily off site backup slots so you can roll back an update instantly. Use code IMSWITCHING for 15% off your first month.

Once you are on the new version, it is a good time to review your RAM allocation, since new versions sometimes shift performance.