So you've been playing Minecraft Java Edition solo and you've put real hours into a world. A sprawling base, a megabuild that took weeks, or just a nice survival save you don't fancy starting over. Good news – you can lift that save straight onto a dedicated server. A few minutes of care with file paths and you're done.
This one's for Java Edition. Bedrock uses a completely different save format and won't run on a Java server, so if you're coming off console, mobile or the Bedrock app on Windows, your save won't drop in directly – you'd need a conversion tool like Amulet first, and that's a separate article.
Where Minecraft Saves Live on Your PC
On Windows the path is:
%APPDATA%\.minecraft\saves\<world-name>\
Fastest route: press Win+R, paste %APPDATA%\.minecraft\saves and hit Enter. Each world gets its own folder named exactly as it appears in your singleplayer menu (New World, My Survival World, whatever you called it).
On macOS you'll find it at ~/Library/Application Support/minecraft/saves/. On Linux it's ~/.minecraft/saves/. The contents are identical across operating systems – a save copied off a Mac will run fine on a Linux server.
Peek inside any world folder and you'll see:
level.dat– world metadata (seed, gamerules, time, spawn), gzipped NBTregion/– the actual chunks, Anvil-format.mcafilesplayerdata/– per-player inventories and positions, filenames are UUIDsdata/– scoreboards, command storage, raid data, world-gen settingsdatapacks/– any datapacks bound to the worldadvancements/andstats/– player progresssession.lock– a one-character file the game uses to detect concurrent access
Where the Nether and End land depends on your Minecraft version. Pre-26.1 worlds keep them in DIM-1/ (Nether) and DIM1/ (End) at the root of the world folder. From 26.1 onwards Mojang restructured the layout: the Overworld moved to dimensions/minecraft/overworld/, the Nether to dimensions/minecraft/the_nether/ and the End to dimensions/minecraft/the_end/. If you poke around and see a dimensions/ folder, you're on the newer format. Both work for upload – you just need to be aware which one you're holding.
You're uploading the whole folder, either way. Don't cherry-pick files. Missing region files mean missing chunks, and no level.dat means the server starts from scratch.
Before You Do Anything
Two things. Both important.
Stop the server first. Log into control.low.ms, find your Minecraft service, hit stop. Uploading files to a running server is asking for corrupted chunks – the server writes to region files constantly, and overwriting mid-write is exactly how .mca files end up half-written.
Back up the server's existing world. Even on a fresh server with nothing worth keeping, get into the habit. In the panel sidebar click Cloud Backup and spin one off. Takes seconds. Saves headaches.
Uploading via File Manager
The panel's File Manager is fine for smaller worlds:
- Log into control.low.ms and pick your Minecraft server
- Click File Manager in the sidebar
- You'll land in the server root –
server.properties,server.jar, yourplugins/ormods/folder and any existing world folders all sit here - Rename the existing world folder rather than deleting it –
worldtoworld_old, for example, so you've got a fallback - Upload your world folder from your local machine into the server root
Folder uploads work via drag-and-drop in modern browsers. Once a save grows past a few hundred megabytes though – and Minecraft worlds puff up fast once a couple of players start wandering, modded ones especially – SFTP tends to be quicker and more forgiving.
Uploading via SFTP
SFTP runs on port 8822. You'll want a client like WinSCP or FileZilla. Your connection details live in Service Settings on the panel.
- Protocol: SFTP
- Host: your server's address (shown in Service Settings)
- Port: 8822
- Username/Password: same as your panel credentials for this service
Once connected, navigate to the server root on the remote side and drag your local world folder over. SFTP handles big transfers more reliably than a browser File Manager, and you get a real progress bar – handy when you're shifting a 2 GB modded save that took hours to generate.
Updating server.properties
This is the step people forget, then wonder why the server's loaded an empty world.
You need to tell the server which folder is your world. Open server.properties in the server root – Configuration Files in the panel handles this, or edit directly in File Manager.
Find the level-name line and set it to the exact name of the folder you uploaded (case-sensitive). If your folder is My Survival World, the line reads:
level-name=My Survival World
Save. If the name doesn't match, the server will quietly create a new empty world folder on boot and your uploaded save just sits there ignored. Single most common reason "my upload didn't work" tickets land in support.
A note on Paper, Spigot and Bukkit-based servers: these platforms split each world into three folders at the server root – <level-name>, <level-name>_nether and <level-name>_the_end. Vanilla singleplayer keeps the Nether and End inside the main world folder (either as DIM-1/DIM1 on older saves or inside dimensions/ on 26.1+). Pre-26.1 saves convert automatically on first boot – upload as-is and let Paper sort it out. For 26.1+ saves with the new dimensions/ layout, we haven't fully confirmed the auto-split works cleanly, so watch the first-boot logs carefully. If you see errors about missing Nether/End or the sibling folders never appear, stop the server and move dimensions/minecraft/the_nether and dimensions/minecraft/the_end up to be siblings at the server root, renamed to <level-name>_nether and <level-name>_the_end. Then start it again.
If you're running modded (Forge, Fabric, NeoForge), check whether your modpack adds custom dimensions. Some modpacks tuck extra dimension data into subfolders inside the world directory – upload the whole thing and you'll catch them.
Starting Up
Start the server back up from the panel. Give the first boot a minute or two – it'll be slower than usual while it loads chunks, runs any version-migration work if your singleplayer world is from an older format and (on Paper/Spigot) splits out the Nether and End.
Open Web Console to watch the startup logs. You're looking for Done! – that's the ready signal. Any issues loading the world will surface here, and they're usually pretty clear about what's wrong (corrupted chunk, missing dimension, version mismatch).
Once it's up, grab your connection details from the panel and join. Your singleplayer character carries over – log in with the same Microsoft account and you'll spawn at your last position with inventory and XP intact, because that data lives in playerdata/<your-uuid>.dat.
A Few Things to Know
Version mismatches are the most common gotcha. A singleplayer world is locked to whichever Minecraft version last opened it. If your client's on 26.1 and the server's still on 1.21.4, the server will refuse to load it (or, on a bad day, silently upgrade it and lose things along the way). Match the server version to your client before you upload – the panel's version selector handles this.
Modpack saves need the same modpack on the server. Playing All The Mods 9 locally and then uploading that world to a vanilla server nets you endless "missing block" errors and any modded items become air. Install the same modpack server-side first, then upload.
The save format is binary, not editable by hand. level.dat is gzipped NBT and .mca region files use a custom binary layout. If you need to read or edit them, NBTExplorer handles level.dat and Amulet handles region files. A text editor will just show you gibberish.
Going back the other way works too. Fancy pulling your server world down to carry on offline? Stop the server, grab the <level-name>, <level-name>_nether and <level-name>_the_end folders over SFTP and merge them back into a vanilla layout. On a pre-26.1 client that means moving the contents of _nether and _the_end into DIM-1 and DIM1 inside the main folder. On 26.1+ it's dimensions/minecraft/the_nether and dimensions/minecraft/the_end. Drop the resulting folder into %APPDATA%\.minecraft\saves\. Fiddlier than uploading, but nothing scary.
If something goes sideways post-upload, that's what your backup is for. Open Cloud Restore, pick the backup you made earlier, and you're back to square one. For more on tuning the server once your save's loaded, see the Minecraft Server Configuration Guide.