Ready to play?
Your Server Is
One Click Away.
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!
Ready to play?
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!
By BruceNode·May 17, 2026·7 min read·67 views
Half the Minecraft world plays Bedrock, half plays Java. They normally can't see each other. Geyser changes that. Install it on your Java server, your friends on phones, consoles, and Windows 10 Edition can connect to the same world without buying the game twice. This is the setup guide for 2026.
Quick answer: install Geyser-Spigot as a plugin on a Paper, Purpur, or Spigot server. Add Floodgate if you want Bedrock players to skip the Microsoft account requirement. Forward UDP port 19132. Bedrock players connect to your server IP on that port. Done in under 15 minutes.
Geyser is a translation layer. It sits in front of your Java server, listens for Bedrock connections on a separate port, and converts every Bedrock packet to Java protocol on the fly. Your Java server has no idea anything unusual is happening, it just sees regular Java players.
The Bedrock client, the one running on phones, Xbox, Switch, PS5, Windows 10/11 Edition, talks to Geyser. Geyser talks Java to your server. Translation happens per packet, both directions, in real time.
What it gets right: blocks, mobs, inventory, chat, movement, PvP, redstone, command blocks. Modern versions handle 99 percent of vanilla gameplay seamlessly.
What it can't do: heavily Java-specific mods (Forge or Fabric mods that change client rendering won't work for Bedrock players), some Java resource packs (Bedrock has its own pack format), and the exact same custom-model-data behavior for items (workarounds exist).
For 95 percent of community servers running vanilla, Paper, or Purpur with standard plugins, Geyser is invisible to players and just works.
The shopping list:
You do need:
plugins/ folder.geysermc.org/download.plugins/ via the file manager or SFTP.That's it for the basic install. On first boot Geyser generates plugins/Geyser-Spigot/config.yml with sensible defaults. Bedrock players can already connect on UDP port 19132.
If your hosting plan doesn't have UDP 19132 open by default, you have two options: change the Geyser port to one that is open (we'll cover that), or ask support to open 19132 for your specific server. BruceNode opens additional ports on request, no extra charge.
Without Floodgate, Bedrock players need a paid Java Minecraft account linked to their Microsoft profile to connect through Geyser. That defeats the point.
Floodgate is a separate plugin that lets Geyser create temporary Java-side identities for Bedrock players. They connect with their Xbox or PSN username, the server treats them as a regular Java player, no Microsoft account needed on the Java side.
Install:
geysermc.org/download.plugins/ alongside Geyser.Floodgate auto-detects Geyser and wires itself up. Bedrock-only players get a . prefix on their username by default (e.g. xX_BedrockBoy_Xx becomes .xX_BedrockBoy_Xx on the Java side). You can configure or disable the prefix in plugins/floodgate/config.yml.
Default Geyser config listens on UDP 19132. Bedrock players connect with:
If port 19132 is busy or your host doesn't open it, edit plugins/Geyser-Spigot/config.yml:
bedrock:
port: 25566 # or any UDP port your host has open
Restart and Bedrock players use that port instead.
Optional: cloning your Java port for Bedrock. Set clone-remote-port: true to make Geyser listen on the same number as your Java server. Bedrock and Java players both connect on the same numeric port (e.g. 25565), Geyser figures out which protocol each connection is using. This is the cleanest setup for a public community server.
From your Java client: connect to your usual IP. Should work as always.
From a Bedrock device: open Minecraft Bedrock, hit Play > Servers > Add Server, paste your IP and the Bedrock port. Connect.
If both connect, you're done. The same world. The same players. The same chat.
"Can't connect from Bedrock, Java works fine." 99 percent of the time this is the UDP port not being forwarded. Geyser uses UDP, not TCP. If your host only forwards TCP for Minecraft (some do), you need them to add UDP. Ping BruceNode support and we add it.
"Bedrock connects but kicks me immediately." Almost always a version mismatch. Bedrock client version has to be compatible with the Geyser build. The Geyser team ships updates within hours of new Bedrock releases, but if your client just updated and Geyser hasn't yet, you'll get kicked. Wait a day or grab the latest Geyser dev build from their Discord.
"Bedrock players can join but blocks look wrong." This is a resource pack issue. Bedrock has its own pack format. Either disable your custom Java pack for Bedrock players (Geyser has a config flag for this) or ship a Bedrock-compatible pack via the auto-resource-pack feature.
"Skins are messed up on Bedrock."
Floodgate uses placeholder Java skins for Bedrock players by default. To pass through the actual Bedrock skin, enable floodgate.bedrock-skins in the Floodgate config. Some Java-side cosmetic plugins still won't recognize it, that's an upstream limit.
"Performance dropped after installing Geyser." The translation layer costs some CPU. On a 4 GB server hosting 15 to 20 players you'll see maybe 5 to 10 percent overhead. On larger servers it's negligible per-player. If you're seeing big TPS drops, check that your server has at least 1 GB of headroom over baseline RAM, and that nothing else is fighting for CPU during chunk-gen bursts.
Geyser's overhead in 2026 is much smaller than it used to be:
Plan for 200 to 500 MB additional RAM headroom on Geyser-enabled servers, depending on Bedrock player concurrency. The resource calculator factors this in for you.
The Java-Bedrock split is the biggest unforced error in multiplayer Minecraft. Geyser fixes it cheaply.
Communities that turn on Geyser see immediate growth because the friction to join drops to near zero. Friends with Switches join. Cousins on phones join. The dad who only owns Windows 10 Edition joins. No "you need to buy a different version" conversation.
Even small servers feel busier. A 10-person Java community becomes a 15-person Java+Bedrock community within a month because every member can now invite people who own the wrong edition.
For private friend servers, this is the single highest-ROI plugin to install. For public servers, it doubles your addressable audience.
This guide covers Spigot, Paper, and Purpur because that's where 90 percent of community servers are. Geyser does have Fabric and Forge variants:
mods/ instead of plugins/. Same config. Works on any modern Fabric server.mods/.The setup steps are identical, just different folder. If you're running a Fabric modded server with our Fabric install guide, you can add Geyser the same way.
For pure proxy setups (BungeeCord, Velocity, Waterfall), Geyser ships dedicated proxy builds. Most community servers don't need this layer, but if you're running a network of multiple Java servers behind a proxy, Geyser-Velocity is the cleanest install path.
Install Geyser-Spigot, install Floodgate, open one UDP port, restart. 10 minutes of work. Bedrock players join through the same IP, see the same world, fight the same mobs. The Java-Bedrock split stops being a problem.
This works on every modern Minecraft server fork. Paper, Purpur, Pufferfish, Leaves, Fabric, Forge, NeoForge, all good. The Paper vs Purpur fork guide is a fine read if you're choosing your engine, but Geyser works on all of them equally.
Use code BRUCE20 for 20% off your first month.