How to back up your Minecraft server
Griefers, a broken plugin update or a corrupted chunk can undo months of building. A backup turns that into a five-minute fix. Here's what to back up and how.
What to back up
- The worlds:
world,world_netherandworld_the_end(on vanilla, Nether and End are insideworld). - Plugin or mod settings: the folders in
plugins/orconfig/, which hold claims, homes, ranks and economies. - Server files:
server.properties,whitelist.json,ops.jsonandbanned-players.json.
The plugin and mod .jar files themselves are easy to download again; their data isn't.
Back up safely
Copying a world while the server writes to it can give you a half-saved copy. Either stop the server first, or run save-off then save-all flush in the console, copy the files, and run save-on afterwards.
Backups on Jump
- Paid plans back up automatically every hour, keeping one from the last hour, one about a day old and one about a week old. Back up now in the panel takes one any time.
- Restoring is one click on the Backups page. Jump backs up the current state first, so a restore can be undone too.
- Jump also backs up on its own before risky changes, like switching version or installing a modpack.
- Free servers have no backups. Download the world from Files (or over SFTP) before anything risky, and now and then anyway.
The backups guide covers downloading a backup to keep on your own computer.
Restoring by hand
- Stop the server.
- Rename the current
worldfolder (for exampleworld-broken) rather than deleting it. - Upload the backed-up world folder in its place, then start the server.
Questions
How often should I back up?
Daily for a friends' server, more often for a busy public one. Always back up right before an update.
Can I roll back one griefed area instead of the whole world?
Yes, with a plugin such as CoreProtect, which logs block changes and can undo one player's actions. Install it before you need it.

