How to Back Up and Restore a Minecraft Server

01Know what to back up

A Minecraft server's state is spread across more files than just “the world”. A complete backup includes:

• World folders: world, world_nether, and world_the_end. On Paper/Spigot the three dimensions are separate folders — backing up only world loses the Nether and End. (Vanilla keeps all three inside one world folder.)
• Server config: server.properties, plus bukkit.yml, spigot.yml, and paper-global.yml if you have tuned them.
• Player-list JSONs: whitelist.json, ops.json, banned-players.json, and banned-ips.json. Losing these silently un-bans everyone and drops your whitelist.
• Plugins and their data: the whole plugins/ folder — not just the jars but the config subfolders, which hold economy balances, protected regions, permissions, and other data you really do not want to rebuild.

If in doubt, back up the entire server directory. World folders dominate the size anyway; the configs add almost nothing.

02Stop the server, or freeze saving for a live backup

The gold-standard backup is taken with the server stopped — nothing is writing to the world files, so the copy is guaranteed consistent. For a server you cannot take down, Minecraft provides commands to make a live copy safe:

save-off        # pause automatic world saving
save-all flush  # force everything in memory to disk
(copy the files now)
save-on         # resume normal saving

Copying a live world without save-off risks catching a region file mid-write, which is how you end up with a backup that itself contains corrupted chunks. The sequence above is exactly what serious backup plugins run under the bonnet.

03Copy the files into a dated archive

Zip the folders from step 1 into a single archive named by date, so restores are unambiguous:

zip -r backup-2026-08-04.zip world world_nether world_the_end \
    server.properties whitelist.json ops.json \
    banned-players.json banned-ips.json plugins

On Windows, select the same folders and Send to → Compressed folder. Compression matters: world files zip down to a fraction of their raw size, which makes off-server storage (step 4) practical.

04Store backups away from the server

A backup sitting next to the live world protects you from a bad plugin update, but not from a failed disk, a billing lapse, or a compromised server. Download the archive to your own machine, or push it to cloud storage. Keep more than one: a sensible minimum rotation is 7 daily backups plus a few weeklies, because world corruption is often discovered days after it happened — if you only keep last night's backup, you may find it already contains the damage.

05Restore: stop, replace, start

The restore procedure is the backup in reverse:

• Stop the server. Never extract files into a running server — it will overwrite them from memory on shutdown, or crash.
• Move the broken state aside — rename world to world_broken rather than deleting it, in case you need to recover anything from it later.
• Extract the backup's folders into place so the paths match exactly what the server expects (world, world_nether, world_the_end, etc.).
• Start the server and verify in-game that the world state matches the backup date. Warn players first: everything since that backup is gone.

06Automate it

Manual backups are the ones that stop happening. Automate with whichever you have available: your host panel's scheduled backups, a cron job that runs the step 2 command cycle nightly via the server console (RCON or a screen/tmux session), or a backup plugin that handles save-off/save-on itself. Schedule for your quietest hour, and check occasionally that the archives are actually being produced and are non-empty — an untested backup system is a hope, not a plan.

Run it on HostPanel: our Minecraft server hosting plans include scheduled automatic backups with one-click restore from the panel.

Troubleshooting

I restored the world but the Nether and End are wrong

You restored world but not world_nether and world_the_end — on Paper/Spigot they are separate folders and must be restored together, or portals lead to out-of-sync dimensions.

My backup contains corrupted chunks too

Either the backup was taken from a live server without save-off, or the corruption predates your oldest backup. The first is fixed by using the step 2 sequence going forward; the second is why you keep a longer rotation than one night.

After restoring, plugin data doesn't match the world

You restored the world folders but not plugins/ (or vice versa), so things like protected regions and economy balances refer to a different point in time. Always restore world and plugin data from the same archive.