How to Set Up Geyser and Floodgate for Java and Bedrock Players

Geyser translates Bedrock client connections for a Java server. Floodgate is an optional authentication companion that allows eligible Bedrock players to join without a separate Java account. Set up the supported Geyser platform, decide the authentication path and allow the actual UDP game listener before testing a cross-edition join.

Choose the correct platform and version first

This walkthrough describes a single Paper server. A Velocity/BungeeCord network, standalone bridge or mod-loader installation needs its own official setup path. Check Geyser’s current supported-version documentation before downloading: protocol support changes as Minecraft updates. A compatible Java protocol translator may be required for older backend versions.

1. Install on a private copy

1. Back up the Java server and record its build, plugins, Java version and existing ports.
2. Download the Geyser-Spigot build from the official project and install it in plugins. Add the matching Floodgate plugin if that authentication mode is required.
3. Start once to generate configuration, then stop before editing. Use the files generated by those releases.
4. Set the Bedrock listener to the UDP allocation supplied by the host. The common default is 19132, but an assigned port takes precedence.

Do not reuse a UDP allocation already occupied by voice chat or query traffic. Java TCP and Bedrock UDP are distinct listeners even if their port numbers happen to match. Verify both host and provider rules. A web-browser or TCP-only port check cannot establish that Bedrock UDP traffic reaches the service.

2. Configure the intended identity path

For Floodgate, follow its platform instructions and select Floodgate authentication in the generated Geyser configuration. Keep its key material private. Without Floodgate, use the documented Java-account authentication path. Do not disable authentication on an Internet-accessible Java backend as a shortcut to crossplay.

If adding a proxy later, revisit forwarding and backend reachability with that platform’s documentation. A setting appropriate behind a trusted proxy is unsafe when players can bypass the proxy and connect directly. Keep allowlists and permissions aligned with the identities the chosen authentication system actually presents.

3. Test both editions and access rules

1. Start the server and inspect Geyser/Floodgate startup messages for version, bind or authentication errors.
2. Connect a Java client normally and a Bedrock client from an external network using the configured address and UDP port.
3. Test a permitted player and an account that should be denied. Check names/identifiers used by your permission and whitelist tools.
4. Verify inventory, movement, a representative plugin interface and persistence after reconnecting. Translation does not guarantee every Java-specific interface works identically.

# Server console; substitute the public address and actual UDP port
geyser connectiontest YOUR_SERVER_IP 19132

What Geyser does not convert

Geyser does not make Java client-content mods available on Bedrock. Console clients can also have platform-specific restrictions on adding external servers. Confirm the actual devices your players use before promising universal access. Keep your prior installation and configuration so an unsuccessful trial can be rolled back.

Read Java vs Bedrock hosting for edition choices. Before ordering Minecraft hosting, confirm Geyser support and an available UDP allocation for the exact deployment.