Free Minecraft Bedrock Server for Mobile and Console

A group using phones, tablets or Windows Bedrock can play on a compatible native Bedrock server. A group containing Java players needs a different arrangement: a supported Java server with Geyser and suitable authentication for Bedrock access. These two designs share the word Bedrock but do not share the same world format or server software.

This page starts with Bedrock selected in the configurator. That selection does not automatically turn the server into Java crossplay. Decide which design your players need before creating the world. Changing the underlying edition later is a separate world-migration problem, rather than a harmless address change.

Consoles need an additional check. Using Bedrock on Xbox, PlayStation or Switch does not guarantee that the platform lets you add any external server address. Test the actual device connection path before importing a world or inviting everyone. The guide covers those limits separately from the normal phone and Windows setup.

Current free-plan resources and operating rules are displayed above and in the configurator. Free hosting does not include a Minecraft licence or bypass multiplayer account restrictions. Plan around the software actually offered and the devices your group has tested.

Under Windows, a player may own and launch either Java or Bedrock. Ask for the edition on the game's start screen, not just the operating system. Ordinary phone and tablet Minecraft uses Bedrock. Normal Java play on macOS and Linux uses Java clients, which cannot directly enter a native Bedrock server.

For a group using only Bedrock, a native Bedrock server does not require Geyser. For a mixed group, the Java world is authoritative and Geyser translates supported Bedrock connections into it. Confirm that choice before players invest time in buildings and inventories.

Use normal release clients for the first test. Preview and beta clients can use a different protocol from the server's supported release. Record the actual version shown on each device. Everyone saying their game is current does not establish that different platform release channels have delivered the same version.

Every player needs access to Minecraft on the intended device. The free server plan supplies hosting, not a game purchase or account licence. Online multiplayer also needs the relevant account permissions. A family-managed account may require the responsible adult to review its settings.

On consoles, check the platform's current requirements for online play. If a platform subscription is required for that account and device, a server configuration cannot replace it. Treat this as a player-side prerequisite and confirm it before investigating hosting ports.

Friends normally do not need the owner's hosting-management account to join the world. Share the game address and port, while keeping dashboard and file-management credentials private. An in-game administrator role is separate from the login that controls installation and backups.

Make a small device checklist before importing an important world: game launches, account permits multiplayer, appropriate release is installed and an external server route is available. Test one phone or Windows client first, then each required console type. A successful phone connection establishes a useful working reference, but does not confirm a console menu can use the same address.

In the configurator, select Minecraft Bedrock and review software, supported version and plan conditions. If you intend to use add-ons or an existing world, check their requirements against the offered software. A Bedrock label does not imply that every dedicated-server extension is installed or supported.

1. Finish creating the server with the intended Bedrock configuration.
2. Open its dashboard and start the game process.
3. Read the console until startup completes.
4. Copy the assigned Bedrock address and port.
5. Test with a phone or Windows Bedrock client that permits external server entry.
6. Check the remaining devices using that known working endpoint.

If startup fails, resolve the game error first. Repeatedly trying an address cannot connect to a stopped process. If the free plan sleeps while inactive, starting the world can be part of preparing each session. Wait for the startup output rather than assuming the process is ready when the dashboard opens.

Microsoft's Bedrock Dedicated Server introduction explains the native server foundation. Distinguish a self-installed dedicated server from other Bedrock software offered by a hosting service. Use the features and configuration documented for the actual software you selected.

Open Minecraft, choose Play and find the server list. Use the option to add a server where available on the current device and software. Menu wording can vary with language and release; the important fields are the local display name, host address and port.

Choose a display name such as Our World. Enter the host without https:// or a dashboard path. Copy the assigned Bedrock port into its separate field. If the details arrived as a host followed by a colon and number, split them into the appropriate fields rather than pasting an entire web link.

Save and connect. Check the expected spawn and, for an imported world, a familiar building. If Wi-Fi works, a further test on another permitted connection can help establish that the endpoint is generally usable. Consider your mobile data conditions when doing so. An externally hosted server does not need a new incoming mapping on your home router.

A phone changing apps, locking its screen or moving between networks may disconnect without the server crashing. Ask whether other players stayed connected and inspect the console. If the picture is slow but world interactions remain normal for everyone else, compare local graphics settings and device performance before treating it as a server resource problem.

Launch Bedrock explicitly when joining a native Bedrock server. Windows Java uses different menus and a different network protocol. Adding another punctuation mark to a Bedrock address does not let a Java client use the Bedrock listener.

In Bedrock, use the server list under Play and enter the dashboard host and port separately. The saved name is only a label in that device's list. A Java server-list entry does not automatically become a Bedrock entry, even when the underlying group calls both worlds by the same name.

