Does Geyser support 26.60 and the latest Minecraft version?
Published on 27 October 2026
Does Geyser support 26.60? Yes. Geyser 2.12.1, build 1273 from 26 October 2026, supports Minecraft Bedrock 26.60, the update Mojang planned for 27 October 2026. On the Java side Geyser supports 26.3, the current release. So Bedrock players on 26.60 can join a Java 26.3 server, as long as Geyser is up to date and switched to NetherNet. This page lists which versions work today and what to do after each update. Last checked on 27 October 2026 at 14:45 UTC, when Mojang had not yet published its 26.60 release notes.
Does Geyser support 26.60 right now?
Yes, from build 1273 onwards. GeyserMC released it the evening before the planned Bedrock release, with the change “Support 26.60”, and removed support for Bedrock 26.30 in the same build. Older builds don’t know 26.60, so a server running an older Geyser turns away players who have already updated. Bedrock updates itself on phones, consoles and PCs, so most of your players get the new version shortly after the release.
On the Java side nothing changes this week: Geyser still behaves like a Java 26.3 client. Java 26.4 is only in snapshots so far, and Geyser supports releases, not snapshots.
Which Bedrock and Java versions work today
| Edition | Supported |
|---|---|
| Bedrock | 26.40 to 26.45, 26.50 to 26.52 and 26.60 |
| Java | 26.3; older servers from 1.20.5 with the ViaVersion plugin |
| No longer | Bedrock 26.30 and older |
The list comes from the Geyser source code on GitHub. GeyserMC’s Supported versions page still said 26.30 to 26.52 when we checked; the wiki tends to follow a little later.
Your Java server doesn’t have to run 26.3 itself. Geyser connects as a 26.3 player, so the server has to accept 26.3 players. On a Paper server from 1.20.5 that works with ViaVersion. On Fabric or NeoForge, Geyser only works on the newest Java version.
What changed with Bedrock 26.60 and NetherNet
With 26.60, Bedrock players stop connecting over RakNet, the old way of connecting. They only use NetherNet. First the player’s game asks the server over TCP how to connect, and then the game itself runs over UDP. For Geyser that means three things:
- Turn NetherNet on. In Geyser’s config, under
bedrock, settransporttonethernet. Every build from 1237 can do NetherNet. In build 1273 it became the default for new configs. Check your existing config anyway: it should saynethernet. - TCP and UDP on the Geyser port. By default Geyser uses port 19132 for both. If Geyser shares a port with your Java server, give it a port of its own.
- A trust question. Players who connect through an IP address get a question the first time whether they trust the server. That’s normal. HTTPS signalling removes it, but that takes a certificate.
Players still on a Bedrock version older than 26.40 can’t use NetherNet at all. They need to update their game. Running a plain Bedrock server without Geyser? Then see Bedrock server and NetherNet.
How to update Geyser and Floodgate on your server
- Make a backup of your server.
- Download the latest builds of Geyser and Floodgate from geysermc.org/download, in the version for your server software: Spigot (also for Paper), Fabric, NeoForge or your proxy.
- Replace the old jars in the
pluginsfolder (ormodson Fabric and NeoForge). Delete the old files, so there’s only one Geyser jar. - Restart the server. The console should show
Started Geyser onfollowed by your port. - Check the version. Type
geyser versionin the console. It shows the build and says whether a newer one exists.
Installing Geyser for the first time? The full walkthrough, with the extra port and Floodgate, is in Install Geyser: Bedrock players on your Java server.
Players get an outdated client or server message
Two messages come up after almost every Minecraft update. They mean opposite things.
| Message | What it means | Fix |
|---|---|---|
| Outdated client! Please use ... | The player’s Bedrock is newer than your Geyser knows | Update Geyser |
| Outdated server! I’m still on ... | Your Java server is older than the version Geyser expects | Update the server or add ViaVersion |
Do Bedrock players time out without any message? Then it’s usually the connection, not the version: transport still set to raknet, a port that isn’t open over both TCP and UDP, or Geyser and another plugin on the same port. The console tells you which port Geyser started on.
Console players are a separate story. Xbox, PlayStation and Switch can’t add a server by address, and the usual workaround doesn’t work with NetherNet yet. How Java and Bedrock players can play together in other ways is in Minecraft crossplay: Java and Bedrock together.
How we keep this page up to date
A new Minecraft version comes out every few weeks, on Java or Bedrock, and the same question comes back every time. We check this page against GeyserMC’s builds and source code when Mojang releases a new version, and the date at the bottom of the page shows the last check. A quick rule until then:
- New Bedrock version: update Geyser as soon as GeyserMC has a build for it. For 26.60 that build came a day before the release.
- New Java version: wait with updating your server until Geyser supports it, or your Bedrock players can’t get in. What’s new in the current release is in Minecraft 26.3 Wilderness Bound.
Java and Bedrock friends on one world? A Java plan at CakeHosting comes with an extra port for Geyser, so Bedrock players get their own address next to your Java server. From €4.95 a month. See the Minecraft server plans.