How to Create a Minecraft Bedrock (PE) Server

Setting up your own Minecraft Bedrock server sounds like one of those projects that begins with “This will only take five minutes” and ends three hours later with you staring at a router menu that looks like it was designed in 2009 by a very tired wizard. The good news? It is absolutely doable, and once it works, it feels glorious.

If you want a private place for friends and family to build, survive, experiment, or accidentally punch each other into lava, a Minecraft Bedrock (PE) server gives you control that random public servers simply cannot. You decide the world, the rules, the player list, the difficulty, and whether your cousin gets operator powers or remains a humble non-destructive potato.

This guide walks you through how to create a Minecraft Bedrock server on Windows or Ubuntu, how to open the right ports, how to configure key settings, and how to make the whole thing more stable and secure. It also covers the real-life experience of running one, because the technical setup is only half the story. The other half is discovering which friend always “accidentally” leaves creeper holes next to the storage room.

What Is a Minecraft Bedrock (PE) Server?

A Minecraft Bedrock server runs the Bedrock Dedicated Server software, which is the official server software for Minecraft Bedrock Edition. That includes players on Windows, mobile devices, Xbox, and other Bedrock-compatible platforms. In other words, this is the version you want if your group plays cross-platform and not everyone is living the Java life.

People still say “PE server” because Bedrock grew out of Pocket Edition, but today the broader term is Minecraft Bedrock server. It is better for cross-device play, easier for console and mobile players to join, and a practical choice for families, friend groups, and small communities.

Why Create Your Own Bedrock Server?

Creating your own Minecraft Bedrock dedicated server gives you three big perks: control, privacy, and consistency. On a self-hosted server, the world does not disappear when one specific player logs off. The world stays online as long as the server stays online. That means your friends can log in without waiting for the host to launch the game.

You also get more control over server settings. Want a clean survival world with no cheats and a small invite-only player list? Easy. Want a creative test world with operators, resource packs, and total chaos? Also easy. The point is that you are no longer borrowing someone else’s sandbox. You own the whole litter box now.

What You Need Before You Start

Before you build your Bedrock server, gather the basics:

• A Windows PC or Ubuntu machine that can stay online
• A stable broadband connection
• Administrative access to your computer and your router
• A copy of Minecraft Bedrock Edition for testing
• Basic patience, plus a healthy respect for firewalls

For small groups, you do not need a monster machine. But if you plan to host more players, large worlds, or lots of activity, better hardware and a solid upload speed matter. Server location matters too. If your players are spread out, the closer the host is to most of them, the better the latency tends to be.

Step 1: Decide How You Want to Host It

You have three practical options for a Bedrock multiplayer setup:

1. Host it at home

This is the classic DIY route. It gives you the most control and can cost very little if you already own suitable hardware. The tradeoff is that you must deal with networking, firewall rules, and port forwarding yourself.

2. Rent a VPS or game server host

This is easier for many people because the server can stay online 24/7 without tying up your home PC. It is also helpful if your home internet is not great or your ISP makes port forwarding miserable.

3. Use Minecraft Realms

Realms is the easiest official option, but it is less flexible than running your own Bedrock Dedicated Server. If you want simplicity, Realms is great. If you want deeper configuration and more control, a dedicated Bedrock server wins.

This guide focuses on the dedicated-server route, because that is what people usually mean when they search for how to create a Minecraft Bedrock server.

Step 2: Download and Install the Bedrock Dedicated Server

Download the official Bedrock Dedicated Server package and extract it into a clean folder. Keep the install directory simple and easy to remember. Something like C:\MinecraftServer on Windows or ~/MinecraftServer on Ubuntu works nicely.

On Windows

1. Open Command Prompt or PowerShell.
2. Change to your server folder.
3. Run bedrock_server.exe or bedrock_server, depending on how the executable appears on your system.

On Ubuntu

1. Open Terminal.
2. Change to your server folder.
3. Run LD_LIBRARY_PATH=. ./bedrock_server.

The first launch creates important folders such as worlds, behavior_packs, and resource_packs. Let it run once before you start moving worlds around or editing advanced settings. That first boot is like the server stretching its legs and figuring out where it left its socks.

Step 3: Edit the Server Settings

