Minecraft Bedrock and Java Crossplay: Complete Setup Guide

Why the editions are separate

Minecraft exists as two separate games. Java Edition runs on PC and is the version mods and most large servers are built for. Bedrock Edition runs on phones, tablets, consoles, and the Windows store version, and it's what most players outside PC actually own.

They're written in different languages and speak entirely different network protocols. Out of the box, a Bedrock player simply cannot connect to a Java server — there's no shared language.

Geyser is what bridges them. It's a translation layer that sits on your Java server and converts Bedrock's protocol into Java's in real time. To your server, a Bedrock player looks like any other Java client. To the Bedrock player, your Java server looks like a normal Bedrock server.

How Geyser and Floodgate work

Two separate pieces, and it's worth understanding what each does.

Geyser handles protocol translation — movement, blocks, inventory, chat, all converted between editions live. Install Geyser alone and Bedrock players can connect, but they'll each need to own a Java account to authenticate, which defeats most of the point.

Floodgate solves that. It lets Bedrock players join using their Xbox Live account, no Java purchase required. Floodgate players appear with a prefix — usually a dot, so .Steve — marking them as Bedrock accounts.

Both are free, open source, and run as ordinary plugins on Paper or Spigot. Note that Geyser is a Java-side plugin: your server stays a Java server, and Bedrock players are translated in.

Setting up crossplay

On FlameHost, crossplay is a one-click feature in the control panel — enable it and the plugins are installed and configured for you. If you're doing it manually, here's the whole process.

1. Run Paper or Spigot. Geyser is a plugin, so it needs plugin-capable server software. Vanilla won't work. Paper is the recommended choice.
2. Download Geyser-Spigot from the GeyserMC site and drop the jar into your plugins folder.
3. Download Floodgate-Spigot and add it to the same folder.
4. Restart the server so both generate their config files.
5. Open plugins/Geyser-Spigot/config.yml and set auth-type: floodgate. This is the step people miss — without it Floodgate is installed but inactive.
6. Check your Bedrock port. Geyser listens on UDP, conventionally 19132, separate from your Java port. On managed hosting you'll need to allocate an extra port and set it in the config.
7. Restart and check the console for Geyser reporting that it's started and listening.

The port is the part that catches people on shared hosting. Java runs over TCP, Bedrock over UDP — you need both open, and the Bedrock port must be one your host has actually allocated to you. FlameHost lets you create extra ports from the panel.

How Bedrock players connect

On phone, tablet or Windows:

1. Open Minecraft and go to Play → Servers.
2. Scroll to the bottom and choose Add Server.
3. Enter any name, your server's IP address, and the Bedrock port — the Geyser one, not the Java one.
4. Save and join.

If it fails, the port is wrong nine times out of ten. Bedrock defaults the field to 19132, and if your Geyser is on a different port you must type it in.

Consoles: the awkward part

Xbox, PlayStation and Switch don't let you type a server address. Microsoft locked down third-party servers on consoles, and there's no official way around it.

The workarounds people use, honestly assessed:

• A DNS service that replaces one of the featured servers with yours. Works, requires changing the console's DNS settings, and breaks whenever the service goes down.
• A LAN bridge on your network — software that makes a remote server appear as a local LAN game. Only works for consoles on the same network as the machine running it.
• Playing on a phone or PC instead. Unsatisfying, but it's the only genuinely reliable answer.

None of these are things a host can enable for you. If your group is console-heavy, know this going in — it's a Microsoft restriction, not a limitation of your server.

Differences players will notice

Geyser is impressively good, but the editions genuinely differ and translation can't erase that.

The practical takeaway: crossplay is excellent for survival, creative and building servers. It's a weaker fit for competitive PvP or heavily modded worlds.

Common problems and fixes

"Unable to connect to world"

Almost always the port. Confirm the Bedrock port in the Geyser config matches what players are entering, and that it's a UDP port your host has allocated.

Bedrock players asked for a Java account

Floodgate isn't active. Set auth-type: floodgate in the Geyser config and restart. Installing the Floodgate jar alone doesn't switch it on.

Players connect then time out

Usually resource strain — Geyser translation costs CPU and memory on top of normal server load. Budget roughly an extra 1 GB if you expect several Bedrock players at once.

Skins don't show correctly

Cosmetic and normal. Bedrock skins are fetched separately and occasionally fail to load; it doesn't affect gameplay.

Some blocks look wrong

Translation gaps between editions, most often with newer blocks. Usually fixed by updating Geyser — it's actively maintained and updates frequently.

Running a good crossplay server

• Keep Geyser updated. It tracks both games' updates closely, and an outdated build is the cause of most odd behaviour.
• Budget extra resources. Translation isn't free. If you're at 2 GB with several Bedrock players, expect to need more.
• Avoid heavy PvP rules or accept that combat mechanics differ by edition. Some servers disable PvP entirely for fairness.
• Test on a phone yourself before telling your community it works.
• Publish both ports clearly — Java players need one, Bedrock players need the other, and mixing them up is the most common support question you'll get.
• Pick a node near your players. Bedrock players are often on mobile networks where latency already runs high, so distance hurts them more.

FlameHost includes one-click crossplay and extra ports on every plan, including free ones. See the invite tiers, or read our guide to sizing your server's RAM before you enable it.