Geyser for Minecraft: Let Bedrock Players Join Your Java Server
Java and Bedrock don't talk to each other. A friend on a console or a phone can't just type your Java server's address and join. Geyser fills that gap. It sits on your Java server and translates Bedrock's traffic so Bedrock players can walk in next to Java players.
This guide covers the plugin route on Paper or Spigot, since that's what most servers run. Everything here was checked against GeyserMC's own setup and common-issues pages on November 21, 2026. Their docs have changed recently (new transport setting, new version numbers), so if your Geyser looks different, believe the pages that ship with your Geyser build. Trouble after install has its own page: Geyser connection problems.
- Install
Geyser-Spigot.jarinplugins, restart, then setbedrock.portandtransportin the config. - Default port is 19132. Geyser's current docs say TCP and UDP both matter.
- Add Floodgate if Bedrock players don't own Java.
On this page
What you need first
- A Java server running Paper or Spigot. If you're still on plain vanilla, the Paper vs Spigot vs Purpur vs vanilla guide explains why most people move.
- A backup. Plugin installs are low risk, but a minute on the Backups tab costs nothing.
- A free port for Geyser. It's separate from your Java port, and the default is 19132.
Other platforms work too. Geyser's setup page lists a Fabric mod and a NeoForge mod (both need a 26.3 server and work server-side only), proxy plugins for Velocity and BungeeCord (installed on the proxy, not the backends), a ViaProxy build, and a standalone program that needs Java 21 or newer. We're sticking to Paper here. For plugins in general, see the Paper plugin install guide.
Install Geyser on Paper
- Get the plugin
Download
Geyser-Spigot.jarfrom GeyserMC's download page. The jar name matters, because the Fabric, NeoForge and proxy builds are different files. - Upload it
Open the Files tab, go to the
pluginsfolder and upload the jar. - Restart once
Click Restart and watch the Console tab. Geyser creates its folder and a
config.ymlon the first start. - Open the config
On the Files tab, open
plugins/Geyser-Spigot/config.yml. Under thebedrock:section you'll findportandtransport. Geyser's setup page tells you to set both, and its example setstransporttonethernet. - Restart again
Save the file and restart. The console should show Geyser starting up without errors.
The port, and why UDP alone isn't enough
Geyser's default port is 19132, and no other program on the machine can share it. The older advice was that Bedrock only needs UDP. GeyserMC's current setup page says otherwise: Geyser uses the port over both TCP and UDP, TCP so players can find the server and UDP for gameplay. Forward only UDP and the server can end up invisible to players.
On ChicagoServers the panel assigns your ports. Look at the Network section of the Startup tab, and if your server offers Extra ports, that's where a second port like this goes. If it doesn't, contact support and tell them you need 19132 (or whichever port you picked) open for both TCP and UDP. If you ever change the port in config.yml, the panel's port has to match.
Floodgate: skip the Java account
By default a Bedrock player has to log in with a paid Java account through Geyser, which most Bedrock players don't have. Floodgate is the add-on that lets them join with their Bedrock account instead. It's a separate plugin with its own setup, covered in the Floodgate guide. If you want Bedrock friends on your server, you almost certainly want it.
Joining from Bedrock
- In Bedrock Edition, open the Servers tab and add a server manually.
- Enter your server's address in the address field and the Geyser port, 19132 unless you changed it, in the port field.
- Join. If it fails, don't type the address and port together in one box, and use the plain IPv4 address if a domain doesn't work. Geyser's docs call out both of those.
Limits to know about
- The Fabric and NeoForge builds only work server-side. A mod that every player has to install on their own client won't work through Geyser.
- Tunneling services that can't forward UDP don't work with Geyser, according to its setup page. You need a real open port.
- The built-in signaling server uses plain HTTP, so players may see a "Trust on First Use?" prompt unless you set up HTTPS.
- Geyser's page ties full support for the new transport to version numbers 26.40 and 26.50. Read it for the exact meaning, and ask players to keep their game updated.
Frequently asked questions
What port does Geyser use?
19132 by default. Geyser's setup page says it uses the port over both TCP and UDP, and that no other program can use it.
Do I need Floodgate for Bedrock players?
If you want Bedrock players to join without a paid Java account, yes. Without it they need a Java account to log in.
Does Geyser work on vanilla servers?
The plugin version needs Spigot or Paper. For vanilla, Geyser lists a standalone program (Java 21 or newer) and mod versions for Fabric and NeoForge.
Can console players join?
Not by typing an address. Consoles need a separate method that Geyser documents on its own consoles page.
Can Bedrock players use Java mods?
No mod that needs to be installed on the player's client will work through Geyser. Server-side-only mods can.