Dec 02, 2025
Alanas M.
8min Read
Whether you’re aiming to support crossplay, reach more players, or just prefer Bedrock’s performance on certain devices, moving a Minecraft server from Java to Bedrock is possible – but it takes a few steps.
In this guide, we’ll show you how to move your Minecraft server while keeping as much of your original setup as possible. If you decide that a complete Minecraft version switch doesn’t fit your needs, we’ll also cover how to configure cross-play on a Java edition server.
Minecraft Java Edition is written in Java and runs on the Java Virtual Machine (JVM), which is how Minecraft was initially programmed. It’s very customizable and with tons of plugins and mods available. However, it uses more RAM and CPU, especially with many players or heavy modding, and is limited to PC players.
Minecraft Bedrock Edition is written in C++ and was initially developed for systems that don’t support Java, starting with Minecraft Pocket Edition for mobile players.
C++ is a more efficient game coding language – it runs faster, uses fewer resources, and performs significantly better on lower-end hardware. Bedrock is widely available and supports cross-platform play on devices like Windows, Xbox, PlayStation, and mobile devices.
Outside of the technical details, some core game mechanics also differ. The two best examples of this are:
There are two main reasons why you might consider switching a server from Java edition to Bedrock edition:
The first thing to understand is that while both are Minecraft, Java and Bedrock are technically two separate games running on different engines. Since these are separate games, there are limitations as to what you can move over:
When moving a server from Java to Bedrock, you typically do not need to consider resources. For example, with 20 players, Java will run well with 4GB RAM and 2 vCPUs, while with Bedrock, you can run the same load with 2GB RAM and 1 vCPU. However, if you expect more players, ensure your server can handle the extra pressure.
Important!
Make sure to back up both your server and world files, as making this change can result in losing your data.
To switch your server from Java to Bedrock, you’ll need to stop your current Java Edition instance and create a fresh Bedrock Edition instance. Here’s a step-by-step on how to do this in Hostinger’s Game Panel:




Now, you need to wait for the server to stop. A stopped server will:

At this point, you should make a full server backup. Here’s how to do it:



Now that you have backed up your files, you can create a new Bedrock instance. At the left-hand menu, click Return to Instances and click Create Instance.

In the pop-up screen, select the Minecraft Bedrock application and click Create Instance.

Your Bedrock instance is now ready, and you can start the migration process.

Even with a fresh Bedrock edition server set up, you can still carry over a few configuration settings from your previous Java setup.
The server.properties file defines the basic configuration for your Minecraft server. The Java edition file differs quite a bit from the Bedrock edition. However, there are some shared or similar values. Here’s a side-by-side comparison of gameplay-impacting server.properties values that can be re-applied:
| Property name | Description |
| difficulty | Toggles difficulty level. |
| gamemode | Sets the default gamemode for players. |
| force-gamemode | Sets player gamemode to default on fresh login. |
| white-list (Java) / allow-list (Bedrock) | Restricts login access to players defined in a list. |
| view-distance | Defines the view distance for players, overriding client settings. |
| simulation-distance (Java) / tick-distance (Bedrock) | Defines the distance where random ticks are sent. |
| player-idle-timeout | Sets the amount of time in minutes before inactive players are kicked. |
| level-seed | Sets the seed for the fresh world generation. |
Additionally, the two Minecraft versions share quite a few game rules. While you cannot transfer them over directly, you can reapply some common game rules. Here are some examples:
| Game rule | Description |
| doDaylightCycle | Defines whether the in-game day-night cycle progresses. |
| doEntityDrops | Toggles if non-mob entities (such as Minecarts) drop items. |
| doMobLoot | Controls if mobs drop items and experience when killed. |
| doWeatherCycle | Toggles if the weather can change automatically. |
| doFireTick | Manages if fire spreads and extinguishes naturally. |
| mobGriefing | Defines if mobs can change blocks, such as creepers or endermen. |
| naturalRegeneration | Toggles natural health regeneration when hunger is full. |
| playersSleepingPercentage | Sets the percentage of sleeping players needed to skip the night. |
You can also switch over your game ports to match what Java had previously. Java edition uses port 25565 by default, while Bedrock edition uses 19132. However, these values are not static and can be changed. Here’s how to do it:




You can also modify this setting in server.properties.
Once you have switched over your server, the next step is moving your Java world to Bedrock. There are two main options for doing this.
A quick and practical way to do this is simply using the same seed. Java and Bedrock use the same world generation algorithms, so if you don’t care about keeping your builds, it’s the easy way of doing it.
However, you must convert your world to move over player-made objects, such as buildings and chests. Multiple tools can help you do this, such as:
While Minecraft world converters do not transfer player data, they transfer items in chests. To retain your progress, store your items in chests that will carry over before starting this process.
To start the conversion process, you need to download your Minecraft Java world:



Now, you must convert the world file to be compatible with Bedrock. In this tutorial, we will use Chunker.





Next, upload your converted world file to the Bedrock instance:








At this point, you can log in and explore your world to check if everything is working correctly and if there are any issues with your world.
Want to invite Bedrock players to join your Java Edition server without giving up Java’s powerful customization options? The good news is that you don’t need to choose between them.
With the help of the GeyserMC plugin, you can make your Java server accessible to Bedrock players without converting the world or losing Java-specific features.
It works by opening a separate port for your server that allows Bedrock players to access it. It acts as a proxy between a Bedrock player and your Java edition server. It takes their Bedrock packets and converts them to Java packets for the server to understand, and any packets sent back get converted back to a Bedrock packet.
To implement it, you need a Java edition server running on Paper or Spigot. Let’s see how you can do it!
Important!
Before doing this, we recommend backing up your server files to restore a vanilla Minecraft server configuration.





geyser connectiontest <servername> <port>
Important!
Bedrock players will be greeted with a message saying, “You need to log in with a Java Edition account to play on this server.” To remove this message, install the Floodgate plugin and adjust GeyserMC’s auth-type value to floodgate in config.yml.
With GeyserMC set up, your server can now support both Java and Bedrock players. If anything goes wrong, check the server console – GeyserMC logs are quite detailed and often point directly to the issue, especially for connections.

Switching your Minecraft server from Java to Bedrock isn’t as complicated as it might seem. While the two editions are built differently, there’s enough flexibility to rebuild your setup, move your world, or even enable cross-platform play to keep both sides connected.
If Bedrock edition is better for your server or players, you have everything you need to make that transition. Whether you’re starting fresh or carrying over your existing world, you have the tools – now it’s just a matter of making the switch.
Yes, but it’s not a direct toggle. Switching between these servers means stopping your Java edition server and spinning up Bedrock. However, you can transfer your world and a few of your server settings with some extra work.
Not quite. While you don’t need to remove your Java edition server, you must stop it and start a fresh Bedrock edition server. You can remove Java afterward, but nothing’s stopping you from keeping it, especially if you want to roll back quickly.
Not automatically. Java and Bedrock use different world formats, so you’ll need a conversion tool like Chunker to transfer your world. Some structures and entities may not carry over perfectly, so testing the converted world before going live is essential.