Minecraft server guide
How to make a Minecraft Java and Bedrock crossplay server
Java Edition and Bedrock Edition cannot normally join the same dedicated server because their network protocols differ. A Paper server with Geyser and Floodgate can bridge that gap while keeping one shared world.
Free Vanilla and Paper servers available.
Section 01
What Geyser and Floodgate each do
Geyser is a protocol translator. A Bedrock client connects to Geyser over UDP, and Geyser communicates with the Java server in the form Paper expects. Java clients continue to connect directly to Paper and do not pass through the bridge.
Floodgate supplies the Bedrock identity layer. It lets a signed-in Bedrock player join without authenticating a second Java Edition account, while keeping the Java server's normal online-mode behavior for Java players.
Section 02
Why Bedrock needs a public UDP port
A normal Java server uses a TCP connection. Geyser listens for Bedrock's RakNet traffic over UDP, so shared hosting must expose the selected port for UDP traffic. TCP and UDP can safely use the same numeric port when a node has no spare secondary allocation.
The Java and Bedrock addresses can share a hostname, but the protocols are distinct. Crafty Servers leaves the Java address unchanged and displays the assigned Bedrock hostname and port together in Server settings.
Section 03
Compatibility to test before launch
A basic Paper survival world usually translates cleanly, but Bedrock and Java do not expose every screen, item, command, and movement behavior identically. Test plugins that depend on custom inventory menus, resource packs, protocol packets, or Java-only client behavior.
Bedrock clients also update frequently. Keeping Geyser current matters because a new Bedrock protocol can arrive before a server owner plans a maintenance window. Re-run the dashboard repair action if the plugin files or configuration are changed manually.
- Join once with a Java client and once with a current Bedrock client.
- Test login, chat, inventory menus, portals, commands, and any custom items.
- Confirm the displayed Bedrock hostname and UDP port from a network outside the server host.
- Keep a normal server backup before changing plugins or rebuilding the server.
Step by step
Set up Java and Bedrock crossplay
Choose Paper
Create the server with Paper + Bedrock, or open Settings on an existing Paper server.
Enable Bedrock
Use the one-click control. It prefers a second allocation, downloads Geyser and Floodgate, and writes the listener and authentication settings.
Allow the restart
An online server restarts only after the port, plugins, and configuration are ready. An offline server loads them on its next start.
Copy both addresses
Give Java players the normal server address. Give Bedrock players the Bedrock hostname and UDP port shown in Settings.
Test important plugins
Verify the join flow and any menus, commands, custom content, or anti-cheat behavior with both editions.
Decision checklist
Before inviting Bedrock players
- The Settings page says Bedrock crossplay is enabled.
- You copied the Bedrock hostname and port separately from the Java address.
- A current Bedrock client can reach the server over an external network.
- Important Paper plugins have been tested from both editions.
- Players know that console server-entry options can vary by platform.
Good to know
Frequently asked questions
Is Geyser a separate Minecraft server?
Not in this setup. Geyser runs as a Paper plugin and translates Bedrock connections into the existing Java server, so both editions use one world.
Why does Bedrock use a different port?
Java normally connects over TCP, while Bedrock uses UDP. Geyser needs an assigned UDP port that can receive Bedrock traffic.
What does Floodgate change?
Floodgate lets authenticated Bedrock accounts join through Geyser without also signing into a Java Edition account.
Can I add Geyser to an existing Paper world?
Yes. Enabling Bedrock installs the bridge around the existing Paper server; it does not replace or reset the world.