Your Java server works. Your friend plays on a phone. Another friend uses a console. Getting everyone into one world is possible, but installing a bridge is only half the job: the address, account flow and everyday gameplay must work for each person.
This guide is for owners adding Bedrock access to a Java community. It follows a single-server Paper deployment, then explains when a proxy or standalone bridge makes sense. It does not convert a Java world into a Bedrock world. If you only want somewhere to play, start with the Bedrock server directory and check the listing's connection details.
Geyser, Floodgate and server software: three different jobs
Geyser translates communication between a Bedrock client and a Java server. The world still runs on the Java server, so its rules and mechanics remain the starting point. Floodgate handles a different problem: it lets authenticated Bedrock players join without also needing a Java account. Bedrock players still need their legitimate Bedrock/Microsoft access; this is not a cracked-server switch.
| Component | Job | What it does not do |
|---|---|---|
| Paper | Runs the Java world and its supported plugins. | Does not by itself accept Bedrock clients. |
| Geyser | Bridges supported Bedrock clients into a Java server. | Does not make Java-only client mods available on Bedrock. |
| Floodgate | Provides the Bedrock account authentication path. | Does not merge every existing inventory or permission record automatically. |
| ViaVersion, when required | Helps bridge supported Java protocol versions. | Does not add all newer gameplay features to an older world. |
Read the current compatibility guidance before choosing a server build. A compatible login is not proof that a custom inventory menu, combat plugin or resource pack behaves well on another device. Our Minecraft version compatibility guide explains why the client version and server version are separate checks.
Choose the smallest deployment that serves your players
| Approach | Use it when | Operational cost |
|---|---|---|
| Paper plugins | You run one Java server and control its plugins folder. | One process to restart; easiest starting point for this walkthrough. |
| Proxy installation | You already operate a supported proxy and multiple backend servers. | Forwarding and backend access controls must be correct across the network. |
| Standalone Geyser | You deliberately want the bridge to run as a separate process. | Another process, destination address and authentication configuration to maintain. |
| Native Bedrock server | Your group wants a Bedrock-only world and its mechanics. | A different server ecosystem; not a route for ordinary Java clients. |
Do not add a proxy solely because a large network uses one. For a small community, every extra component adds a place where the published address, firewall and account forwarding can disagree. Conversely, if a proxy already owns player connections, follow the proxy-specific instructions instead of installing duplicate bridges randomly across backend servers.
Make a one-page deployment record: public Java address, public Bedrock address, bridge location, selected transport, allocated ports, backend destination, authentication mode and who can change the configuration. This is especially useful on managed hosting, where the number shown in the panel may be an allocation rather than your usual Java port.
Install on a Paper test server
- Prove the baseline. Join with Java, place a block, leave and rejoin. Save the startup log. If that fails, fix Java access before introducing another edition.
- Download from the project. Use the GeyserMC download page and select the Paper/Spigot artifacts, rather than a reuploaded bundle.
- Stop the test server and install. Put the matching Geyser and Floodgate plugin files into its plugins directory. Start it once so their configuration files are created, then inspect startup errors before editing anything else.
- Choose account handling. For Floodgate access, set Geyser's generated authentication setting to
floodgate, following the Floodgate setup instructions. Restart after changes. - Keep Java authentication intact. For this direct Paper setup, do not solve a Bedrock login problem by turning off Java authentication. Proxy configurations have separate rules and are outside this direct-server example.
- Record what changed. Save the two plugin versions, the edited settings and the restart result. That gives you a short rollback path when an update causes trouble.
Use your installed build's generated configuration. Copying an entire old file can silently preserve obsolete options or overwrite defaults that changed for a reason. If a tutorial's folder name differs from yours, locate the folder named in the current startup log rather than creating a second empty one.
Minecraft Java & Bedrock Crossplay Server (GeyserMC Tutorial)
KasaiSora. A visual introduction linked by the Floodgate project. Treat its interface and networking steps as version-specific; use the current written documentation for configuration.
Watch on YouTubePlan the connection route before opening ports
The current Geyser setup guide includes NetherNet and a combined NetherNet/RakNet mode. Its present instructions require the Geyser port over TCP and UDP; combined mode also uses a separate UDP WebRTC port. Older UDP-only tutorials do not describe every current deployment. Confirm the transport supported by your installed build and host before applying an example.
Keep an allocation worksheet rather than assuming everything belongs on 19132. Write one row for Java, one for Geyser and, if applicable, one for its additional transport port. Include the protocol, internal destination and public port. Ask the host to confirm that the allocation supports the necessary protocols. On self-hosted systems, check both the operating-system firewall and the router.
Test from outside the hosting network. A successful connection on your own Wi-Fi does not establish that your public route works. Ask a tester to record the exact address, port, client version, time and error message. Do not publish a private LAN address as the public server address. Avoid repeatedly changing plugins when the server log never sees the attempted connection.
When using NetherNet, review the project's HTTPS signaling guidance as part of the public setup. Leave transport-specific examples to that maintained documentation. Your job as an owner is to record which route you deployed and test it with the clients you actually support.
How to Setup Geyser + Floodgate on Minecraft Server | Java Bedrock Crossplay 2026
GigaNodes. Shows installation through a hosting panel. The panel and earlier port guidance are examples, not a replacement for the current transport instructions above.
Watch on YouTubeProtect account identity before inviting the whole community
An account appearing in chat is not enough. Log in with a non-operator Bedrock tester, give that account an ordinary permission group, claim a small area and put an inexpensive item in a chest. Leave, restart the test server, and repeat the login. Confirm that the same account still owns the claim and retains the expected inventory.
Keep the Floodgate key private. Its official setup guide explains key placement for separated components and warns against distributing it. Do not attach the key or full credential-bearing configuration to a public support post. If you use a proxy, follow that platform's forwarding instructions instead of mixing settings from a direct Paper setup.
Do not rename, link or merge accounts while a player is moving valuable items. First identify how your permissions, economy, claims and inventory plugins store ownership. Make a backup and test the account-linking procedure separately if you intend to offer it. A matching visible nickname is not a sufficient reason to overwrite an existing player record.
Run a crossplay acceptance session
| Test | Pass condition | Why it matters |
|---|---|---|
| First login | A fresh Java account and a fresh Bedrock account can join without operator privileges. | Staff permissions can hide missing access rules. |
| Inventory and shops | A player buys, sells, drags items and closes menus without loss. | Custom interfaces may expose input differences. |
| Claims | The owner can build; a visitor cannot modify the claim. | Successful login does not prove protection works. |
| Movement and combat | Ordinary movement, boats, ladders and combat do not cause false kicks. | Anticheat behavior needs real-client testing. |
| Persistence | Inventory, permissions and claims survive reconnect and restart. | Identity mistakes often appear only on the next session. |
| Support route | A player can find the right address and report an issue. | Good setup instructions reduce repeated support requests. |
Design the first five minutes around the least convenient input device in your group. Avoid making a tiny inventory icon the only route out of spawn. Put the survival exit in view, keep essential command instructions short, and provide a written alternative to an elaborate menu. These are design choices, not a promise that every plugin supports every client.
Console access deserves a separate line in your instructions. Some platforms require an additional connection method rather than a standard custom-server entry. Link to Geyser's console guidance, state which devices your own testers used, and avoid promising universal one-click access.
EASY Bedrock & Java Cross-Play Server Tutorial
TroubleChute. A device-oriented crossplay demonstration. Console methods and network configuration can change; check the linked project guidance before following older steps.
Watch on YouTubeTroubleshoot the stage that actually fails
| Symptom | First check | Avoid |
|---|---|---|
| No connection reaches the log | Public endpoint, transport allocation and firewall rules. | Reinstalling account plugins before proving reachability. |
| Address already in use | Another process or duplicate bridge on the selected port. | Choosing a new port without updating the public instructions. |
| Login rejected after connecting | Floodgate loading, authentication mode and supported client/server versions. | Disabling authentication as a general fix. |
| Login works; menus or movement fail | Plugin compatibility and one reproducible action with a normal account. | Changing ten unrelated settings simultaneously. |
| Only a console fails | The console connection method and account/platform restrictions. | Assuming the whole bridge is broken after one device test. |
The official common-issues page is the next reference for specific messages. Preserve the exact error and a short log excerpt around the attempted connection. Replace private tokens and addresses before sharing. If the problem started after an update, compare the last working versions with the current ones before rebuilding the server.
Publish connection instructions people can use
Write two compact connection blocks: one labeled Java with its address, and one labeled Bedrock with its address and port. Add the tested versions and a separate console note. Do not bury the port in a paragraph about community features. Ask someone who did not configure the server to follow those instructions from scratch.
Update your listing after the acceptance test. Compare the information shown in the Java directory and Bedrock directory. If your next challenge is the community itself, the SMP planning guide covers claims, spawn and launch rules. If everyone connects but the world stalls, use our server lag diagnosis guide.
Crossplay questions owners ask
Do Bedrock players need to buy Java as well?
Floodgate provides an authenticated Bedrock route without requiring a separate Java account. Without that route, authentication requirements differ. Check which mode you have actually deployed before advising players to purchase anything.
Will Bedrock redstone farms behave like Bedrock?
The destination is a Java world. Plan around the server's mechanics and plugins, not the edition of the connecting device. Test a small farm before committing scarce resources to a large design.
Can I run a Java client-mod pack for Bedrock players?
A bridge cannot install Java client mods on a Bedrock device. Distinguish server-side changes from features that require a specific client. Advertise only the combinations you have checked.
Why does Java work while Bedrock cannot connect?
They can use different endpoints and transport paths. Verify the Bedrock allocation and whether its attempt reaches the bridge log, then investigate authentication. Java access alone does not validate that route.
Should I change every setting in an older tutorial?
No. Use demonstrations to understand the workflow, then compare the current official instructions with your installed build. Keep a record of deliberate changes so you can reverse one without rebuilding the rest.
Editorial scope: documentation reviewed on October 22, 2026. This is a deployment and acceptance-test plan, not a claim that we tested every host, console or plugin combination.