26.2 vs 26.3: Should Server Owners Update Yet?

Vanilla and Fabric servers can move to 26.3 now, as long as you back up first and your mods have 26.3 builds. Paper, Folia and Geyser crossplay servers should stay on 26.2 for now, because as of September 18, 2026 none of them has a stable release that runs on 26.3. Minecraft Java 26.3 "Wilderness Bound" came out on September 15 with the dappled forest and abandoned camps, and the rundown of everything new in 26.3 covers the player side. What forces the decision for owners is the protocol bump from 776 to 777: vanilla 26.2 and 26.3 can't connect to each other in either direction.

Where each platform stands

Treat the last column as today's advice, and check each project's downloads page before you act.

Software	26.3 status (as of September 18, 2026)	What I'd do
Vanilla	Official 26.3 `server.jar` out since September 15, needs Java 25	Update after a backup
Paper	Only experimental (alpha) 26.3 builds; the downloads page still leads with Paper 26.2	Stay on 26.2
Folia	No 26.3 builds yet; the newest is 26.2	Stay on 26.2
Spigot	First 26.3 builds available through BuildTools since September 15	Move once your plugins confirm 26.3
Velocity	Stable release 4.2.0 supports 26.3 (protocol 777)	Update the proxy any time
Fabric	Loader 0.19.5 is stable for 26.3, and Fabric API has `+26.3` builds	Move once your mods have 26.3 builds
NeoForge	Beta builds only (26.3.0.x-beta)	Wait, unless you're happy running a beta
ViaVersion / ViaBackwards	26.3 support is finished but not yet in a public release	Wait for the public release
Geyser / Floodgate	Bedrock 26.50 and 26.51 supported, but the Java side is still 26.2	Update Geyser, keep Java on 26.2

As of September 18, 2026, Paper's 26.3 builds sit behind a "Toggle experimental builds for 26.3" switch on the Paper downloads page. Move when that page headlines 26.3.

Crossplay is the firmest reason to hold. As of September 18, 2026, Geyser's supported-versions page lists Bedrock 26.30 through 26.51 and Java 26.2, and its Java 26.3 support exists only as preview builds the team labels "experimental; expect bugs and don't use on production!" Floodgate needs an update too. Move the Java side first and your Bedrock players lose their way in, so keep a Geyser and Floodgate crossplay setup on 26.2 until that page lists Java 26.3.

Spigot's announcement says there are no significant API changes since 26.2 and no substantial breakage expected for plugins that use the API. Plugins that reach into server internals are the usual exception.

Updating Velocity won't let 26.3 players into 26.2 backends by itself. That translation is ViaVersion's job, and as of September 18, 2026 ViaVersion's 26.3 support is finished but hasn't been published as a public release.

What holding on 26.2 means for your players

Anyone whose launcher is set to Latest Release gets 26.3 the next time they press Play, and a plain 26.2 server can't let them in. On Paper or Spigot they're kicked with "Outdated server! I'm still on 26.2", which comes from messages.outdated-server in spigot.yml, so you can reword it to point people at your Discord while you wait. A vanilla or Fabric server sends "Incompatible client! Please use 26.2" instead, which reads as if their game is the problem, even though your server is the one behind. For a Paper server the practical bridge is ViaVersion: once its 26.3 release is public, installing it on your 26.2 server lets 26.3 clients join without you touching the world.

Moving early has its own cost. Anyone still on 26.2 sees "Incompatible version!" next to your server in their list, and if they try to join a Paper or Spigot 26.3 server anyway they get "Outdated client! Please use 26.3" (messages.outdated-client in the same file), or "Incompatible client! Please use 26.3" on vanilla. On a public server, that's a lot of confused players at once.

The changes that actually affect owners

New servers start with the whitelist on

white-list in server.properties now defaults to true. Mojang only says the default changed, but an existing server.properties already has a white-list= line written in it and the server reads what's there, so an upgraded server should keep whatever value you had. Where it will catch you is a fresh install, like a test server you spin up to try 26.3, where players get "You are not white-listed on this server!" until you add them with /whitelist add or set white-list=false. Whitelisting a server properly covers the rest.

Command signs need a new flag

