LiveChat 
Support 
How to Update a Minecraft Bedrock Server to a New Version (Safely)
When Mojang ships a new Minecraft update, your players’ clients update automatically through the Microsoft Store, Google Play, or their console. Your Bedrock Dedicated Server (BDS) does not. The result is predictable and frustrating: players open the game, try to join, and get a connection error. A version mismatch between an auto-updated client and an out-of-date server is the single most common reason players cannot join after a Minecraft update.
Updating BDS is not difficult, but doing it carelessly is the fastest way to corrupt a world or wipe a carefully tuned configuration. This guide walks through the safe, repeatable process for updating an existing Bedrock server to a new version — with backup-first discipline and clean file migration at the center.
Key Takeaways
• Clients auto-update; servers do not. A version mismatch is the #1 cause of “can’t connect” errors after a Minecraft update.
• Always back up first: your `worlds` folder, `server.properties`, `allowlist.json`, and `permissions.json` are irreplaceable.
• Extract the new BDS build into a clean folder — never on top of the old one.
• Copy your saved world and config into the new server, not the other way around. Do not overwrite new binaries with old files.
• Keep the previous backup until the new version is verified and stable.
If you are standing up a server for the first time rather than upgrading one, start with our companion guide instead: . This article assumes you already have a running server and need to move it to a newer version.
Why do you need to update a Bedrock server at all?
The Bedrock edition enforces strict version parity between client and server. Unlike some Java setups where a small version gap may still negotiate a connection, Bedrock clients refuse to join a server running a different protocol version. Because mobile and console clients update on their own schedule — often the moment an update is released — your server can fall behind without you touching anything.
Common symptoms of a behind-the-curve server include:
- Players see “Unable to connect to world” or a generic connection-failed message.
- The server log shows a protocol or version mismatch when a client attempts to join.
- Some players (who delayed their client update) can still join, while freshly updated players cannot — a tell-tale sign of a mismatch.
Beyond reconnecting players, updates also deliver security fixes, performance improvements, and new gameplay features. Running an outdated build indefinitely is both a compatibility and a maintenance risk.
The single most important rule when updating BDS: extract the new version into a *fresh, clean folder* and copy *your* world and config files *into* it. Never extract the new build on top of your existing server directory. The BDS archive does not cleanly replace every file — overwriting in place can leave stale or conflicting files from the old version (changed resource packs, deprecated definitions, leftover binaries) that produce subtle, hard-to-diagnose errors. A clean extraction plus a deliberate copy of only *your* data is the only way to guarantee the new build runs exactly as Mojang shipped it.
What should you back up before updating?
Treat the backup as non-negotiable. Before you change anything, stop the server and copy these out to a safe location:
| Item | Path | Why it matters |
|---|---|---|
| Worlds | `worlds/` | Your entire map, builds, player data, and inventories. The most irreplaceable asset. |
| Server config | `server.properties` | Server name, gamemode, difficulty, ports, view distance, and all tuning. |
| Allowlist | `allowlist.json` | Your whitelist of permitted players (formerly `whitelist.json`). |
| Permissions | `permissions.json` | Operator and member permission assignments. |
| Packs (if used) | `resource_packs/`, `behavior_packs/` | Any add-ons or custom content you installed. |
Everything else in the BDS folder — the `bedrock_server` binary, default packs, and definition files — comes from Mojang and will be replaced by the new build. You only need to preserve your data and configuration.
How do you update a Bedrock server step by step?
Follow this sequence exactly. The order matters: stop, back up, download, extract clean, migrate, verify.
- Stop the server gracefully. Never copy a world while the server is writing to it — you risk corruption. Stop it cleanly so all data flushes to disk.
- Back up your data. Copy the world and config files (table above) to a dated backup folder.
- Download the new BDS build from the official Minecraft server download page.
- Extract the new build into a brand-new, empty folder. Do not extract over the old server.
- Copy your saved world and config into the new folder. Migrate *your* files into the new build — not the reverse.
- Start the new server and verify that the world loads and players can join.
- Keep the old backup until you are confident the new version is stable.
Step 1 — Stop the server and back up
If you run the server interactively, type `stop` in the console. If it runs as a service, stop the service so it shuts down cleanly. On a Linux VPS the workflow over SSH typically looks like this:
“`bash
sudo systemctl stop bedrock
cd /opt/minecraft
mkdir -p backups/$(date +%F) cp -r bedrock-server/worlds backups/$(date +%F)/ cp bedrock-server/server.properties backups/$(date +%F)/ cp bedrock-server/allowlist.json backups/$(date +%F)/ cp bedrock-server/permissions.json backups/$(date +%F)/ “`
On Windows, stop the server window or service, then copy the same `worlds` folder and `.json`/`.properties` files into a dated backup directory using File Explorer or PowerShell.
Step 2 — Download and extract the new build into a clean folder
Grab the latest Bedrock Dedicated Server archive for your platform (Linux or Windows) from Mojang’s official download page. Then extract it into a *new* directory — never on top of the existing one.
“`bash
cd /opt/minecraft wget -O bds-new.zip “https://www.minecraft.net/en-us/download/server/bedrock/
The version number in the filename changes with every release, so always copy the current link from the official page rather than reusing an old URL.
Step 3 — Migrate your world and config into the new server
Now copy your preserved data into the freshly extracted build. This is the direction that keeps you safe: your data moves into Mojang’s new binaries, not the other way around.
“`bash
cp -r backups/$(date +%F)/worlds bedrock-server-new/ cp backups/$(date +%F)/server.properties bedrock-server-new/ cp backups/$(date +%F)/allowlist.json bedrock-server-new/ cp backups/$(date +%F)/permissions.json bedrock-server-new/ “`
If you use add-on resource or behavior packs, copy those folders in as well. Do not copy the old `bedrock_server` binary or default packs — those must come from the new build.
Step 4 — Start the new server and verify
Point your service at the new folder (or rename folders so the new build takes the active path), then start it.
“`bash
mv bedrock-server bedrock-server-old mv bedrock-server-new bedrock-server sudo systemctl start bedrock
journalctl -u bedrock -f “`
Watch for the “Server started” line and confirm the log reports the new version. Then join from an updated client to verify the world loads correctly, your settings carried over, and your allowlist still works. Keep `bedrock-server-old` and the dated backup until you are confident — if anything is wrong, you can revert in seconds.
What can go wrong, and how do you avoid it?
- Overwriting in place. Extracting the new build on top of the old folder is the classic mistake. It leaves stale files behind. Always extract clean.
- Copying old binaries forward. Never let an old `bedrock_server` executable or default pack survive into the new install — migrate only your data.
- Skipping the backup. A world copied while the server is still running can corrupt. Stop first, then back up.
- Deleting the old version too soon. Keep the previous build and backup until the new one is verified stable across a real play session.
Run and update your Bedrock server on a DarazHost VPS or dedicated server
The stop-backup-extract-migrate-verify workflow is dramatically easier when you have full root access and a real shell. On a or , you control the entire machine: you can script the backup, pull the new BDS build over SSH, extract it cleanly, and swap folders in seconds — exactly the process described above.
DarazHost plans are built for game-server workloads that demand consistent performance:
- Root access and SSH for the full stop, back up, download, and migrate update workflow.
- The CPU, RAM, and resources to run a Bedrock server smoothly and handle updates without contention.
- Fast NVMe SSD storage for quick world saves, backups, and extractions.
- Reliable uptime so your players stay connected.
- 24/7 technical support when you need a hand with a migration or a stubborn service.
Whether you run one world for friends or several busy servers, a VPS or dedicated machine gives you the control to keep Bedrock current the moment Mojang ships an update.
Frequently asked questions
Why can’t players join my server after a Minecraft update?
The most common cause is a version mismatch. Players’ clients auto-update, but your dedicated server does not — so the client and server speak different protocol versions and refuse to connect. Updating the server to the matching version resolves it. Check your server log for a version or protocol error to confirm.
Will updating my Bedrock server delete my world?
Not if you follow the safe process. Your world lives in the `worlds` folder, which you back up before updating and then copy into the new build. The danger is procedural, not inherent — corruption happens when people skip the backup or copy a world while the server is still running. Stop, back up, then migrate.
Can I just unzip the new version over my existing server folder?
No — this is the most common and most damaging mistake. Extracting on top of the old folder can leave stale, conflicting files behind and produce errors that are hard to trace. Always extract the new build into a clean folder and copy *your* world and config into it.
Do I need to update the server every time Minecraft updates?
For your server to stay reachable by current clients, yes — Bedrock enforces version parity, so a behind server will reject updated players. You can briefly delay if no one has updated their client, but in practice clients update quickly, so plan to update the server promptly after each release.
How long does a Bedrock server update take?
The mechanical steps — stop, back up, download, extract, migrate, verify — usually take only a few minutes on a VPS with SSD storage and a fast connection. Larger worlds take longer to back up and copy. Scripting the workflow over SSH reduces it to a short, repeatable routine.
