Set up crossplay (Geyser + Floodgate)
Updated September 2026 · Geyser translates Bedrock to Java. Floodgate lets Bedrock players join without a Java account. You need both.
How crossplay works
Java and Bedrock speak different network protocols. Geyser sits in front of your Java server and translates for Bedrock players. Floodgate handles logins, so Bedrock players can join with their Microsoft account and do not need to own Java Edition.
Your server stays a Java server. Java players connect as usual; Bedrock players connect to the same address on a separate port.
What you need
- A Java server running Paper (or Spigot), Velocity, BungeeCord or Fabric. Paper is the most common and the easiest.
- A UDP port for Bedrock. The default is 19132.
- The Geyser and Floodgate builds for your platform, from geysermc.org.
Geyser supports the current Java version. If your server runs an old Minecraft version, you will also need a plugin like ViaVersion, and results vary.
Step by step on Paper
- Stop the server.
- Download Geyser-Spigot and Floodgate-Spigot and put both
.jarfiles in thepluginsfolder. - Start the server once, then stop it. Both plugins create their config folders.
- Open
plugins/Geyser-Spigot/config.ymland check two settings:bedrock→port: the UDP port Bedrock players will use (19132 by default).auth-type: set tofloodgate.
- Start the server again. The console should show Geyser starting on the Bedrock port.
On a host, the Bedrock port has to be open for UDP. If your server only has one port, some setups let Geyser share the Java port number for UDP — check the Geyser config comments for the clone-remote-port option. For a home server, forward UDP 19132 on your router.
How Bedrock players join
- Windows, iOS, Android: Play → Servers → Add Server. Enter the server address and the Bedrock port.
- Xbox, PlayStation, Switch: consoles only show featured servers and have no “Add Server” button. The common workarounds are joining through a friend who is already on the server, or a DNS redirect tool that turns a featured server entry into a custom one. Geyser’s own documentation lists the current options.
Bedrock players appear on the server with a prefix in front of their name. By default Floodgate uses a dot, so “Steve” becomes “.Steve”. Keep that in mind for commands.
Whitelist and permissions for Bedrock players
- Bedrock names contain spaces and the prefix, so quote them if needed.
- Floodgate adds
/fwhitelist add <name>for Bedrock players who have never joined before. - Once a Bedrock player has joined, you can treat them like any Java player in LuckPerms or with
/op.
More on this in whitelist, OPs and permissions.
What does not work the same
Geyser is very good, but it cannot make two different games identical.
- Mods: Bedrock players cannot join a Forge or NeoForge modpack server. Geyser works with Fabric, but only for mods that do not add new content the client would need.
- Custom items and resource packs may look different or need a converted pack.
- Combat follows Java rules, so Bedrock players notice the attack cooldown.
- Some blocks and UI (like certain inventories or maps) are approximations.
For vanilla survival and most plugin servers, players rarely notice.
Troubleshooting
| Problem | Check |
|---|---|
| Bedrock gets “Unable to connect to world” | UDP port open? Correct port in the Add Server screen? |
| Geyser starts on the wrong port | bedrock → port in config.yml |
| Bedrock players asked for a Java login | auth-type is not floodgate, or Floodgate is missing |
| Works for Java, not Bedrock, on a home server | Router forwards TCP 25565 but not UDP 19132 |
| “Outdated client” on Bedrock | Update Geyser; it usually adds new Bedrock versions quickly |
If Java players cannot connect either, the problem is not Geyser — see server not showing up: fixes. For a deeper comparison of the two editions, read Java vs Bedrock for server owners.