How to Update a Minecraft Server to 26.2 (from 1.21 or 26.1)

Two releases sit between a 1.21 server and 26.2, and both matter for an upgrade.

26.1 "Tiny Takeover" (March 24, 2026) was the first release with the new year.drop version numbers. It followed 1.21.11 directly. It raised the Java requirement to Java 25 and reorganised the world save folder: the Nether and End moved from DIM-1 and DIM1 into dimensions/minecraft/, and player data moved into a players/ folder. The conversion happens automatically on first start and cannot be undone.

26.2 "Chaos Cubed" (June 16, 2026) added sulfur caves with the new sulfur and cinnabar blocks, a friends list, and an experimental Vulkan renderer on the client. On the server side it added two server.properties keys, chat-spam-threshold-seconds and command-spam-threshold-seconds, both defaulting to 10, and moved the server management protocol to version 3. Data packs must target pack format 107 and resource packs format 88.

Before either of those, 1.21.9 removed four server.properties keys and turned them into game rules: command blocks, PvP, monster spawning, and Nether access. If your properties file still has enable-command-block or pvp, they are silently ignored on 26.2. The configuration step of the setup tutorial shows the replacement game rules.

Fifteen minutes of checking saves an evening of restoring:

• Plugins. On Paper, Spigot, or Purpur, open each plugin's download page and confirm a build for 26.2 or 26.1 exists. Plugins built for 1.21 will not load. Our PaperMC page lists the status of the most common ones.
• Mods. On Fabric, Forge, or NeoForge, every mod needs a 26.2 build and the loader itself needs a 26.2 release. Modded servers usually lag vanilla by weeks; wait if anything essential is missing.
• Players. A 26.2 server only accepts 26.2 clients. Tell everyone the date so they can update their launcher profile.
• Disk space. The backup doubles the size of the server folder for a while. Check you have room.

A 1.21 server ran on Java 21. 26.2 will not start on it, failing with UnsupportedClassVersionError. Install Java 25 first and confirm with java -version before touching the server files. The Java 25 install guide covers Windows, macOS, and Linux, including how to switch when an older Java is still the default.

Replace each jar in plugins/ with its 26.2 build. Anything without one goes into a folder outside the server, such as plugins-disabled/, until it is updated. Do not leave old jars in place hoping they will work: an incompatible plugin can stop the server from starting, and a plugin that half-loads can corrupt its own data.

Two plugins deserve a special look. Vault is unmaintained and stopped at 1.21; replace it with VaultUnlocked, which is a drop-in fork. ViaVersion, if you use it to let older clients join, must itself be updated before it can bridge 1.21 clients to a 26.2 server.

Start the server. Coming from 1.21, the console shows the world being converted to the 26.x folder layout. It takes seconds for a small world and minutes for a large one. Do not stop the server during this stage. Coming from 26.1, there is no conversion and startup is normal.

Startup is finished when the console prints the usual line ending in Done (12.3s)! For help, type "help". Errors before that line are almost always a plugin that is not compatible. The stack trace names the plugin; move it out and start again.

Stop the server, rename the live folder to something like minecraft-server-26.2-failed, and rename the backup to the original name. Switch the start script back to Java 21 if you replaced it, then start. You are exactly where you were before Step 1. Anything players built in the 26.2 session is lost, which is why the players were warned about the date.