The heart of your Minecraft Bedrock dedicated server is the server.properties file. This is where you control your server name, game mode, difficulty, player limit, ports, world name, and more.

Here is a clean example for a small private survival server:

Those settings are beginner-friendly and sensible for a private server. A few important notes:

• online-mode=true is the right move for internet-facing servers.
• allow-list=true helps keep random players out.
• server-port should usually stay at 19132 for Bedrock over IPv4.
• server-portv6 defaults to 19133 for IPv6.
• max-players should be realistic for your hardware and connection.
• view-distance can be lowered if performance starts to wobble.

One of the most useful settings is level-name. The server uses that value to decide which folder in worlds/ is active. If you already have an existing Bedrock world, copy its world folder into worlds and make sure level-name matches the folder name exactly, including letter case.

Step 4: Configure the Allowlist and Permissions

If you want a private Minecraft PE server, turn on the allowlist. This restricts the server to approved players only. On Bedrock, that usually means players identified by their Xbox Live Gamertags.

The simplest way to manage this is from the server console:

If a Gamertag includes spaces, keep the quotes. Without them, Minecraft treats the name like a broken sentence and gets confused.

You can also grant operator powers from the console:

Operators can manage the server in-game, so choose wisely. Giving op status to the funniest person in the group is not always the same as giving it to the most responsible person in the group. History has many lessons on this.

Step 5: Open the Firewall

Your server may be running perfectly and still be unreachable if the firewall blocks incoming traffic. This is one of the most common reasons a new Minecraft Bedrock server appears to “work” while nobody can actually join.

On Windows

When you first run the server, Windows Defender may ask whether to allow it through private or public networks. If you plan to host for people on your home network only, private access may be enough. If remote players will join from the internet, you typically need public access too.

On Ubuntu

If you use UFW, allow the default Bedrock ports:

Bedrock uses UDP, not the Java default TCP pattern many players remember. That tiny detail causes a surprisingly large number of headaches.

Step 6: Set Up Port Forwarding on Your Router

If players outside your home network need access, you must configure port forwarding. This tells your router to send incoming Bedrock traffic to the computer running the server.

1. Find your server machine’s local IP address.
2. Give that machine a static IP or DHCP reservation so the address does not change later.
3. Log in to your router’s admin page.
4. Create a port forwarding rule for UDP 19132 to your server’s local IP.
5. If you use IPv6, also consider 19133.
6. Save the rule and restart the router if needed.

Many tutorials skip the static IP step, and that is a mistake. If your server’s local address changes, your forwarding rule points to the wrong machine and everyone suddenly thinks your server died. It did not die. Your router just lost the plot.

Step 7: Connect to the Server

Once the server is running, the firewall is open, and the router is forwarding traffic, it is time to join.

Local testing

If you are joining from the same PC on Windows, you may need loopback configuration. If you are joining from another device on your LAN, use the server machine’s local IP address.

Remote connections

Friends outside your network will use your public IP address and, if needed, the port. A typical entry looks like this:

If players see Outdated Server or Outdated Client, the game and the server are not on matching protocol versions. Make sure both sides are updated to compatible versions.

Step 8: Improve Performance and Stability

Once your Bedrock server is online, the next job is keeping it smooth. A server that technically works but lags every time two people run in different directions is less “multiplayer paradise” and more “digital swamp.”

Here are practical ways to improve stability:

• Lower view-distance if players report lag
• Keep tick-distance modest for small servers
• Use a wired connection if possible
• Close unnecessary apps on the host PC
• Restart the server after major changes
• Back up your worlds folder regularly

If you want to use an existing world, copy it into the worlds directory, rename the folder to something clean, and update level-name to match it exactly. That is the reliable way to move a personal Bedrock world into a dedicated server environment.

Step 9: Troubleshoot Common Bedrock Server Problems

Nobody can connect from outside your home

Check the router forwarding rule, confirm the server machine still has the same local IP, verify the firewall is open, and make sure you forwarded the Bedrock port using the correct protocol.

The server runs, but only LAN players can join

This usually means the server is fine but the router or ISP is blocking the outside path. Some internet providers make home hosting harder than it should be. In that case, a VPS or managed game host may be the simpler fix.

