Letting Bedrock Players Join Your Java Server With Geyser

Minecraft comes in two editions that normally can’t play together: Java Edition on PC and Bedrock Edition on consoles, phones, tablets and Windows. If your friends or community are split between them, Geyser bridges the gap, letting Bedrock players join your Java server. This guide covers setup and the quirks worth knowing.

How Geyser works

Geyser is a protocol translator. Bedrock players connect to Geyser, which translates their Bedrock traffic into Java traffic for your server, and translates the server’s replies back. From the server’s point of view, Bedrock players look like Java players.

Floodgate, a companion plugin, solves authentication. Normally a Java server requires a Java Edition account. With Floodgate, Bedrock players can join with just their Microsoft/Xbox account — they don’t need to own Java Edition.

Where to install it

• Single Paper server: install Geyser (the Spigot/Paper build) and Floodgate on the server.
• Velocity network: install Geyser and Floodgate on the proxy (their Velocity builds), and Floodgate on the backends too, so player data forwards correctly. See setting up a Velocity or BungeeCord proxy network.
• Fabric servers: Geyser has a Fabric version; check its documentation for current Floodgate support.

Download Geyser and Floodgate from the official GeyserMC site or Modrinth.

Setup on a Paper server

1. Put Geyser-Spigot.jar and floodgate-spigot.jar in plugins/.
2. Start the server once to generate configs, then stop it.
3. In plugins/Geyser-Spigot/config.yml, check the Bedrock section and authentication:

bedrock:
  address: 0.0.0.0
  port: 19132
remote:
  auth-type: floodgate

4. Start the server. The console shows Geyser starting and listening on the Bedrock port.

The UDP port

This is the step that trips most people up. Bedrock uses UDP, and by default port 19132 — separate from Java’s TCP port (usually 25565).

• On a hosting panel, you need a UDP port allocated to your server. If the panel gives you a different port, set bedrock.port in Geyser’s config to match (or enable Geyser’s option to reuse the Java port where supported).
• On a VPS or home server, open the UDP port in your firewall and router.

Bedrock players connect with your server’s address and the Bedrock port. If Java players can join but Bedrock players time out, the UDP port is almost always the reason.

Usernames and plugins

Floodgate gives Bedrock players a username prefix — by default a dot, so Steve becomes .Steve — to avoid clashing with a Java player of the same name. You can change the prefix in Floodgate’s config.

Things to check:

• Permissions and whitelists — add Bedrock players by their prefixed name. Floodgate provides commands for whitelisting Bedrock players.
• Plugins that validate names — a few plugins reject names with a dot. Change the prefix (for example to * or _) if you hit this.
• UUIDs — Bedrock players get a stable Floodgate-generated UUID, so their data persists between sessions.

Floodgate can also let players link a Bedrock account to an existing Java account, so the same person shares one inventory and identity across both editions.

Limitations to expect

Geyser is impressive, but Java and Bedrock are different games under the hood:

• Combat feels different — Java’s attack cooldown and Bedrock’s combat don’t match perfectly. Competitive PvP between editions can feel uneven.
• Some blocks, items and mechanics are translated imperfectly or approximated, especially new features right after a Minecraft update.
• Custom resource packs don’t transfer directly; Geyser supports Bedrock resource packs separately.
• Some plugin menus (chest-based GUIs) look and behave differently on Bedrock. Floodgate supports Bedrock-native forms that some plugins use for better menus.
• Modded servers — Bedrock players can’t use Java mods, so Geyser suits plugin servers rather than content modpacks.

For survival, building and casual play, it works very well.

Consoles need extra steps

Phones, tablets and Windows Bedrock can add custom servers directly. Consoles — Xbox, PlayStation and Switch — only show featured servers by default, so console players need a workaround (commonly a DNS-based method or joining through a friend on another platform). The GeyserMC documentation keeps up-to-date instructions.

Keep Geyser updated

Bedrock Edition updates frequently, and each update can change the protocol. When Bedrock players suddenly get “outdated client” or connection errors after a Bedrock update, update Geyser (and Floodgate). Geyser usually supports new Bedrock versions quickly. Also keep your Java server and Geyser on compatible versions — Geyser’s documentation lists which Java versions each release supports.

Performance

Geyser adds some CPU and memory overhead for translation, proportional to the number of Bedrock players. For a few Bedrock players on a normal server it’s modest; on large mixed communities, factor it into your resources. See how much RAM a Minecraft server needs.

Troubleshooting

Bedrock players can’t connect at all — the UDP port isn’t open or allocated, or Geyser’s configured port doesn’t match the one your host gave you.

“Unable to connect to world” — often the port, or a Bedrock client newer than your Geyser version supports. Update Geyser.

Players see “you are not whitelisted” — add them by their prefixed Floodgate name, or use Floodgate’s whitelist command.

Auth errors — make sure auth-type: floodgate is set and Floodgate is installed (on backends too, for networks).

Hosting

On Kerit Cloud’s Minecraft hosting, mention Bedrock players when you request your quote so a UDP port is set up for Geyser; staff can install and configure Geyser and Floodgate for you, or you can do it through full panel access.

Summary

Geyser translates Bedrock Edition traffic so phone, console and Windows Bedrock players can join your Java server, and Floodgate lets them do it without a Java account. Install both on your Paper server (or proxy), make sure the Bedrock UDP port (19132 by default) is allocated and matches Geyser’s config, whitelist players by their prefixed names, expect some combat and feature differences, give console players the documented workaround, and update Geyser whenever Bedrock updates.