Vanilla Bedrock ARM64 Server Hosting

What does ARM64 mean for a Bedrock server?

An ARM64 Bedrock server is a Minecraft: Bedrock Edition server running on a machine with an ARM processor. The catch is that Mojang's official Bedrock Dedicated Server is only published for the x86-64 architecture, as Windows and Linux builds. There is no native ARM64 build, and although players have requested one on the Minecraft feedback site, Mojang has not announced it.

So on a Raspberry Pi 4 or 5, an ARM cloud instance or similar hardware, BDS runs through a translation layer such as Box64 or FEX-Emu, which converts x86-64 instructions into ARM instructions on the fly. It works, but at a price: CPU load goes up, the number of players the same hardware can carry goes down, and warnings that the server cannot keep up become more frequent while new chunks generate. Community ARM64 setups also document quirks such as chat not appearing in the console and in-game op grants not persisting. In other words, ARM64 is usually a compromise made to use hardware you already have, not a first choice.

What does the ARM64 option mean at TheCrewHost?

The honest answer: our game servers run on AMD Ryzen 9 9950X processors, which are x86-64, the same architecture BDS is compiled for. You do not need a translation layer to run a Bedrock server here, and the standard Vanilla Bedrock setup uses the hardware at full speed.

That is why the plans on this page make the most sense for people whose ARM box has hit its limits and who want to move their server somewhere with real headroom. RAM, storage and vCore numbers are identical to our Vanilla Bedrock plans. If you want the ARM64 build for a specific reason, for example to reproduce a bug you saw on your own ARM setup, or you are simply unsure which build will be installed, ask our support team before ordering. We will confirm which setup fits so you do not carry emulation overhead you do not need.

How do you move a world from a Raspberry Pi or ARM server?

Bedrock worlds are stored as LevelDB-based folders, and that format does not depend on CPU architecture. The same world folder opens on a phone, on Windows and on a server, and it moves from your ARM machine to an x86-64 server without conversion.

Start by stopping the server on the ARM device cleanly so the last changes are written to disk. Then download the world folder from worlds, along with server.properties, allowlist.json and permissions.json, plus behavior_packs and resource_packs if you use add-ons. Upload the same structure to your new server over SFTP and make sure level-name matches the world folder's name.

The one thing to watch is the version. The BDS on your Pi may be several updates behind, and players on current clients need the new server on the current BDS release. A world upgrades cleanly to a newer version, but there is no guarantee it can go back, so keep a copy of the original folder before you migrate.

How many players does each plan handle without emulation?

Under Box64 a meaningful share of CPU time goes into translating instructions. On x86-64 all of it goes to the game, so a world that struggled with five players on a Pi has far more breathing room here. BDS is a native program, so there are no JVM flags to tune either.

For a small family or friends world, Bronze 4GB is enough. If you are bringing a large, heavily explored map from your Pi or running add-ons, Silver 6GB or Gold 8GB is a more comfortable starting point. For busy communities the real limit is the CPU: Bronze through Diamond include 4 vCores, Emerald 6 and Xtreme 12. If you lowered tick-distance and view-distance in server.properties to keep the Pi alive, raise them gradually here and watch the console for warnings after each change.

Reconnecting players after the move

After the migration, players only need to swap the old address for the new one. On phones, tablets and Windows they edit the saved entry in the Servers tab and enter the IP address and port shown in your panel. You can now switch off the port forwarding and dynamic DNS you set up for the Pi, which closes your home network to the outside and stops your home IP from being visible to players.

For Xbox, PlayStation and Switch players nothing changes about the rules: consoles still do not let anyone type in a server address. Whatever community method they used with your Pi, such as a DNS redirect or a helper app that broadcasts the server as a LAN game, works the same way with the new server once the target IP and port are updated.