Signs no longer run click events in their text by default, and text components on newly placed signs aren't resolved by default either. A new block-entity field, allow_op_features, brings the old behaviour back. Signs saved before 26.3 are migrated with it set to true, so the command signs already in your hub keep working after the upgrade. New ones are the catch: any sign created on 26.3 needs allow_op_features set explicitly, or clicking it won't run its command. Hubs and minigame servers that build click signs are the ones to test, and if a plugin makes those signs for you, check its changelog for 26.3.

Some console log lines are gone

Mojang's changelog says "some log lines that server software might look out for have been removed" and doesn't list which. If a panel, bot or script reads the console to spot startup or joins, run it against a 26.3 test server before you trust it. Mojang points to the Minecraft Server Management Protocol instead, and its version 3.1.0 adds notifications for a full world upgrade on startup.

Data packs moved to format 121.0

The data pack format went from 107.1 on 26.2 to 121.0, with real breaking changes, so expect custom packs written for 26.2 to need work. These are the ones most likely to bite:

worldgen/configured_feature moved to worldgen/feature, and the configuration is now written inline instead of in a separate config field.
cookingtime is now required on every cooking recipe. Custom smoker and blast furnace recipes need double their old value, and a recipe that relied on the default can use 200 to keep the same timing.
Block-state fields were renamed: Name is now id and Properties is now properties.
In advancement trigger predicates, condition was renamed type and is now mandatory.

Resource packs moved too, to format 97.1 from 88.0, and adding a data pack to a server covers where packs live.

Java stays at 25

26.3 needs Java 25, the same as 26.2 and 26.1, and Paper lists the same minimum for 26.3, so a server already on 26.2 has no Java upgrade to do.

Dappled forests only appear in new chunks

The new biome and the abandoned camps only generate in chunks that haven't been generated yet, and existing terrain isn't rewritten. That matters more if you pre-generated your map on 26.2: when everything inside your world border already exists, there's nowhere left for the new content to spawn, and the usual answer is to push the border out into fresh land or start a new world for it. Tell your players, too, before someone spends an evening looking for a dappled forest near spawn.

Back up before anything else

World upgrades only go one way. Spigot's announcement puts it plainly: "it is not possible to downgrade your server to an earlier version." Once your world has loaded on 26.3, the copy you took beforehand is your only route back to 26.2, and backing up a Minecraft server has the full routine. The staged test from the 26.1 vs 26.2 decision still applies too: load a copy of that backup on a 26.3 test server, read the console, and fix what breaks before production ever sees it.

How to update when you're ready

Stop the server and take the backup.
Swap in the new server software: Mojang's 26.3 server.jar for vanilla, java -jar BuildTools.jar --rev 26.3 for Spigot, or the Fabric installer with Loader 0.19.5 and a Fabric API build tagged +26.3. For Paper, wait until the downloads page offers a stable 26.3 build.
Update each plugin or mod to its 26.3 version, and hold back anything whose author hasn't confirmed 26.3, especially plugins that reach into server internals.
Start the server and read the console for errors from plugins, mods and data packs.
Check what 26.3 changed: click a command sign, confirm your data packs loaded, and look at the white-list line in server.properties.
Update your listing so players know which version to load. Servers that have already moved show up under 26.3 on the server list.

FAQ

Can players still on 26.2 join after I move to 26.3?

ViaBackwards is the plugin that lets older clients onto a newer server, and it needs ViaVersion installed alongside it. Neither has a public 26.3 release as of September 18, 2026, so for now a 26.3 server only takes 26.3 clients. Neither one goes into the vanilla server jar itself. They run as plugins on Paper, Spigot or a Velocity proxy, or as mods through ViaFabric, so a pure vanilla server can only use them through a proxy placed in front of it.

Does staying on 26.2 lock out my Bedrock players?

No. Bedrock numbers its releases on a separate line, and its Wilderness Bound release is 26.50, with a 26.51 hotfix. Current Geyser builds support both of those while still pointing at a Java 26.2 server, so a crossplay server that holds on 26.2 keeps its Bedrock players as long as you update Geyser to its latest build (26.50 support landed on September 15). Moving the Java side too early is what would cut them off.

Is a 26.3.1 hotfix worth waiting for?

As of September 18, 2026 there's no 26.3.x hotfix out or announced, and 26.2 never got one either. Wait on your server software, not a point release.

Why aren't all my Fabric mods ready if the loader is?

Some mods have extra work this time. Fabric API for 26.3 removed several registries, including the fuel, composting-chance and strippable-block ones, because vanilla now handles those through components or recipes. Any mod that relied on them needs a 26.3 build that moves off them.