Guide How much Minecraft really costs in South Africa — every edition in rand
MinecraftSA

Java vs Bedrock: How Minecraft Crossplay Actually Works

Why there are two Minecrafts, the differences that actually matter, how one server can accept both, and which edition a South African player should buy.

The short answer

Are they the same game?
No. Java Edition is written in Java for PC; Bedrock Edition is a separate C++ codebase for consoles, mobile and Windows. They use different network protocols and cannot natively connect to each other.
Can Java and Bedrock players play together?
Not on their own — but a server running a translation layer such as GeyserMC can accept both at the same address.
Default ports
Java uses 25565. Bedrock uses 19132. Same address, different port.
Biggest practical differences
Java has free mods and an attack cooldown in combat. Bedrock has no cooldown, runs better on weak hardware, supports console split-screen, and handles redstone differently.
Which should you buy?
Java for mods and technical redstone on a capable PC. Bedrock for phones, tablets and consoles. On PC you get both in one purchase.

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, Chromebook, Xbox, PlayStation, Nintendo Switch and Fire devices, with a native Switch 2 version due on 27 October 2026. 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.

Advertisement

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.

Java EditionBedrock Edition
PlatformsWindows, macOS, LinuxWindows, iOS, Android, Chromebook, Fire, Xbox, PlayStation, Switch
ModsEnormous free ecosystem (Fabric, Forge, NeoForge)Add-ons (behaviour and resource packs), free or from the paid Marketplace; far more limited than Java mods
Custom serversAny address, freelyAny address on PC and mobile; restricted on consoles
CombatAttack cooldown — timed swingsNo cooldown — click speed matters
PerformanceHeavier. Mojang’s minimum since July 2026: 4-core CPU, 8 GB RAM (12 GB with integrated graphics) and a Vulkan 1.3 GPU with 2 GB of video memoryGenerally faster, especially on weak hardware
Split-screenNoYes, on consoles
Default port2556519132

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 add-ons: some free, many sold on the curated Marketplace, and all much more limited in what they 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.

Check the edition before you follow a tutorial

If a redstone build refuses to work and you have checked it three times, the odds are good you are building a Java design on Bedrock or the reverse. Search for the design with your edition's name attached before assuming you made a mistake.

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.

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.

Advertisement

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 (Bedrock has Preview builds for the same purpose). 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.

On PC you generally get both

On PC you do not have to choose: “Minecraft: Java & Bedrock Edition for PC” (R567.99 on the South African Microsoft Store when we checked on 20 October 2026) includes both, so you can install whichever your friends play.

The South African angle

Two considerations specific to playing here. Price: Bedrock is much cheaper to get into — about R380 on Xbox or PlayStation and far less on a phone — while Java comes only in the R567.99 PC bundle (see our price guide). Hardware: Bedrock runs well on modest machines and phones, while Java’s requirements went up in 2026. Java is the choice if you want the depth. Consoles can only join Mojang’s featured servers and Realms, so for a local crossplay server with friends, the console players are the ones who need a workaround. 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

Can Java and Bedrock players play on the same server?

Not natively — the two editions use incompatible network protocols. But a server can run a translation layer that converts between them, and then both editions connect to the same world at the same address. The Java client connects on port 25565 and the Bedrock client on port 19132.

What is GeyserMC?

GeyserMC is an open-source proxy that sits in front of a Java Edition server and translates Bedrock Edition network packets into their Java equivalents in both directions. The Java server believes every connection is a Java client; the Bedrock player sees an ordinary Bedrock server. It is the standard way servers offer crossplay.

It is usually paired with a plugin called Floodgate, which lets Bedrock players join using their Xbox Live identity instead of requiring a Java account. That is why Bedrock players often appear with a prefix on their username, commonly a full stop.

Which is better, Minecraft Java or Bedrock?

Neither is better outright; they suit different players. Java has the enormous free modding ecosystem, snapshots, and the redstone behaviour most tutorials assume, but it needs a reasonably capable computer. Bedrock runs on phones, tablets and consoles, performs better on modest hardware, and supports split-screen — but its add-ons, free or paid, are far more limited.

Choose Java if you want mods and technical builds. Choose Bedrock if you play on mobile or console, or your PC is weak.

Do I have to buy Minecraft twice to get both editions?

No, not on PC. The PC product is “Minecraft: Java & Bedrock Edition for PC”, and one purchase gives you both editions under your Microsoft account. On consoles and phones you only ever get Bedrock.

Why doesn't my redstone build work on Bedrock?

Because redstone genuinely behaves differently between the editions. Java has a long-standing quirk called quasi-connectivity, where a piston can be triggered by a power source diagonally above it, and Bedrock does not. The two also update redstone components in a different order, which changes timing.

A large share of redstone tutorials online are Java-specific. Flying machines, many piston doors and most compact item sorters will not work if you build the Java design on Bedrock. Search for the design with your edition's name attached.

Is Minecraft combat different between Java and Bedrock?

Yes, and it is the difference players notice first. Java has an attack cooldown — swinging too quickly does a fraction of full damage, so combat is about timing. Bedrock has no cooldown, so clicking faster is straightforwardly better.

On a crossplay server the mechanics follow the server, so Bedrock players on a Java-based server are subject to Java's cooldown even though their client behaves otherwise.

Advertisement
All guides →
Advertisement