How crossplay works

You don't need to know any of this to play. But if you're curious about why a Bedrock player on a phone can fight a Java player on a desktop in the same world, here's the architecture. The player-facing summary is on the Crossplay page.

The bridge

A server-side translation layer accepts Bedrock connections on UDP port 19132 and translates their packets into the Java protocol the server speaks. The server keeps each Bedrock player's identity distinct from Java accounts.

This bridge handles:

• Packet translation — Bedrock packets in, Java packets out, and back
• Inventory translation — Bedrock's slot-grid vs Java's container-windows
• Block ID mapping — most blocks have a 1:1 Bedrock↔Java match; the few that don't get the closest equivalent
• Item translation — same idea for items, tools, armor, enchantments
• Skin support — Bedrock skins display correctly to Java players

Bedrock sign-in

A second component handles authentication without a Java account. When a Bedrock player connects:

1. Their Bedrock client provides standard Bedrock auth (Microsoft account or device-linked)
2. The bridge gives that Bedrock identity a stable identity on the Java server
3. The player joins the shared world without buying Java Edition
4. Their username appears in chat with a leading dot, such as .YourName

Java players still sign in with a Java account. Bedrock players sign in with their Bedrock account; the dot distinguishes their names when you use commands such as /msg.

Custom biome colors

Sunday Market also maps the world's custom biome colors for Bedrock players.

Some custom biomes have no matching Bedrock ID. The mapping gives Bedrock a nearby vanilla biome look for grass, water and fog, so unfamiliar terrain remains readable.

The mapping happens automatically when Bedrock players connect.

What Bedrock players experience differently

Both editions share the world, but the client experience differs:

• Inventory and chest UIs use Bedrock's native rendering (this is normal)
• Touch controls work; controller works; mouse-keyboard works (Win10/11 Bedrock)
• Some chat formatting (gradients, hover cards) renders simpler on Bedrock — the content is preserved, the richness is reduced
• Proximity voice works only for Java players with its optional client mod; Bedrock players use text chat

Performance

Performance depends on the device, connection and area of the world. Bedrock's phone, console and Windows clients use their own rendering and controls, while the server runs the same world for everyone. Check the feature differences above when deciding which client to use.

See also

• Bedrock tips — controller, touch, hot-bar tips
• Version compat — what client versions can connect
• Connecting from Bedrock — step-by-step setup