Java vs Bedrock: how crossplay actually works

Why there are two Minecrafts

Minecraft was originally written in Java — hence the name — and that version, now called Java Edition, ran on Windows, macOS and Linux. It was open enough that a modding community grew around it almost immediately, and that community is a large part of why the game became what it is.

Java is a poor fit for phones and consoles, so a separate version was written from scratch in C++ for those platforms. That codebase became Bedrock Edition, and it now runs on Windows 10 and 11, iOS, Android, Xbox, PlayStation, Nintendo Switch and Fire devices. One engine, many platforms, all able to play with each other.

The result is two games that look almost identical, play almost identically, and cannot natively talk to each other at all. They use different networking protocols — Java runs over TCP, Bedrock over UDP — with different packet formats, different world formats and different default ports. A Bedrock client pointed at a Java server does not connect and fail gracefully; it does not recognise anything on the other end.

The differences that actually matter

Feature parity has narrowed enormously over the years. Terrain generation, biomes, mobs and blocks are broadly the same. What remains different is worth knowing.

Combat feels genuinely different

This is the difference players notice first. Java has an attack cooldown: swing too fast and your hits do a fraction of their damage, so combat is about timing your swings to a rhythm. Bedrock kept the older model with no cooldown, where clicking faster is straightforwardly better.

Neither is wrong, but the muscle memory does not transfer. A Java player moving to Bedrock underperforms because they are pausing between swings for no reason; a Bedrock player moving to Java underperforms because they are spamming clicks and landing weak hits.

Mods versus Marketplace

For many players this decides it. Java's modding scene is vast, free, and community-run — performance mods, quality-of-life mods, and total conversions that amount to different games. Bedrock has the Marketplace, which is curated, paid, and much more limited in what it can change. There is no Bedrock equivalent of installing Fabric and running a hundred mods.

Redstone: the big one

If you build technical contraptions, this section is the reason you cannot simply move between editions.

Redstone behaves differently in the two versions, and not cosmetically. Java has a long-standing quirk known as quasi-connectivity, where a piston can be activated by a power source diagonally above it — an artefact of very old code that the community built on top of for years. Bedrock does not have it. Bedrock also updates redstone components in a different order, which changes the timing of anything sensitive.

The practical consequence: a large share of the redstone tutorials on YouTube are Java-specific and will not work if you build them on Bedrock, usually with no indication of why. Flying machines, many piston doors, and most compact item sorters fall into this category.

Mob farms are affected too, since spawning rules and despawn ranges differ. Rates that a Java tutorial promises are frequently not achievable on Bedrock with the same build, and vice versa.

How one server serves both

So if the protocols are incompatible, how does a single address accept both?

The answer is a translation layer. The standard solution — used by essentially every server that advertises Java and Bedrock together — is an open-source project called GeyserMC. It sits in front of a Java server and acts as a bidirectional translator: it accepts Bedrock connections on the Bedrock port, converts Bedrock packets into their Java equivalents, passes them to the server, then translates everything coming back the other way.

The Java server never knows it is talking to a phone. As far as it is concerned, every connection is a Java client. The Bedrock player, meanwhile, sees a normal Bedrock server. Both sides are being lied to convincingly, in real time, for every packet.

There is a second problem: identity. Java servers authenticate against Mojang's servers using a Java account, and a Bedrock player does not have one. That is handled by a companion plugin, usually Floodgate, which lets Bedrock players in using their Xbox Live identity instead. This is why Bedrock players often appear with a small prefix on their username — commonly a full stop, as in .PlayerName — marking them as arriving through the bridge rather than through a Java account.

What this means in practice

Crossplay through a translation layer is very good, and it is not invisible. Things worth knowing:

• Inventory and UI screens are the hardest thing to translate, because the two editions handle them quite differently. Custom menus built by server plugins occasionally render awkwardly on Bedrock.
• Combat mechanics follow the Java server. If the server is Java-based, Bedrock players are subject to Java's cooldown rules even though their client behaves as though there is no cooldown. This takes adjusting to.
• Redstone follows the server too. Build Java designs, regardless of which client you are on.
• Resource packs and custom models may not translate perfectly to Bedrock clients.
• Both editions need the right port. Java clients use 25565, Bedrock clients use 19132, on the same address. Putting the wrong port into a Bedrock client is the most common join failure there is.

None of this stops a Bedrock player on a phone and a Java player on a desktop building the same house together, which twelve years ago would have sounded like nonsense.

Which should you buy?

If you already own one, keep playing it. Both work here. If you are starting from scratch:

Buy Java if…

You have a reasonable Windows, Mac or Linux computer and you care about mods, technical redstone, or the wider community's content. Java is where the modding scene lives, where most tutorials are made, and where snapshots let you try new features early. It is the better long-term choice for anyone who wants to go deep.

Buy Bedrock if…

You mostly play on a phone, tablet or console, or your PC is not strong enough to run Java comfortably. Bedrock is meaningfully lighter on hardware and much more forgiving of a modest machine — which matters. It also handles split-screen on consoles, which Java cannot do at all.

The South African angle

One consideration specific to playing here: Bedrock is the pragmatic choice if you are on mobile data or a modest machine, both of which are common. Java is the choice if you want the depth. Since a good local server accepts both, you are not choosing which of your friends you can play with — which used to be the real cost of picking wrong.

Whichever you land on, the ping guide matters more to how the game feels than the edition does.

Frequently asked questions

← All guides