Guides

Minecraft Server Backups: What to Backup, How Often, and How to Restore

Don't lose your world. Learn exactly what to backup—world folder, configs, plugins—how often to run backups, and how to restore when something goes wrong.

Milo G.February 13, 202610 min read
Minecraft Server Backups: What to Backup, How Often, and How to Restore

Losing your Minecraft world or server config is painful—and avoidable. A solid Minecraft server backup strategy means knowing what to backup, how often, and how to restore when something goes wrong. This guide covers exactly that, with no fluff.

What to Backup

Your server has a few critical pieces. Miss one and a restore can leave you with a broken or outdated setup.

World folder(s)

The world directory (or world_nether, world_the_end for vanilla) holds all chunks, player data, and structures. This is the most important backup—without it you lose the world. For modded servers, world names may differ (e.g. DIM-1 for Nether).

Config files

server.properties, ops.json, whitelist.json, banned-*.json, and any custom JVM flags or startup scripts. These define rules, who can join, and how the server runs.

Plugins or mods

Backup the plugins folder (and each plugin's config/data) for Spigot/Paper; for Forge/Fabric, backup mods plus config and defaultconfigs if present. Plugin/mod configs hold permissions, economy data, and custom settings—restoring without them resets everything.

Server jar and pack config (optional but useful)

If you run a specific modpack or custom jar, note the pack name/version or keep a copy of the jar. That way you can recreate the same environment if you ever migrate to a new host or rebuild from scratch.

How Often to Backup

Frequency depends on how much you're willing to lose. More backups = more storage and (if automated) more CPU/disk use during the backup; fewer backups = bigger risk.

  • Daily (automated) – Good default for most servers. Covers a full day of play; if something breaks, you lose at most 24 hours.
  • Before any update – Server jar, modpack, or plugin updates can corrupt worlds or configs. Always backup right before you apply an update.
  • Before major changes – Big WorldEdit jobs, map resets, or switching server software (e.g. vanilla → Paper). One manual backup before you run the change is cheap insurance.
  • After major milestones – Some admins keep a "golden" backup after a successful event or season start so they have a known-good restore point.

Retention: Keep at least 2–3 backup cycles (e.g. last 3 days) so you can go back further if you don't notice a problem immediately. Some hosts rotate backups automatically; if you do manual backups, name them with dates (e.g. world-backup-2026-02-13).

How to Restore

Restoring means putting the backed-up files back in place and starting the server again. Do it in order so you don't overwrite good data with bad.

  1. Stop the server – Fully stop the Minecraft server so no files are in use. A restart is not enough; the process must be stopped.
  2. Replace world folder(s) – Delete or rename the current world (and world_nether, world_the_end if applicable). Copy the backup world folder(s) into the server root with the correct name(s).
  3. Replace configs and plugins/mods if needed – If you backed up and are restoring server.properties, plugin configs, or mod configs, overwrite the current ones with the backup versions.
  4. Start the server – Start the server and check logs for errors. Join and verify the world and permissions look correct.

If your host provides a backup panel (e.g. "Restore from backup"), they usually handle steps 1–3 for you—you pick a backup and confirm. Manual restore is the same idea: stop server, replace files, start server.

Host Backups vs Manual Backups

Many Minecraft server hosts offer automated backups (daily, weekly) and one-click restore. That's the easiest option: set the schedule, keep a few retention points, and use the panel to restore if needed. Downsides: you depend on their storage and retention; if you leave the host, you need to download those backups before you go.

Manual backups mean you download or copy the world and important folders yourself (via FTP, SFTP, or a file manager in the host panel). You control where they live (your PC, cloud storage) and how long you keep them. Best practice: use both. Rely on the host for daily automated backups, and do a manual backup before big changes or when you want an extra copy off the host.

Quick Backup Checklist

  • ✓ World folder(s) (world, world_nether, world_the_end or modded equivalents)
  • ✓ server.properties, ops.json, whitelist.json, banned-*.json
  • ✓ plugins folder + plugin configs (Paper/Spigot) or mods + config (Forge/Fabric)
  • ✓ Backup daily (automated) and before any update or major change
  • ✓ Keep 2–3 backup cycles; name manual backups with dates
  • ✓ Restore: stop server → replace world/config/plugins → start server

A good Minecraft server backup routine takes a few minutes to set up and can save you from losing weeks of work. Know what to backup, how often, and how to restore—then you're covered when something goes wrong. For more on keeping your server healthy, see what a healthy Minecraft server feels like and why Minecraft servers lag.

Need reliable hosting with backups?

BiomeHosting includes backup options so you can protect your world. Check our plans and get started.

View Plans
Minecraft Server Backups: What to Backup, How Often, and How to Restore | BiomeHosting Blog