If the game keeps refusing your invite, one of three things is almost always true: you're on Bedrock and haven't joined the Realm yet yourself, you're on Java and nobody holds an open invitation slot, or the friend's Microsoft account isn't the one you typed into the invite box. "Invite" is also three different buttons in Minecraft β€” the initial invitation, the Realm's own "Invite" button once you're inside, and a shareable link β€” and the game only responds to the route that matches your platform and your role. Work through the triage below in order and you'll hit your specific blocker in minutes rather than reinstalling the game on a hunch.

How Invites Actually Differ Between Java Realms and Bedrock Realms

Only the Bedrock edition's Realm subscription carries a share link. A Java Realm has no such thing β€” its invite permission list is capped at 10 player entries, with the owner holding one of those slots. That is why instructions telling you to "copy the link" simply don't work if you're renting a Java Realm, and why Bedrock players sometimes wonder where their permission list went: Bedrock swaps it for a share link and a set of toggle switches.

The second structural difference is account type. A Java Realm invites by Minecraft username, which changes when the player changes their profile name. A Bedrock Realm invites by Microsoft/Xbox gamertag, delivered through the Xbox network. Type the right string into the wrong field and the game reports a failed invite without ever telling you why.

Third, ownership transfer behaves differently. Bedrock owners can transfer a Realm to another player from the settings menu, and the new owner must accept before the change takes effect. On Java, ownership cannot be handed over this way, and a lapsed subscription locks the invite list until the owner renews. Confusing a Bedrock transfer with a Java username change is one of the most common misdiagnoses.

Fourth, every one of these routes depends on a setting that lives outside Minecraft: "You can join multiplayer games" in Xbox privacy settings. According to Microsoft's Xbox support documentation, when that setting is blocked, the account cannot play multiplayer in any title, including a Realm it was explicitly invited to β€” and the owner sees a generic invite failure rather than the real cause. Check the friend's side before you rebuild your Realm.

Triage First: Five Cause Categories That Cover Every Failed Invite

Work through these five categories in order. Each one takes under a minute and each eliminates a group of causes, so you're not guessing once you reach the fix that applies.

1: Owner-side subscription and role. Open the Realm in the game and confirm your own access shows as Owner. An expired subscription, a gamerpic still showing "Invited" instead of a role, or an account that was never actually the purchaser all produce failures that look like the friend's fault. 2: Invite route matched to platform. Bedrock: share link plus the "Join Realm" toggle. Java: the 10-slot player list. Console child accounts: storage capped by the parent's console settings. 3: The friend's typed identity. Exact Minecraft username for Java, exact Microsoft gamertag for Bedrock. An email address typed here fails every time β€” the field wants a gamertag or username, not a login. 4: The friend's account state. Not signed in, no Xbox profile created, multiplayer privilege blocked by a parent, or on a different edition than the Realm. 5: Network path. The friend's connection type, firewall, or VPN intercepting Minecraft's traffic, or a router that blocks the game's outbound ports.

If the invite fails at step 2 or 3, you'll fix it inside Minecraft. If it fails at step 4 or 5, the fix is on your friend's device or account.

Step-by-Step: Sending a Working Bedrock Realm Invite

Bedrock gives you two routes, and the Realm must recognize you as Owner or a permitted member before either one works.

1: Launch Minecraft Bedrock and select Play, then Realms. 2: Select your Realm. If you see "Join Realm" instead of "Play", you haven't joined it yet β€” select it and wait for the world to load. Invite controls stay hidden until you're inside. 3: Open the pencil (Edit) icon on the Realm tile, then Members. 4: Type the friend's exact Xbox gamertag into the invite box and select Invite Player. The gamertag is the handle shown under the profile name on Xbox β€” not the display name, and not an email address. 5: Watch that name appear in the members list. If nothing appears after the button press, the gamertag didn't resolve to an Xbox profile. 6: For the link route, open Settings on the Realm, set Invite Links to On, tap Create Link, then Copy Link and send it through Minecraft chat or a text message. 7: On the friend's device, have them open Play β†’ Realms β†’ Join Realm and paste that code. The same window takes a Realm ID if you'd rather share that.

If the invite still fails, have your friend check Settings β†’ Account in Minecraft to confirm which Microsoft account the game is signed into, then check that their Xbox profile exists at all β€” a Microsoft account with no Xbox profile cannot join anything on the network. A parent-managed child account that can't switch to an adult account needs a signed-in adult on that console to change the privacy setting.

Step-by-Step: Sending a Java Realm Invite When the Screen Refuses

The Java flow is shorter on paper and stricter in practice, because the page simply greys out controls when a condition isn't met.

