Skip to main content
Backups are the cheapest insurance you’ll ever have for your server. Worlds get corrupted, mods go wrong, and updates occasionally break saves — a recent backup turns any of these from a disaster into a two-minute fix.

​
Creating a Backup

1

Open the Backups tab

Log in to the Game Panel, select your server, and open the Backups section.
2

Create the backup

Click Create Backup. You can optionally name it (for example before-update-1.21) so you can identify it later.
3

Wait for completion

Small servers finish in seconds; heavily modded servers with large worlds can take a few minutes. The backup appears in the list when it’s done.
Name backups after why you made them — pre-wipe, before-oxide-update, working-modpack — future you will thank present you.

​
Restoring a Backup

  1. Stop your server from the Console.
  2. Open Backups, find the backup you want, and choose Restore.
  3. Wait for the restore to finish, then start the server again.
Restoring replaces the current server files with the contents of the backup. Anything changed since that backup was created will be lost — if in doubt, create a fresh backup of the current state first.

​
Downloading Backups

You can download any backup as an archive to your own computer from the Backups list. We recommend keeping an offline copy of your most important worlds — especially before big changes like map wipes or major game updates.

​
Scheduling Automatic Backups

Use the Schedules feature in the panel to automate backups:
  1. Open Schedules and create a new schedule (for example, daily at 05:00).
  2. Add a Create Backup task to the schedule.
  3. Optionally chain a server restart afterwards during off-peak hours.
Backup slots are limited per plan. When all slots are full, delete an old backup (or let the schedule rotate them) before creating a new one. Need more slots? Contact support.

​
When You Should Always Back Up

SituationWhy
Before game updatesUpdates can break saves, mods, and plugins
Before installing mods/pluginsA bad mod can corrupt your world
Before editing config or economy filesSyntax errors can prevent startup
Before a map or blueprint wipeWipes are irreversible without a backup
Before restoring another backupPreserves your current state as a fallback

​
Backup Best Practices

  • Automate it — a daily scheduled backup means you never lose more than a day.
  • Back up before, not after — make it a reflex before any risky change.
  • Keep an offline copy — download your most valuable worlds monthly.
  • Test your backups — occasionally restore one to confirm it works as expected.

Need a bigger server for your growing world?

Upgrade anytime from the billing area — your files and backups are kept during the upgrade.