Windows loopback instructions concern particular local arrangements, such as a client connecting to a server on the same Windows device. They are not a routine requirement for an externally hosted server. Avoid applying a local loopback repair to a remote endpoint without evidence that it addresses the actual issue.

If Windows Bedrock succeeds but a phone fails, compare version, copied port, account permissions and network. If all devices fail, inspect the game process and Bedrock listener first. A real second client is more informative for this purpose than a web checker that may only test TCP.

Consoles often lack ordinary arbitrary external-server entry. A featured-server list is not necessarily an input field for your hosting address. Bedrock compatibility and the platform's server-selection interface are separate prerequisites.

The Geyser console documentation describes community connection approaches and limitations. A method may rely on another device on the same LAN or an independently operated connection service. Check its current supported platform and instructions rather than assuming a name mentioned in an old tutorial guarantees success.

Work through the checks in order:

1. Confirm that the console account is allowed to use online multiplayer.
2. Identify an external connection route documented for that console.
3. Check whether a helper device must remain on the same network and running.
4. Use the Bedrock endpoint already tested on a phone or Windows client.
5. Record the original network settings if the documented method requires changes.

A DNS change is not authentication and does not make every server reachable. Geyser itself does not add a console menu option. If none of the documented routes is usable for your group, choose a multiplayer arrangement the devices actually support. Do not promise console access solely because a hosting form includes a Bedrock selection.

Unofficial Console Method via BedrockConnect

The open-source project BedrockConnect is a community-run DNS service. It redirects the featured servers in Minecraft to your own server list. In this list, you enter the address and port of your server. Please note the following first:

• This method is unofficial. It does not come from Mojang, Microsoft, Sony or Nintendo.
• It is a third-party service. It can go down or stop working after updates to Minecraft or the console.
• The DNS change applies to the whole console. All name resolution then runs through this service.
• Never enter account details on websites that promise a DNS guide.
• Public instances do not share server lists. After switching instances, you have to add your server again.

DNS Addresses per Console

As of: checked on 14.10.2026 in the official BedrockConnect guide. Please compare the addresses with this source before entering them, as they may change.

Setting Up PlayStation 5

1. On the home screen, open Settings and then Network.
2. Select Settings and then Set Up Internet Connection.
3. Select your connection and open the advanced settings.
4. Set the DNS settings to Manual.
5. Enter the primary and secondary DNS from the table and confirm with OK.
6. Wait until the connection test is complete.

Setting Up PlayStation 4

1. Open Settings and then Network.
2. Select Set Up Internet Connection and your connection type.
3. Select Custom and then your connection.
4. For IP Address, select Automatic, and for DHCP Host Name, select Do Not Specify.
5. For the DNS settings, select Manual, enter the addresses from the table and select Next.
6. For MTU, select Automatic, and for Proxy Server, select Do Not Use.
7. Start the connection test.

Setting Up Xbox and Nintendo Switch

1. Open the internet or network settings of your console.
2. Set the DNS setting to Manual.
3. Enter the primary and secondary DNS from the table and save.
4. Run the console's connection test.

The exact menu names differ depending on the console and system version. The project page links video guides for Xbox and Nintendo Switch.

Adding your server to the server list

1. Start Minecraft, open Play and go to the Servers tab.
2. Select one of the featured servers: Mineville, Lifeboat, Enchanted, Galaxite or The Hive.
3. Instead of this server, the BedrockConnect server list opens.
4. Add your server there with the address and port from your server dashboard (Connection section) and join.

For a Java server with crossplay, enter the Bedrock address and the Bedrock port (Geyser), not the Java port.

Reverting the Changes

Set your console's DNS settings back to Automatic and run the console's connection test. After that, the console uses its normal DNS service again.

If It Doesn't Work

• Run the console's connection test and check that the addresses are exactly right.
• On the PlayStation, enter 45.55.68.52 as the primary DNS, as the official guide recommends.
• Check the address and port beforehand on your phone or PC so you know the server is reachable.
• Add your server again after switching instances.
• You can find more help on the BedrockConnect troubleshooting page.

For a mixed group, start supported Java server software and install the appropriate Geyser distribution. Paper is a common plugin-based foundation; other supported distributions have their own installation paths. Copying a generic plugin file into an unrelated modloader is not a valid universal installation method.

Follow the Geyser setup documentation for the selected software. The Java world remains the main world. Bedrock players connect through a translated protocol, not to a separate native Bedrock copy of the same map.

Floodgate offers suitable Bedrock-account authentication without requiring an additional Java licence from those players. Installation and authentication configuration must agree. Follow the Floodgate setup guide; do not replace that method by disabling general Java authentication as a quick fix.