1: Open the Minecraft Launcher and select Minecraft: Java Edition, then Play. 2: Choose Minecraft Realms from the main menu and select your Realm. 3: Select Configure Realm, then Players, then Invite Player. 4: Type the friend's exact Java username. This is the profile name, not the email on their Microsoft account and not their gamertag. 5: Select Invite. If the name doesn't turn up, ask the friend to sign in at minecraft.net and read their profile name back to you letter for letter. 6: For a whitelisted Realm, have the friend launch Java, open Minecraft Realms, switch to the Friends tab, select your Realm, and accept β€” after which add them to the whitelist if your Realm runs one.

If the Invite Player control is missing or the page won't react, the causes are limited: your subscription has lapsed, you aren't signed in with the account that owns the Realm, or all 10 player slots are occupied β€” the owner is one of those 10, "Players" and "Operators" lists are separate, and removing an entry frees the slot immediately. One real drawback of Java Realms worth knowing before you chase a technical fix: there is no share link and no ownership transfer, so every invite depends on the owner staying active and the subscription staying paid.

The Ten-Slot Ceiling Nobody Mentions Until It Bites

The Java Realm player list, set by Mojang's Realms documentation at 10 total entries including the owner, is the quietest failure in this whole troubleshooting tree. You copy a username correctly, press Invite, and the list rejects the eleventh name with no explanation. The count is a total, not an additional allowance. Existing names you've removed still count toward the list until the removal saves, so delete an inactive member, close the page, and reopen it to verify the list length.

Bedrock's ceiling runs higher but arrives in stages. Microsoft's Minecraft help documentation on Realms lists 3 players for the one-month and six-month Realm subscriptions and an 11-player cap for the 10-player subscription tier β€” confirm the current ceiling on the Realm's own Members screen before assuming you've hit it, because these limits have been revised. A Bedrock Realm already limited to 3 can invite exactly one more visitor at a time before it needs the tier that raises the ceiling.

Practical workaround for either edition: rotate access. Swap one long-inactive member for the friend you're trying to add, keep a written list of who holds a slot, and re-add the inactive member when a spot opens. That keeps you under the ceiling without buying anything.

When Invites Fail on Consoles and Child Accounts

Bedrock invites to a Nintendo Switch, PlayStation, or Xbox player fail for a reason the game can't display: the console's online service subscription or the platform's privacy setting is blocking multiplayer. Microsoft's Xbox support documentation explains that a child account inherits the parent's "You can join multiplayer games" setting, and that the parent must change it on the account level before the child can accept any Realm invite.

Two other platform-specifics matter. A Java-account friend cannot join a Bedrock Realm β€” convert the world to Bedrock, or invite that friend to a Java Realm in the same version. And the Edge browser's Xbox website, not Minecraft's in-game menu, is where a browser-only player manages invitations, which trips up anyone who bought the title through a mobile app: the game remembers how you purchased it and hides unsatisfied invite routes.

If the console play session is the issue, reduce the audience. On Xbox Series X|S and Xbox One, Settings β†’ General β†’ Online safety & family β†’ Privacy & online safety β†’ View details & customize β†’ "You can join multiplayer games" is the switch. Recheck before the next session; parental revocations take effect even after you've signed in once.

The Friend's Side: Reading the Invitation Without Sending One Back

An invitation is one-directional in Minecraft. As Bedrock's own onboarding flow explains, the person receiving it must open Realms and either accept the invite directly or join with the code, then select the world's name β€” the arrows in the "Manage World" section do nothing until they're a member. If their account already sits in the members list, the friends screen will read "Join Realm" instead of "Invite". The type of that button, not the owner's screen, tells you which side of the interaction is blocked.

Bedrock buttons and their meanings:

Button you see Meaning Correct action
"Play" on the Realm tile You're in and the Realm is running Confirm your role from the Edit screen
"Join Realm" Invite received, not yet accepted Select it, wait for the world to load
"Resume" Realm idle and needs starting Select it, then invite from Members
"Invite" on the pencil screen The owner hasn't added you as a member Ask the owner to add the gamertag

For indenting-code flows there's no substitute for contact: ask the friend to screenshot their Realms screen and send it, then read the exact button label against the table. The same test applies on a Java whitelist β€” if their Friends tab shows an Accept button on your Realm, they see the invite; if it shows nothing, the username in the list is wrong.

Account and Version Mismatches That Block the Invite

Mojang's own Realm FAQ names the first match failure: the invite must be sent to the exact username that signs in at minecraft.net, and a username that doesn't resolve appears in the invite list as a name that can never be accepted. The profile-name rule bites twice for the same person if they recently changed their profile name mid-session, because the launcher caches the old name until restart.

Version mismatches break the other half. Bedrock builds across Windows, Xbox, PlayStation, Switch, iOS, and Android only joint a Realm when their versions are compatible, and preview or beta builds are separated from general release through a known separation managed by Mojang. A Java Realm doesn't know about preview builds at all: a friend on a snapshot build can see the Realm but fails at the join stage, and the fix is to switch that installation back to the latest release and launch again.

The account-type mismatch is the one to rule out first. A Microsoft account that has never created an Xbox profile holds a valid Minecraft purchase and still cannot be added to a Bedrock Realm, Open the Xbox app once and accept the gamertag prompt and the invite lands. The same friend on a Java username can be invited before the profile exists, because Java Realms never consult Xbox.