The world does not load correctly

Make sure the world folder is placed inside worlds/ and that level-name exactly matches the folder name. One tiny mismatch can stop the server from loading the intended world.

Players keep asking why they cannot join

If the allowlist is enabled, add them correctly. If their Gamertag contains spaces, use quotes. Also confirm they are using Bedrock Edition, not Java Edition, because Minecraft loves giving players two nearly identical-looking doors that open to totally different rooms.

Should You Self-Host or Pay for Hosting?

If you enjoy tinkering and only need a small private world, self-hosting is rewarding and cost-effective. It is perfect for families, friend groups, and hobbyists who do not mind a little hands-on setup.

If you want 24/7 uptime, less networking work, or easier scaling, paid Minecraft server hosting is often worth it. A host can save you from router drama, power outages, and that one night when your home PC decides now is the ideal time to install updates and reboot itself into another dimension.

Realms sits in the middle. It is easier than running your own Bedrock Dedicated Server, but less customizable. If convenience is your priority, it is a solid option. If control is your priority, build your own server.

Real-World Experiences of Creating a Minecraft Bedrock (PE) Server

Anyone who has ever created a Minecraft Bedrock server knows the process feels like a mini-adventure before the actual adventure begins. At first, it is exciting in a very pure, optimistic way. You imagine a neat little world where your friends log in, build charming houses, and somehow behave like civilized block-based citizens. Then reality arrives wearing a nametag that says Port Forwarding.

The first experience most people have is surprise at how simple and how weird the process is at the same time. Downloading the Bedrock Dedicated Server is easy. Extracting files is easy. Running the executable is easy. But then you hit the networking layer and suddenly you are looking up your default gateway, checking firewall rules, and wondering why a game about punching trees now requires a casual understanding of home infrastructure.

Once you get past that, the next feeling is usually satisfaction. There is something genuinely fun about seeing the server console start up, watching folders appear, and realizing that you are not just playing Minecraft anymore. You are hosting a little world. It feels surprisingly official, like you have been promoted from player to mayor, electrician, and emergency response team all at once.

Then come the social experiences, and those are often the best part. A private Bedrock server changes the rhythm of multiplayer. Instead of waiting for one person to be online and hosting the game, the world becomes a shared place that keeps existing. One friend might log in early to gather wood. Another might build a farm. Someone else will absolutely dig a suspicious hole directly through the middle of town and claim it was “for efficiency.” The world starts to tell stories even when you are not there to watch them happen.

There is also a special kind of joy in small improvements. The first time you fix a connection issue, add someone to the allowlist, move an existing world, or tune the view distance to reduce lag, you stop feeling like you are guessing. You start feeling capable. And that is a sneaky bonus of learning how to create a Minecraft Bedrock server: it teaches a little bit of systems thinking along the way.

Of course, it is not all enchanted apples and victory music. Sometimes the server works locally but not remotely. Sometimes a player is on the wrong version. Sometimes the public IP changes. Sometimes somebody forgets to mention they are trying to join from Java Edition and your carefully configured Bedrock server gets blamed like it personally chose chaos. But even those little setbacks become part of the experience. Once solved, they turn into stories you laugh about later.

For many people, that is the real reward. A Bedrock server is not just a technical project. It becomes a gathering place. It is where inside jokes are built into the map, where half-finished bridges become landmarks, and where a humble starter hut somehow survives long enough to become local history. The setup may begin as a how-to task, but the result feels much bigger. You are not just launching software. You are creating a tiny online world that people return to because it feels like home.

Final Thoughts

Learning how to create a Minecraft Bedrock (PE) server is one of those projects that pays off twice. First, you get a custom multiplayer world that is always yours. Second, you gain enough hands-on knowledge to troubleshoot, tune, and manage it with confidence.

Start simple. Use the official Bedrock Dedicated Server, keep the default ports unless you have a reason to change them, enable the allowlist, and test one step at a time. Once the foundation is solid, you can experiment with custom worlds, packs, permissions, and performance tweaks.

And when your server finally goes live and your friends join without a single error message, take a moment to enjoy it. You did not just build a server. You built the stage for your group’s next ridiculous, brilliant, blocky saga.