To move a world, copy the entire Minecraft Java Edition save to a stopped server running the same game version, then set its name in server.properties. Do not copy only the Overworld folder: the save may also contain the Nether, End, player data, and world settings.
This guide covers vanilla worlds or worlds compatible with the chosen server software. It does not cover Bedrock Edition: Bedrock save formats and its dedicated server use a different procedure. If the world uses Fabric, Forge, or NeoForge, the server needs the same compatible loader and mod set. Paper does not load those mods, and blocks or items added by them may not survive a move to Paper.
Prepare a copy of the save#
Save and close the single-player world normally. Close the game and launcher so the files stop changing. Make a separate copy of the entire world folder and keep it outside the target server directory. Do not use the original save as your working migration copy.
In the standard launcher, saves are under %AppData%\.minecraft\saves on Windows, ~/Library/Application Support/minecraft/saves on macOS, and usually ~/.minecraft/saves on Linux. Third-party launchers may use another path: use their instance-folder action and check which folder contains level.dat and the dimension folders.
If you are moving the server to your own VPS, Nexardo can help you manage your infrastructure. You should still check the migration in a private test launch first.
Choose compatible server software#
Record the Minecraft version used to open the source world. Download official server software for the same Java Edition and game version from Minecraft's official download page. If that release requires a specific Java version, check the server's current documentation before starting it.
Do not open an old save in a newer game version before you have a backup: Minecraft may update data so that an older version can no longer load it. If you need a newer release, first upgrade a separate copy in the target client version, check that it opens, and use a server on that same version. Minecraft 26.1 and later require Java 25; check the selected release notes for other versions. For a modded world, record the exact loader, mod, and datapack versions; a single-player modpack does not automatically become a dedicated server. Mods that change generation, blocks, dimensions, or require client-side components need particular care.
The first server launch prepares the EULA and configuration files. Read the Minecraft EULA and set eula=true only if you accept it. Then fully stop the server process.
Copy the world into the server directory#
Rename the copy of the world folder to a short unique name such as friends-world, then move it to the server root—the directory containing server.properties. In a hosting panel, first confirm the actual server root and upload the complete save folder. Check that level.dat is directly inside friends-world, not nested inside another folder such as friends-world/My World/level.dat.
With the server stopped, open server.properties and set the same folder name:
level-name=friends-world
Check that there is no other friends-world directory on the server containing an empty or test world. If one exists, do not merge folders: keep it under another name and ensure the intended copy is in place. Do not delete the older save until the migration is verified.
Current Paper versions handle Vanilla migration automatically. However, Paper's world layout changed: from 26.1 onward, Vanilla and Paper dimensions use the new layout within the level folder; older Paper versions could store the Nether and End in separate world_nether and world_the_end directories. In Java 26.1 and later, the Nether and End are under dimensions/minecraft/the_nether and dimensions/minecraft/the_end, the Overworld is under dimensions/minecraft/overworld, and player data lives under players. This matters when moving between server types and versions. Do not copy individual dimension folders using an old guide until you check the version, the Minecraft 26.1 release notes, and the official Paper migration guide. Paper separately warns that direct migration from Spigot/CraftBukkit is unsupported.
level-name match reduce the risk of opening the wrong world.Verify the world before opening access#
Keep the server available only to you, start it, and read the first log messages carefully. If it generated a new landscape, stop: check the server root, level.dat nesting, spelling of level-name, file permissions, and actual working directory. Do not continue exploring the new world or overwrite your old copy with it.
Connect locally with a Java client that matches the server. Check familiar builds and coordinates in the Overworld, then visit the Nether and End. Confirm that the expected datapacks, rules, and settings load. Inventory, spawn position, and player progress can depend on UUID and the saved account state; verify them separately instead of assuming that moving the world also moved each player profile. If items or data are important, keep them in the source backup and prepare a reversible recovery path in advance.
Run stop, wait for the process to exit, start the server again, and confirm that changes persisted. Only after this check should you configure public access and give other players the address. Leave the original and backup untouched until you have confirmed the expected dimensions, player data, and mods.
The commands and paths in this article were checked against documentation, but the migration, server start, and player join were not run here.
