Minecraft · Editions
Java and Bedrock are the same game only in name.
The two editions look alike and behave alike, but they are separate products with separate clients, separate accounts and separate server software. Which one you host is really a question about who you want to be able to join.
Two editions, two communities
Java Edition is the original, and it lives only on computers. It is the edition that mods and server plugins were built around, and it uses a Java account rather than an Xbox Live one. If you have ever installed a modpack or joined a server running Paper, you were on Java.
Bedrock Edition is the one most people meet first, because it is on phones, consoles and the Windows app. It signs players in through Xbox Live and its customisation arrives as add-ons and behaviour packs rather than a server plugin API. Players across all its platforms can join the same Bedrock world, which is its great advantage.
Who can join what
| Edition | Players run it on | Server software | Client needed |
|---|---|---|---|
| Java Edition | Windows, macOS and Linux PCs | Paper, Purpur, Spigot, Fabric, Forge, NeoForge or Vanilla | The Java Edition client and a Java account |
| Bedrock Edition | Phones, tablets, consoles and Windows | Vanilla Bedrock | Any Bedrock Edition client signed in to Xbox Live |
| Java + cross-play | A Java server with a translation layer | Java software plus Geyser and Floodgate | Both Java and Bedrock clients |
Cross-play with Geyser and Floodgate
If your group is split across a PC and a few phones, you have two sensible routes. The first is to host a Bedrock server and have everyone play Bedrock. The second is to host a Java server and add the Geyser and Floodgate plugins so Bedrock players can join it.
Geyser translates Bedrock’s protocol into the Java protocol the server understands, and Floodgate lets Bedrock players connect without needing a Java account. Together they make one server reachable from both editions. On paper that is exactly what a mixed group wants.
- Some mechanics and interfaces do not translate cleanly, so gameplay can differ slightly between Java and Bedrock players.
- Plugins that assume a Java client, or read Java-specific player data, may behave unexpectedly and are worth testing.
- Console players bring their own limits, from controller input to what their platform allows.
- Treat cross-play as a convenience layer on top of a Java server, not as native support from either edition.
Plugin and mod ecosystems
The clearest practical difference between the editions is what you can add to the server. Java has two deep, mature worlds: server-side plugins on Paper, Purpur and Spigot, and mod loaders in Fabric, Forge and NeoForge. Plugins change behaviour without altering the client, while mods add new content and require every player to run the same mods.
Bedrock’s model is different. Customisation arrives mainly through add-ons and behaviour packs, which is a lighter and more contained way to change the game but a smaller server-side surface than the Java plugin API. If your plans involve running a network with permissions, minigames, custom items or deep automation, that work belongs on Java.
Accounts, installs and updates
The accounts are a quiet but important difference. A Java player needs a Java Edition account and installs the game client on a computer. A Bedrock player signs in with an Xbox Live account and usually already has the game on their device, whether that is a phone, a console or the Windows app, with no separate client to install.
Updates follow different rhythms too. When a new Minecraft version arrives, the Java server jars wait for their plugin and mod ecosystems to catch up before they are safe to run, which can take time. The Bedrock server ships with the game itself and tends to move with it. Neither is better, but if you run a heavily modded or plugged-in Java server, patience on version day is simply part of the deal.
Ports, addresses and connecting
Each edition has its own way of being reached. A Java server typically listens on port 25565, with extra servers on nearby ports such as 25566. To join, a Java player adds the server address and port in their client. Bedrock uses port 19132 and its own add-server flow inside the game.
This is worth knowing when you pick a plan, because the edition decides which server software the panel installs. The Bedrock hosting page covers the Bedrock specifics, and the server software comparison covers the Java jars in detail.
Which should you pick?
- Everyone plays on a PC and you want mods or plugins: Java.
- Your friends are on phones and consoles: Bedrock, where they can all join natively.
- Your group is mixed and you want one server: Bedrock, or a Java server with Geyser and Floodgate if you need Java plugins.
- You want a technical, near-vanilla world and a mature server ecosystem: Java.
- You want add-on style content rather than server plugins: Bedrock.
- You are not sure yet: start where your players already are, because a server nobody can join is not a server.
The edition is one of the few choices on this list that is genuinely hard to undo later, because it determines who can connect. Decide it around your players, not around a feature list.
Java and Bedrock — questions
Can Java and Bedrock players play together?
Not natively. The two editions speak different protocols and use different accounts, so a Java server does not accept a Bedrock client and the reverse. Cross-play is possible by adding a translation layer such as Geyser, usually with Floodgate, on top of a Java server, but it is a bridge rather than native support.
Which edition has more plugins and mods?
Java, by a wide margin. Its server-side plugin API and its mod loaders have years of ecosystem behind them and a very large catalogue. Bedrock customisation works mainly through add-ons and behaviour packs, which is a different model with a smaller server-side surface.
Do I need a separate server for each edition?
If you want to support both natively, yes, or you run a Java server with a cross-play layer. Native is the more predictable path and cross-play is the more convenient one. The right answer depends on which devices your players actually own.
Does cross-play change how the game plays for Bedrock players?
It can. A translation layer cannot reproduce every Java mechanic and interface perfectly, so some features behave differently, some plugins that read Java-specific data can misbehave, and console players bring the usual controller limits. It works, but it is worth testing before you promise a group a seamless experience.
Pick the edition your players already own.
Rynox can run the Java jars and the Bedrock server, so the choice is about who joins, not about what the platform supports. Compare plans on the pricing page.