Bedrock "This Server Is Not Compatible With Your Current Version": How to Fix

That message means your Bedrock app and the server are on two different game drops, and one side has to move to the other's version before you can connect — it's not a network or account problem, since the connection got far enough to compare versions. The full wording is usually "This server is not compatible with your current version," followed by "Try updating your game or contacting the server admin." The frustrating part is that line tells you a mismatch exists without telling you which side is behind, so the actual work here is figuring out the direction.

Java splits this into two separate messages that name the direction for you — "Outdated client!" when you're behind, "Outdated server!" when you're ahead. Bedrock collapses both into the one "not compatible" line, so you have to deduce it yourself by comparing version numbers. If the add-a-server flow itself is still new to you, the walkthrough on joining a server covers both editions, and as a quick reference, Bedrock's default port is 19132 where Java's is 25565.

What the message actually means

A server and a Bedrock client have to be on the same drop to talk to each other. When they aren't, the app reports it with this "not compatible" line instead of Java's two-message split. What it names is a mismatch, not a direction — your app could be behind the server, or it could be ahead of a server that hasn't updated yet. So "update my game" isn't automatically the right move, and assuming it is will send you in circles when the server is the one lagging.

You read your own version in the bottom corner of the Bedrock main menu, on the same screen as the Play button. There's no in-game patch button anywhere — Bedrock only updates through the store or console. The server's drop is shown on its card in the listing. Put those two numbers side by side and that comparison is what tells you which way to move. You can grab a server's exact version from any entry on the listing.

This is also different from a silent connection failure. If the address or port is wrong, Bedrock doesn't give you this message at all — it throws the blank "Unable to Connect to World" with no text, which is a separate problem covered in the Bedrock no-error guide. The "not compatible" wording specifically means the connection got far enough to compare versions and they didn't match.

First, work out which side is behind

Compare your menu version number against the server's listed drop. Most of the time your number is the lower one — you're behind the server, and updating your app is the fix. The less common case is that your number matches or beats the server's and it still won't connect; then the server is the one lagging and there's nothing on your end to change but wait.

A fast sanity test settles which it is. Try a second server you know is on your current drop — pull one from the live rankings — and see if it connects. If that one loads fine, your app and your account are both healthy, and the first server is simply sitting on a different drop than you are. That narrows the problem down to versions in one step.

If your app is behind: update it

For the store apps, the path depends on your platform. On Windows, open the Microsoft Store, go to Library, and hit Get updates; the Xbox app does the same thing under My Library. On phones and tablets, update Minecraft from your installed apps in Google Play or the App Store. Once it's done, fully close the app and relaunch it before you try the server again.

Consoles often don't pull the update right away, so it's worth forcing a check. On Xbox, go to My Games & Apps, then Manage, then Updates. On PlayStation, highlight Minecraft, press Options, and choose Check for Update. On Switch, highlight the game, press + (or Start), then Software Update, then Via the Internet.

The relaunch matters more than people expect. An update that's downloaded but not actually applied still reports the old version number, and that's the usual reason behind "I updated and it still fails." So after updating, go back and re-read that bottom-corner version number to confirm it now matches the server's drop, and only then reconnect.

Why consoles sometimes lag a version behind

Each platform gets its own Bedrock build, and that build has to pass the platform's certification before it can be released. Xbox Game Studios tries to line up availability across platforms, but certification isn't something it controls, so a given platform's build can land late. That's not a fault with your console — it's just the release pipeline.

In practice the rollout is staggered rather than simultaneous, so a console — Switch especially — can sit a version behind everything else for a day or two while its certified build catches up. The hard consequence is that if your platform's build isn't out yet, there's literally no update to install. You'll check the store, it'll show nothing, and waiting for the certified build is the only move. So while you wait, the sensible play is to connect to servers already on your current drop rather than chasing the one server that updated ahead of your console.

When you have to wait for the server instead

The flip side happens when you auto-updated to the newest drop and the server hasn't. Now you're the one ahead, the server trails, and there's genuinely nothing to fix on your side. Server software and the plugins it runs trail Mojang on purpose — owners hold back to test that everything still works before they move up — so a freshly released drop commonly leaves a lot of servers a version behind for days, sometimes weeks.

Your realistic options are short: wait for the server to update, or pick one that's already on your version. The 26.2 list and 26.1 list filter the directory straight to servers on a given drop, and the crossplay servers are built to accept Bedrock clients in the first place. The monthly rankings are a good place to find ones that are clearly live and tend to update quickly after a drop.

How this differs from Java's "Outdated client / Outdated server"

Java does the deduction for you. "Outdated client!" means update your side up to the server; "Outdated server!" means you're ahead and the server is the one lagging. Bedrock's single "not compatible" line hands you neither, so comparing version numbers is how you recover the direction Java would have just told you.

The bigger difference is the room you have to fix it. Java keeps every version you've downloaded and lets you switch installations right in the launcher, so a Java player can drop back down to a server's older version and connect. Bedrock's one auto-updating install removes that option completely — there's no second profile to fall back to, and no version picker to pin an older drop. That's the whole reason a Java player can keep a 26.1 fallback while a Bedrock player can't, and why your room to maneuver is genuinely smaller here. If you want the Java side of this, the outdated client/server guide covers that wording, and updating your client to 26.2 walks through the launcher's version-pinning that Bedrock simply doesn't have.

FAQ

I'm on the same version as the server but still get this — what else could it be?

The overlooked cause is that you're running Minecraft Preview, the Bedrock beta app, instead of the retail one. Preview builds run ahead of the public drop, so the number won't line up with a server on the released version even when the two look close. Switch to the regular Minecraft app, or find a server that's running the Preview build. Failing that, you've probably misread one of the two numbers, so check the menu corner against the server card digit by digit.

My friend can join the server but I can't, and we're both on Bedrock.

Then the two of you are on different drops. One updated and the other didn't, or one of you is on a platform whose build landed later. Whoever gets the "not compatible" message is on the older app, so that's the side that needs to update. If your friend is hosting the world themselves rather than pointing you at a listed server, the same rule holds — your apps have to be on the same drop before the join goes through.

Does an add-on or resource pack trigger this message?

No. This is strictly about the game version, not content. Add-ons, behavior packs, and resource packs don't change the drop your app reports, so they won't cause this error or clear it. If you can reach other servers on your version but not this one, the version numbers are where to look, not your installed packs.