How to Join a Minecraft Server on a Mac
Join a Minecraft server on a Mac through Java Edition: open the launcher, click Play then Multiplayer, and add the address. Why Bedrock servers can't connect.
You join a Minecraft server on a Mac through Java Edition: open the official launcher, click Play, then Multiplayer, then Add Server (or Direct Connection), type the address, and hit Join Server. Same steps on an Apple silicon Mac (M1 through M4) and on an older Intel one. The one thing worth knowing up front is that macOS only runs Java Edition — there is no Bedrock client for Mac — so you can join Java servers all day but never a Bedrock one. Once you know that, the rest is just a couple of menus.
The steps
Grab the official Minecraft Launcher and open it. Sign in, and make sure Minecraft: Java Edition is the thing selected on the left, not some other product.
Before you click Play, pick a version that matches the server you want. The launcher usually defaults to the newest release, so if the server is still on an older version (say 26.2 while your launcher is on 26.3), choose that version in the version dropdown first — a mismatched client and server won't connect, and this is the most common reason a Mac player gets stuck. More on that below.
Click Play. When the game finishes loading and you're at the title screen, click Multiplayer. That button only shows up here, on the main menu inside the game — not in the launcher.
Now you've got two ways in:
- Add Server saves the server to your list so it's there every time. Click it, type anything you like into Server Name, then type the address into Server Address exactly as the owner gave it to you. Click Done, select the server, and click Join Server (a double-click works too).
- Direct Connection joins once and doesn't save anything. Click it, paste the address, click Join Server. Handy for a server you're only visiting once.
The address is a domain like play.example.com or a raw IP. You only add a port on the end if the server uses a non-standard one — play.example.com:25566, for example. Java's default port is 25565, so you can leave that off; typing :25565 isn't wrong, just redundant. If you're not sure what the address even is, here's how to find a server's IP and port.
The macOS bits that catch people
Gatekeeper on first launch. If you downloaded the launcher from the website rather than the App Store, macOS might refuse to open it the first time. Right-click (or Control-click) the app and choose Open, then confirm. If that doesn't do it, go to System Settings > Privacy & Security, scroll down, and click Open Anyway. This is a one-time thing — once it's open, it stays trusted.
The firewall prompt. At some point macOS may pop up a box: Do you want the application "java" to accept incoming network connections? with Allow and Deny buttons. Here's the part people get wrong — it doesn't matter which one you click, at least not for joining. Connecting to a server is an outgoing connection from your Mac to theirs, and the macOS firewall only governs incoming ones. Click Allow, click Deny, either way you'll still join fine. That prompt only actually matters when you host — Open to LAN, or running a server on the Mac itself — because then other machines need to reach in.
The big one: a Mac can't join Bedrock servers
This trips up more people than any menu setting. If a friend on Xbox, PlayStation, Switch, a phone, or Windows 10/11 hands you a server address, it's almost certainly a Bedrock server, and your Mac cannot join it. Not with a setting or a plugin, and not with any address trick.
The reason is that Java and Bedrock are two different games that speak two different network languages. Java servers listen on TCP port 25565; Bedrock servers listen on UDP port 19132. People sometimes hear "different port" and try typing the address with :19132 on the end into the Java client, expecting that to bridge the gap. It does nothing. Your Java client can't speak Bedrock's protocol regardless of the port, and there's no Bedrock client you can install on macOS to fix it. The Java vs Bedrock split for console and cross-play goes deeper if your group is spread across platforms.
There's one thing that looks like an exception but isn't. Some Java servers run a bridge called Geyser (often with Floodgate) so Bedrock players on consoles and phones can join the Java server. It only lets Bedrock players into Java, not the other way around. It gives your Mac nothing new; you'd still join that server through the normal Java port like everyone else on Java. So if you and your console friends want to actually play together, the realistic path is that they join a Java server running Geyser, or the whole group moves to Java.
Match your version to the server
A Java client and server have to be on the same version to talk. Under the hood that's a protocol number — 26.3 is protocol 777, 26.2 is 776, 26.1 is 775 — but you never see those numbers in the menus. What you match is the plain version: 26.3 client to 26.3 server, 26.2 to 26.2.
When they don't match, the server's line in your Multiplayer list turns red instead of the usual green, and the version label next to it shows in red too. Try to join anyway and you get kicked with the version spelled out — "Outdated client! Please use 26.2" when your client is older than the server, or "Outdated server! I'm still on 26.2" when it's the other way around. That red text is purely a version problem, not a firewall or network issue and nothing to do with RAM. The fix is to go back to the launcher, pick the version that matches the server, and relaunch — not to edit the address.
The trap is leaving the launcher set to "Latest release" and assuming it'll always line up. It auto-updates you to the newest version, so the day a new drop lands, a server still sitting on the previous one will suddenly show as incompatible even though nothing on your end "broke."
More RAM — only if you're modded
By default the launcher hands the game a fixed chunk of memory, around 2 GB, set as a JVM argument that reads -Xmx2G. Plain vanilla survival at a normal render distance is completely fine on that, and bumping it does nothing for a regular server join.
Where more RAM helps is heavy modpacks (Fabric, Forge, NeoForge) or cranking render distance way up. To change it, go to the launcher's Installations tab, click Edit on the installation you use, open More Options, and find the JVM Arguments field. Change -Xmx2G to something like -Xmx4G. Keep it well under your Mac's physical RAM — about half is a sensible ceiling. Handing the game most or all of your memory backfires: it causes long garbage-collection stalls and crashes, so more is genuinely worse past a point. The full walkthrough on allocating RAM has the details.
One thing to be clear about: RAM has zero effect on whether you can connect to a server. If you can't join, adding memory won't help, so don't reach for it as a fix.
Modded also needs the right client profile — the loader and version on your side have to match the modded server. Once you've launched the correct modded profile, though, joining is the same Multiplayer > server list flow as anything else.
When it won't connect
A few errors and what they usually mean:
| What you see | Usual cause |
|---|---|
| Server line red, "Outdated client!" or "Outdated server!" | Client and server are on different versions (e.g. 26.3 vs 26.2). Pick the matching version in the launcher. |
| Failed to connect to the server | Wrong address or wrong custom port. Recheck the spelling and whether it really needs a :port. |
| Connection timed out | Server is offline, or the address/port is wrong so nothing's answering. |
| Connection refused | Something's at that address but nothing's listening on that port — usually a wrong port. |
Most Mac connection trouble comes down to two things: a version that doesn't match, or a typo in the address. Turning off the firewall won't help (joining is outbound, remember), and neither will more RAM. If a server that used to work suddenly won't, check whether the launcher quietly updated you past the server's version; can't join a server after updating to 26.3 walks through exactly that case. The general how to join a Minecraft server guide covers the cross-platform basics if you want them.
Not sure which server to jump on? The live vote-ranked list on the site sorts current, populated Java servers, and you can filter to servers running 26.3 or 26.2 so the version already matches whatever your launcher is set to.
FAQ
A friend on the same wifi opened their world to LAN — how do I join from my Mac?
Open Multiplayer and look at the bottom of the list. A world someone shared with Open to LAN on the same network shows up there on its own, usually named something like "Friend's world," and you click it — there's no address to type. If it doesn't appear, use Direct Connection instead and enter their Mac's local IP plus the port that showed up in their chat when they opened the world, like 192.168.1.20:53412. Both machines have to be on the same network for either route to work.
I clicked Deny on the java firewall prompt and now I want to host — how do I undo it?
Open System Settings > Network > Firewall and click Options. Find the java entry in the list and switch it from Block Incoming Connections to Allow Incoming Connections. Your earlier Deny never affected joining servers, because that traffic is outgoing, but hosting — Open to LAN, or running a server on the Mac — needs incoming connections allowed so other machines can reach you. If java isn't in that list at all, it'll prompt you again the next time you host, and this time click Allow.
Is the Apple silicon version any different from the Intel one for joining servers?
No difference at all. It's the same Java Edition and the same steps, and the current launcher and game run natively on Apple silicon, so you don't need Rosetta or a special Intel build. Forcing Rosetta actually tends to hurt performance rather than help.
I really need Bedrock on my Mac — is there any workaround at all?
Not a clean one. Older Intel Macs could run Windows through Boot Camp and use the Bedrock client from there, but Apple silicon Macs (M1 and up) can't do Boot Camp, and running Bedrock inside a virtual machine is slow and glitchy where it works at all. There's no supported Mac Bedrock build and no emulator that reliably stands in for one. The realistic answer is to run Java on the Mac and pick a Java server to play on.
