Short answer
Stop the server, move the current world folder aside rather than deleting it, extract the backup so the world folder sits beside server.properties, check level-name matches it, and start. The console line Preparing level "<name>" is how you confirm which world loaded.
A restore is a file swap, and the only irreversible part of it is the world folder you are replacing. Which is why the first step is to move it aside rather than delete it: if the backup turns out to be the wrong one, or half a day old, the thing you were trying to recover is still there.
This guide covers the swap, the two settings that make restores silently do nothing, and how to confirm afterwards that you are playing on the world you meant to.
Before you start
- A backup archive, and a date you know it covers
- File access to the server folder
- Players off the server for the duration
1. Stop the server and preserve what is there
The server must not be running. Two processes on one world is how a restore turns a bad day into a worse one, and it is the single most important step.
Rename the current world folder rather than deleting it. Something like world.broken costs nothing and gives you a way back if the backup was not what you expected.
world/ <- the world as it is now (griefed, corrupted, whatever)
backup-2026-10-14.tar.gz <- the archive you are restoring
server.properties2. Extract the archive so the world folder is in the right place
Extract in the server root, so the result is a world folder beside server.properties, plugins and the JAR. If the archive contains a top-level folder of a different name, the extracted folder's name is the one that matters.
Check what landed before starting: the world folder should contain level.dat, region, playerdata and entities. If it contains a folder called world inside another world, the nesting is wrong and the server will generate an empty one.
cd /opt/mc
mv world world.broken-$(date +%H%M)
tar -xzf backup-2026-10-14.tar.gz
ls -d world*/
ls world | headworld/
level.dat
region/
playerdata/
entities/
stats/3. Check level-name and the Minecraft version
level-name in server.properties tells the server which folder to load, and it defaults to world. If your backup extracted into a folder called something-else, either rename the folder or set level-name to match. This is the single most common reason a restore appears to do nothing.
The version matters in one direction only. A world can be restored onto a server of the same version or newer; restoring onto an older server fails, because the data written by the newer version is not something the older one can read.
level-name=world4. Start it and confirm which world loaded
The console names the level as it prepares it. Read that line: Preparing level "world" means it found the folder you expected, and Preparing spawn area after it means the world is usable. A fresh world folder appearing in your files after the start means it generated a new one and your backup was in the wrong place.
The first start after a restore is slower than usual, because the spawn chunks are being written for the first time. Let it finish.
[12:31:02 INFO]: Preparing level "world"
[12:31:05 INFO]: Preparing spawn area: 84%
[12:31:11 INFO]: Done (16.204s)! For help, type "help"5. Verify in game before you delete anything
Join and look for the things you are restoring: the base, the chests, the players' inventories, the terrain around spawn. Player data is part of the world folder, so inventories and positions come back with it if the backup covered them.
Only after a session of normal play should the folder you moved aside be deleted. A restore that looks right at spawn can still be missing a region, and the copy you kept is the only way to try an older backup.
Good to know
- If you are restoring because of corruption, the cause may still be present. A damaged region file restored from a good backup will be damaged again if the disk or the memory is failing.
- Restoring is the moment to restore plugin configurations too. A backup that contains a world and the configuration that caused the problem reproduces the problem.
- A restore rolls the whole server back, including the play that happened after the backup. Tell players what date they are returning to.
- Backing up is where the archive comes from, and uploading a world is the same operation when the destination is a different server.
Common questions
Why is my server still showing the old world after a restore?
Because level-name in server.properties names a different folder, so the server generated or loaded a different world. Check the folder name after extracting and make level-name match it exactly.
Do I need to delete the old world folder?
Not at first. Move it aside rather than deleting it, start the server and confirm the restore worked, and only delete it after playing a session. That copy is the way back if the backup was not the one you needed.
Can I restore a backup onto a newer Minecraft version?
Yes. The server upgrades the world on first start, the same way it does for a version change. Restoring onto an older version does not work: the newer data cannot be read by older software.
Will players get their inventories back?
Yes, if the backup includes world/playerdata, which a complete backup of the world folder does. Players get back the inventory they had at the time of the backup, not now.
The world restored but a plugin still breaks. Now what?
Restore the plugin configuration from the same backup, or remove the plugin and start. A world restored under a broken configuration reproduces the problem, which is why both come from the same archive.
Sources
Official documentation this guide was checked against.
Rather not run this on your own machine? PufferHost gives every player a free Minecraft server with 3 GB of RAM and 10 slots. Create a free server.