Floodgate is recommended when Bedrock players should join without a linked account. Enable it in the Auth step to get matching config notes.

Which port does Bedrock use?

Bedrock commonly uses UDP 19132. Geyser listens there while the game port usually stays on TCP 25565 unless you changed those values.

Should Geyser run on Velocity?

Yes, for networks. Choose “On Velocity / BungeeCord” in step 1 so the checklist keeps backends private and opens only the proxy ports.

Geyser Setup Wizard

Set up Geyser for Bedrock cross-play — choose server or proxy install, ports, Floodgate auth, and download config snippets.

Where will Geyser run?

Geyser lets Bedrock players join your world. Choose whether it sits on the game server or on your proxy.

On the game server Install Geyser (and usually Floodgate) as a plugin on Paper, Purpur, or Spigot. On Velocity / BungeeCord Install Geyser on the proxy and forward Bedrock players into your network.

Ports & address

Bedrock joins over UDP. Keep your normal game port for everyone else.

Bedrock UDP port

Default is 19132. Open this UDP port publicly for Bedrock.

Remote / game port

Port Geyser uses to reach the game server or proxy (usually 25565).

Public address

Hostname or IP Bedrock players type — e.g. play.example.com

Compression level

Use -1 for default. Higher values save bandwidth but use more CPU.

Passthrough MOTD Show your server MOTD in the Bedrock server list.

Authentication

Choose how Bedrock players sign in when they join through Geyser.

Use Floodgate Recommended. Lets Bedrock players join without owning a Java account.

Online-mode backend Keep this on for public servers. Turn off only for carefully controlled offline networks.

Review & generate

Confirm your Geyser setup, then generate config snippets and a checklist.

Generated Geyser output

Copy each snippet into Geyser and Floodgate, then restart the server or proxy.

Firewall ports to open

Next steps

What Geyser does

Geyser is the bridge that lets Bedrock Edition players join your existing world. You install it on the game server itself or on Velocity/BungeeCord when you run a network. This wizard stays focused on that Geyser path — ports, auth, and the config pieces you actually need.

Wrong UDP ports or auth modes are the usual reasons Bedrock clients time out. Follow the generated firewall table so UDP 19132 (or your custom Bedrock port) and your game/proxy port both reach the host.

Floodgate and authentication

Floodgate is recommended when Bedrock players should join without a linked account. The wizard generates Floodgate notes plus a Geyser config.yml snippet with the matching auth-type. Keep online-mode on for public servers unless you run a carefully controlled offline network.

Test with one Bedrock device on mobile data and one on Wi‑Fi so you catch local NAT issues separately from server firewall mistakes.

Go-live checklist

Install Geyser where you chose (server plugin or proxy), open the listed ports, merge the snippets, restart, and join from Bedrock with your public address and UDP port. Other clients keep using the normal TCP port or domain.

Use our DNS generator for clean hostnames and the port checklist if your host uses UFW or firewalld.

Common questions

Do I need Floodgate?: Floodgate is recommended when Bedrock players should join without a linked account. Enable it in the Auth step to get matching config notes.
Which port does Bedrock use?: Bedrock commonly uses UDP 19132. Geyser listens there while the game port usually stays on TCP 25565 unless you changed those values.
Should Geyser run on Velocity?: Yes, for networks. Choose “On Velocity / BungeeCord” in step 1 so the checklist keeps backends private and opens only the proxy ports.