One more version-specifics case needs naming: a Bedrock owner who purchased through a retail key rather than a Microsoft Store license can't transfer Realm ownership through the settings menu, because the transfer option depends on the purchase being linked to the same account as the gamertag. Check the "How to purchase" for your installation is licensed to one Microsoft account before you plan a transfer.

Using Commands and Settings to Confirm Roles Instead of Redoing the Same Click

You don't mastermind a Realm through guesswork. Run /team list β€” this Java command confirms whether the account the game believes it's logged in as has that name β€” after pressing Invite, and compare it with the profile name you typed. On Bedrock, /reload after a purchase or multiplayer switch re-syncs admin privileges that the game has cached from before your subscription state changed. A quickly stale role after a purchase is one of those cases where re-entering Realms from the main menu helps more than the fix inside the Members page.

Permissions design carries a longer-term answer for friends who'll return. Once a player is on the Bedrock Members list, the pencil icon beside their name toggles the three roles: default members can play and chat, operators can run commands and break blocks, visitors are restricted to the world's designated area. Java's equivalent split into Players and Operators gives you the same control, and adding a name to the Players list grants no command access by itself. Setting role expectations at invite time prevents a second round of "it says I can't build anything," which is a permissions failure that looks like a Realm failure.

For a larger circle than your subscription comfortably serves, the Java side can't exceed its 10 entries; put the world on a private hosting server instead, or convert the world to Bedrock and use the tiered Realm. The wrong fix is to reuse the same username on two accounts: the game treats a duplicate as the same owner and refuses.

Rebuilding Trust Around a Failed Invite: Checking the Realms Service

Instead of chasing the same failure screen, rule out the service in under a minute. Check Microsoft's official Xbox status page and Mojang's help articles for an active Minecraft Realms incident β€” Microsoft publishes a per-service status, so a Realms incident that affects invitations will not affect your friend on a regular multiplayer world, and a friend can play freely in a server while a Realm ticket fails. Realms service interruptions happen under repeated ticketing and are not your fault.

Connection type matters too. The Realm service routes console editors through both IPv4 and IPv6; if your friend connects on a network with IPv6 blocked and no fallback, the invite attempt returns a generic join failure. Trying a mobile hotspot on the friend's phone isolates this in one test. If they connect successfully, ask the network admin whether the firewall blocks Minecraft's ports; if the same failure persists on the hotspot, it's service or permission.

Then check the prior fix program's elements in sequence: repeat the exact invite from a desktop installation once services are clean. Do not reinvite a third time until both the subscription page shows active and the Realm is re-opened from scratch. Repeats without new data just burn the same error.

FAQ

Why does the Realm show my friend as invited but the invite never arrives?

Because the button press created a pending entry, not a delivered message β€” and pending entries never expire on their own. Typing a gamertag often creates a member with a role of "invited," so confirm the friend is signed in with exactly that Microsoft account, then delete the pending entry from the Members screen and re-add it while the friend keeps the Realms menu open on their own device.

Can my friend join my Bedrock Realm with a Java username?

No β€” Bedrock Realms match Xbox gamertags, and a Java username resolves to nothing on that list. The two editions never cross-join, so the only routes are converting the world to Bedrock and re-inviting, or renting a Java Realm and inviting the Java username there.

What does a failed Realm invite actually cost?

A Java Realm failed by an expired subscription stays locked until renewal at Mojang's published subscription rate, and the invite list holds at 10 β€” nothing is lost, but the fix only arrives when the bill is paid. A Bedrock Realm stuck on its 3-player tier needs the higher tier to serve a bigger group; check the current tier prices against your play group's size before upgrading blindly.

Why does the Realm let me in but not my friend?

Final permission isn't binary. Your friend may hold a role that lacks build access, be on a whitelist you cleared, or be signed into a child account whose parent revoked multiplayer that same day. Snapshot their Members entry and role alongside their privacy settings before changing anything on your side.

How do I let an invited friend onto a Realm whose owner already left?

In Bedrock, the existing owner transfers the Realm in preferences and the recipient accepts. In Java, no transfer exists β€” either the owner signs back in and invites from Configure Realm, or you rebuild the world and re-add your friend. A transfer does not require either party to be online at the same moment; the acceptance side does.

A Realm ID is the world's fixed identifier, typed into the main Join Realm screen and unchanged for the life of the Realm. An invite link is a toggle you turn on for new members first, then swap it off when you're done handing it out; leaving the toggle on keeps the same code valid indefinitely.

Does an invite expire if my friend ignores it for a week?

In Bedrock it doesn't expire on its own β€” the entry waits in the Members list until you remove it, and a linked invite stays live while links are enabled. In Java the entry holds its slot and may be removed and re-added freely, but the slot ceiling applies, so a forgotten invite is the common reason a fresh one fails.