Check both paths independently: a Java client reaches the Java listener, Geyser starts successfully, a Bedrock client reaches the assigned Bedrock listener and the access list recognises its actual identity. Then test relevant inventories and extension menus on both editions. Java modpacks that require custom client blocks or features are not made universally playable on an unchanged Bedrock client by this translation.

The host identifies the reachable machine or endpoint. The port identifies the intended listener. For hosted software, use the actual allocation from the dashboard. Familiar defaults from guides are explanations, not replacement values for your server.

Typical Bedrock and Geyser listeners use UDP. A checker that tests only TCP cannot confirm that path. Current native Bedrock software can also have relevant transport configuration. Use the exact software's current documentation and a real client rather than inferring compatibility from a green web check.

An externally hosted world needs no incoming home-router forwarding. Restrictions on outgoing game traffic belong to the network the player uses. Compare another permitted network to distinguish that situation, and check the network's operating conditions when needed. Keep the working host and port as the reference while testing.

Back up the source world before exporting or transferring it. Stop the destination server before replacing files. Confirm the native Bedrock software supports the world's version and required packs. Export options depend on the source device; consoles do not necessarily expose the same ordinary file access as a computer.

Inspect the archive structure. It should contain the actual world, not merely a parent directory around it. Native Bedrock worlds use their relevant database structure. Java world files are not interchangeable, and changing an archive extension does not convert them.

After uploading, select the intended world through the server's supported setting and start deliberately. If a new landscape appears, check the active world name and path before deleting anything. The import may be present but inactive or nested at the wrong level.

Test spawn, buildings, player inventory, relevant dimensions and add-ons. Some content needs additional packs or a specific supported combination. Save the successfully imported state before continuing normal play. On a Java and Geyser setup, import a Java world using the Java software's rules; edition conversion is a separate task with possible differences and data loss.

Use the access list appropriate for the running native Bedrock software. Its commands and settings can differ from Java's whitelist. Test the list with an allowed account and keep the intended authentication enabled. Knowing the address should not be treated as permission to enter a private group world.

With Floodgate, confirm the actual Bedrock identity reported by the supported authentication path. A similar-looking Java name is not enough. Observe a controlled first join and use the documented management method. An incorrectly entered identity can exclude a legitimate friend even when the network is working.

Give administrator permissions only to people who need to manage the world. Agree on game mode, difficulty, PvP and how restores are handled. A normal participant does not require full server privileges. Remove temporary setup permissions once the group is ready.

Keep hosting login, in-game administration and Microsoft account access separate. A friend can help with game rules without receiving credentials that control installation and files. Conversely, access to file management does not establish the correct identity for joining through a whitelist or allowlist.

Start with edition, exact version, completed server startup and copied endpoint. Then investigate account and authentication details. Note the time of the failed attempt and inspect the corresponding console line. A connection that never arrives and a login that is explicitly rejected require different next steps.

Ask for the precise error, not only a statement that the server is broken. Avoid switching general authentication off or replacing the Bedrock port with a Java port at random. Preserve the working reference client and reproduce the same test after each supported change.

Platform clients may update at different times. After a game release, check that the server and, for crossplay, Geyser support the clients your group has. A mixed-platform update should be coordinated so one player does not unexpectedly lose access during a session.

Save the world, necessary packs and configuration before updating. Test one login, then the remaining device types. Inspect meaningful parts of the world and reconnect, rather than stopping at the title screen. Tell everyone which version and client path the group now uses.

An inactive free server may sleep, which stops normal world ticks. Stored files do not imply continuously operating farms or mechanisms. If continuous activity is essential, check an operating option suited to that requirement. The RAM amount alone does not answer the question.

Rollback needs the pre-update backup and its compatible software. Do not treat an already updated world as a safe downgrade candidate. Retain the original working state until device checks pass. Include player data and relevant dimensions so restoring the landscape does not leave the group with missing progress.

The setup is complete when every intended device type has actually joined, private access behaves correctly and the expected world returns after a restart. A successful phone login alone confirms neither the console route nor the Java listener of a mixed setup.

• Minecraft multiplayer basics explains joining from supported game clients.
• Microsoft's native Bedrock server introduction explains the dedicated-server foundation.
• Geyser installation documents supported Java and Bedrock connections.
• Floodgate authentication covers the corresponding Bedrock-account setup.
• Console connection methods explains device restrictions and community approaches.

For an all-Bedrock group with a tested external connection path, configure the selected native Bedrock server. For a mixed group, choose the Java foundation deliberately and verify both listeners. In either case, keep the tested address, world backup and start procedure available for the next session.