How to Import a Singleplayer World to Your Server
Complete guide to uploading a singleplayer Minecraft world to your server, covering file structure, version compatibility, Multiverse import, and common issues.
You have spent weeks building a survival world in singleplayer, a sprawling base, automated farms, maybe an entire village redesign. Now you want friends to join. Moving that world to a dedicated server is straightforward, but there are a handful of details that trip people up: file naming, version mismatches, playerdata conflicts, and chunk rendering glitches. This guide covers the full process from locating your save to having players connect to it.
Finding your singleplayer saves folder
Minecraft stores singleplayer worlds in the saves directory inside your game folder. The exact path depends on your operating system:
| OS | Path |
|---|---|
| Windows | %APPDATA%\.minecraft\saves\ |
| macOS | ~/Library/Application Support/minecraft/saves/ |
| Linux | ~/.minecraft/saves/ |
Each save is a folder named after the world. Inside you will find level.dat, region/, playerdata/, DIM-1/ (Nether), and DIM1/ (End). The entire folder is what you need to transfer.
Preparing the world for upload
Before transferring, do a few things in singleplayer:
- Match the version, open the world in the same Minecraft version your server runs. If the server is on 1.21.4 and your world was last played on 1.20.4, open it in 1.21.4 singleplayer first. Minecraft will upgrade the chunks and
level.datformat. Going backward (downgrading a world) is not supported and will corrupt chunks. - Set your spawn, use
/setworldspawnin singleplayer to place the world spawn where you want new players to appear. The server uses this location as its default spawn point. - Remove local mods, if you used client-side mods that alter world generation (like Terralith or Biomes O' Plenty), the server also needs those mods or the chunks generated by them may render incorrectly.
Uploading to the server
Using the file manager (Pterodactyl / panel)
- Compress the world folder into a
.zipor.tar.gzarchive on your local machine. - Open the server file manager in your hosting panel.
- Upload the archive to the server root directory (where
server.jarlives). - Extract the archive using the panel's extract tool.
- You should now have a folder like
/home/container/MyWorld/sitting next toserver.jar.
Using SFTP
For large worlds (several gigabytes), SFTP is faster and more reliable than the web-based file manager. Connect with an SFTP client like FileZilla or WinSCP using the credentials from your hosting panel, then drag the world folder directly into the server root.
Configuring server.properties
The server reads the level-name property to decide which folder to load as the main world. If your uploaded folder is called MyWorld, edit server.properties:
level-name=MyWorld
The value must exactly match the folder name, including capitalization on Linux servers. After saving, restart the server. It loads MyWorld/ as the Overworld, and its DIM-1 and DIM1 subfolders become the Nether and End.
If you want to keep the default world name, rename your uploaded folder from MyWorld to world instead. Just make sure you move or delete the old world/ folder first so there is no conflict.
Handling playerdata
Your singleplayer world has a playerdata/ folder with a .dat file for your player UUID. This file contains your inventory, position, health, XP, and advancements. When you join the server, the server looks up your UUID and loads that file.
There are two potential issues:
- UUID mismatch, singleplayer uses an offline-mode UUID derived from your username. If the server runs in online-mode (which it should), your UUID is different. The server creates a new playerdata file, and your singleplayer inventory does not carry over. This is usually fine, you can reclaim items from chests.
- OP status, your singleplayer operator status does not carry over. Add yourself as OP on the server with
/op YourNamefrom the console.
If you specifically need to preserve your inventory, rename your offline-mode .dat file to your online-mode UUID. Look up your online UUID at mcuuid.net or a similar tool.
Importing as an additional world with Multiverse
If the server already has a main world and you want to add your singleplayer world as a secondary world (for creative building, an event map, etc.), use Multiverse-Core:
/mv import MyWorld normal
This registers MyWorld as a normal-type world without regenerating it. Players can teleport in with /mv tp MyWorld. You can set per-world game modes, weather, and difficulty through Multiverse config.
To also import the Nether and End from that world, extract DIM-1 and DIM1 into separate folders (e.g., MyWorld_nether and MyWorld_the_end) and import them as NETHER and END types:
/mv import MyWorld_nether nether
/mv import MyWorld_the_end end
Common issues and fixes
Chunks not loading or invisible
This usually means a version mismatch. The world was saved in a newer version than the server runs. Minecraft does not downgrade chunk data. Solution: upgrade your server jar to match the world version, or open the world in the correct singleplayer version first.
Missing structures after upload
Structures like villages, ocean monuments, and trial chambers are stored in a data/ folder inside the world directory. If you missed copying this folder, structure bounding boxes disappear, which breaks mob spawning in those areas. Make sure the entire world folder is copied, not just the region/ files.
Mods and datapacks not working
Singleplayer worlds using datapacks store them in world/datapacks/. These transfer automatically if you copy the whole folder. However, mods like Terralith or custom worldgen datapacks require the same datapack or mod on the server. Without it, newly generated chunks use vanilla terrain, creating harsh biome borders at chunk boundaries.
Spawn protection blocking players
Servers have a spawn-protection setting in server.properties (default 16 blocks). Non-OP players cannot break or place blocks within that radius of the world spawn. If your base is near spawn, players may complain they cannot build. Set spawn-protection=0 or use WorldGuard for more granular control.
World too large to upload
If the world exceeds your panel's upload limit, use SFTP. If it exceeds available disk space, consider trimming chunks you do not need. Tools like MCA Selector let you delete specific region files based on criteria like "inhabited time less than 30 seconds," removing chunks that were briefly loaded but never built in.
For a smooth start after import, run through the initial server setup checklist to make sure permissions, plugins, and spawn are configured correctly for multiplayer.
Need reliable hosting for your server? Astroworld Hosting offers NVMe SSD, Pterodactyl panel, and DDoS protection. See features , plans from €6.39/mo.