How to Update Your Minecraft Server to 26.2 (Java & Bedrock)

Minecraft’s new 26.2 “Chaos Cubed” game drop landed on June 16, 2026, adding sulfur caves, cinnabar blocks, a built-in friends list, and an experimental Vulkan renderer. If you run a multiplayer world, your players will want it the moment they update their clients. This guide walks you through how to update your Minecraft server to 26.2 safely, covering both Java Edition (server version 26.2) and Bedrock Edition (server version 26.30), plus the gotchas that bite Paper, Spigot, Fabric, and Forge admins. Follow the order below and you won’t lose a single block.

Quick answer: how to update a Minecraft server to 26.2

• Back up your entire server folder first (worlds, configs, plugins/mods).
• Stop the server cleanly before touching any files.
• Vanilla Java: download the new 26.2 server file from the official source, replace the old one, keep your world and configs.
• Bedrock: download the new 26.30 dedicated server zip, copy your worlds folder and settings into it.
• Paper/Spigot/Fabric/Forge: wait until that software and every plugin/mod has a 26.2-compatible build before updating.
• Match the client and server versions, confirm your Java version, then start and test on a copy first.

Before you update (back up!)

This is the step nobody should skip. A version jump can corrupt a world, break a config, or expose a plugin incompatibility, and there is no undo button on a live server. Before changing anything, stop the server and make a complete copy of the server directory somewhere safe.

At minimum, back up these:

• Your world folder(s) — on Java that’s usually world, world_nether, and world_the_end; on Bedrock it’s the worlds directory.
• server.properties and any operator/permission files.
• Your plugins folder (Paper/Spigot) or mods folder (Fabric/Forge), including each plugin/mod’s config files.

The safest approach is to test the update on a duplicate of the server first. Copy the whole folder, update the copy, and confirm it boots and behaves before you touch the real thing. If anything goes wrong, your original is untouched.

Updating a vanilla Java server

A plain vanilla server with no plugins or mods is the easiest case. The world format and config files carry forward, so you’re really just swapping the program that runs them.

• Stop the server completely (use the stop command in the console, not a force-kill).
• Take your backup as described above.
• Download the new 26.2 server file from the official Minecraft download page. Don’t trust third-party mirrors for the vanilla jar.
• Place the new server file in your server folder. Either replace the old file or update your start script / launcher to point at the new filename.
• Leave your world folders and server.properties in place — they’re compatible across the update.
• Start the server. It will load and migrate your existing world to the new version automatically on first launch.

Confirm your Java runtime is current. Modern Minecraft servers require at least Java 21, and 26.2 is no exception. If your start command points at an older Java, the server will refuse to launch — install Java 21 (or newer) and update the path.

Updating a Bedrock server

Bedrock Dedicated Server (BDS) works a little differently. Instead of a single jar, you download a full server package, and the recommended path is to set up the new version cleanly and migrate your data into it rather than overwriting files in place.

• Stop the running Bedrock server.
• Back up the entire current server folder, especially the worlds directory and your server.properties, permissions.json, and allowlist.json files.
• Download the new Bedrock Dedicated Server 26.30 package from the official Minecraft source and extract it into a fresh folder.
• Copy your worlds folder from the old install into the new one.
• Re-apply your settings — copy your saved values into the new server.properties, and bring over permissions.json and allowlist.json.
• Launch the new server and verify your world loads and players can connect.

Working in a fresh folder avoids leftover files from the old version causing conflicts, while your migrated worlds and re-applied configs preserve everything that matters.

Updating a Paper/Spigot server (plugin compatibility)

Here is the single most important rule for any server running plugins: do not update until Paper (or Spigot) has released a build for 26.2 and your plugins have updated too. Updating early is the number-one cause of broken servers. Paper and Spigot are forks of the vanilla server; each new Minecraft version needs a new corresponding build, and that build appears after the vanilla release, not at the same moment.

The safe sequence:

• Wait for Paper/Spigot to publish a 26.2 build. Until then, your server simply can’t run 26.2 with plugins intact.
• Check every plugin you depend on. Visit each plugin’s official page and confirm it lists 26.2 (or the matching API version) as supported. A plugin built for an older version may silently break, throw errors, or crash the server on startup.
• Once the platform and all critical plugins are ready, take your backup, stop the server, and replace the Paper/Spigot jar with the 26.2 build.
• Update each plugin jar in the plugins folder, keeping the existing per-plugin config files where the new version supports them.
• Start the server and watch the console closely for errors. Test on a copy first if you can.

If even one essential plugin has no 26.2 release yet, the correct move is to wait. Running your server one version behind for a week or two is far better than a broken plugin stack on launch day.

Updating a modded server (Fabric/Forge)

Modded servers follow the same principle as plugins, only more strictly: every mod must support the exact target version, and the mod loader itself must release a 26.2-compatible version first.

• Wait for the loader. Fabric and Forge each need a release that targets 26.2. NeoForge follows its own schedule too. Don’t update the loader before it officially supports the version.
• Wait for every mod. A modpack is only as ready as its least-updated mod. Check each mod’s page for a 26.2 build. Mixing mod versions, or running a mod built for an older Minecraft, will usually crash the server or corrupt the world.
• Update the loader’s server files to the 26.2-targeted version (re-run the Fabric/Forge server installer for that version, or follow your host’s loader switcher).
• Replace each mod jar in the mods folder with its 26.2 build, keeping config files where compatible.
• Ensure server-side and client-side mod versions match — every player needs the same mod set and versions to connect.
• Always test the updated modpack on a copy of your world before going live.

Because modpacks have many moving parts, it’s common for a full pack to take weeks to be fully 26.2-ready. Patience here saves you from a corrupted save.

Common problems & fixes

The easy way: managed hosting

If you’d rather skip the manual jar-swapping, a managed host handles the heavy lifting. A Minecraft server from XGamingServer gives you one-click version switching between vanilla, Paper, Fabric, and Forge, plus automatic backups so you always have a safe restore point before you update. There’s also full documentation if you want to walk through it step by step.

Frequently asked questions

Will my world carry over to 26.2?

Yes. Minecraft migrates your existing world to the new version automatically on first launch, on both Java and Bedrock. The migration is one-way, though, so always keep a backup of the old world before you update in case you need to roll back.

Will my plugins or mods break?

They can, if they aren’t updated for 26.2. Plugins and mods are tied to specific Minecraft versions. Always confirm every plugin (Paper/Spigot) or mod (Fabric/Forge) has a 26.2-compatible build before you update — running outdated ones is the most common way to break a server.

Do I have to update right away?

No. Vanilla servers can update as soon as the new server file is out, but plugin and modded servers should wait until the platform and every add-on is ready. There’s no harm in staying one version behind for a couple of weeks while the ecosystem catches up.

How do I roll back if something goes wrong?

Stop the server, delete the broken files, and restore your pre-update backup of the world and configs, then put back the older server jar or package. This is exactly why you back up first — a rollback is only possible if you saved the previous version’s files.

What Java version do I need for 26.2?

At least Java 21. Modern Minecraft server releases require Java 21 or newer, and 26.2 follows that requirement. If your server won’t start after updating, an outdated Java install is the first thing to check.