How to Backup A Minecraft Server

Learning how to backup a Minecraft server’s files is one of the most important things you can do as a server owner. A good backup protects your world, player progress, plugins, mods, and configuration files if something breaks or gets deleted.

Minecraft servers can run for weeks or months with no issues, but problems can happen quickly. A plugin update can fail, a world can become corrupted, a player may accidentally destroy something important, or a version update may not go as planned. Paper’s own update guidance specifically recommends backing up world folders, server configuration files, plugin configuration files, and plugin JARs before making major changes.

This guide explains how to backup a Minecraft server in two ways:

• Creating a backup through the Game Panel, which stores the backup remotely in S3
• Downloading the correct server files manually to your computer

This guide is written for Minecraft: Java Edition servers, including Vanilla, Paper, Spigot, Purpur, Forge, and Fabric servers.

Why Minecraft Server Backups Matter #

A Minecraft server backup is a saved copy of your server files. If something goes wrong, you can restore that copy and return the server to an earlier working state.

Backups are especially important before:

• Updating Minecraft versions
• Installing new plugins
• Adding or removing mods
• Changing server configuration files
• Resetting worlds
• Testing new datapacks
• Making major permission changes
• Migrating to a new server or host

A backup gives you a rollback point. Without one, a broken plugin, corrupted world, or accidental file deletion can become a much bigger problem.

What Should Be Included in a Minecraft Server Backup? #

A proper Minecraft server backup should include more than just the main world folder.

At minimum, you should back up:

• World folders
• Player data
• Plugin files
• Plugin configuration files
• Mod files
• Server configuration files
• Permission data
• Whitelist, ban, and operator files

For Paper, Spigot, and other Bukkit-based servers, worlds are often split into separate folders such as:

world
world_nether
world_the_end

For Vanilla Minecraft servers, Nether and End data may be stored inside the main world folder in dimension folders instead. Paper’s migration documentation shows the difference between Vanilla-style dimension storage and Bukkit/Paper-style separate world folders.

Because of this, the safest approach is to back up the entire server folder whenever possible.

Method 1: Create a Manual Backup in the Game Panel #

The easiest way to manually backup Minecraft server files is by using the Backups section in the Game Panel. This method is recommended because it packages the backup for you and stores it remotely in S3 instead of only keeping it on the server.

Remote S3 storage is useful because the backup is not sitting on the same machine as the active server. If the server files are damaged or the node has an issue, the backup is still stored separately.

Step 1: Open the Game Panel #

Log in to your server’s Game Panel.

From the server dashboard, select the Minecraft server you want to back up.

Step 2: Stop the Server #

Before creating a backup, stop the server fully.

This helps make sure all world data, player data, and plugin files are saved cleanly before the backup is created.

If you create a backup while the server is actively running, there is a higher chance that files may change during the backup process.

Step 3: Go to the Backups Section #

In the Game Panel, open the Backups tab or section.

This is where you can view existing backups and create new manual backups.

Step 4: Create a New Manual Backup #

Click the option to create a new backup.

Give the backup a clear name, such as:

Before-Plugin-Update

or:

Pre-1-21-Update-Backup

Use names that explain why the backup was created. This makes it much easier to identify the right backup later.

Step 5: Start the Backup #

Start the manual backup process.

The Game Panel will package the server files and upload the backup to remote S3 storage. Depending on your server size, this may take some time.

Large worlds, modded servers, Dynmap folders, and plugin data can make backups much larger.

Step 6: Confirm the Backup Completed #

Do not assume the backup is finished until the panel shows it as completed.

Before making major changes, confirm that the backup exists and is available in the Backups section.

A backup is only useful if it actually completed successfully.

Method 2: Manually Download Your Minecraft Server Files #

You can also manually backup Minecraft server files by downloading them to your computer. This is useful if you want your own local copy or if you are preparing to migrate the server.

This method works through your hosting panel’s File Manager or through SFTP.

Step 1: Stop Your Minecraft Server #

Stop the server before downloading files.

This is the safest way to make sure the server is not writing world or player data while you are copying files.

For advanced users, Minecraft has dedicated server save commands such as save-all and save-all flush, which force world and player data to be written to storage. The save-all flush option saves immediately but may freeze the server briefly while the data is written.

For most server owners, stopping the server before backing up is still the cleanest and easiest method.

Step 2: Open the Server Files #

Open your server files using one of these methods:

• Game Panel File Manager
• SFTP
• FTP client such as FileZilla
• Direct local folder access if self-hosting

Your main server folder usually contains files and folders such as:

server.properties
eula.txt
plugins
mods
config
world
world_nether
world_the_end

The exact files may vary depending on whether you run Vanilla, Paper, Spigot, Forge, Fabric, or a modpack.

Step 3: Download the Correct Files #

For the safest manual backup, download the entire server directory.

If you only want the most important files, back up these:

world
world_nether
world_the_end
server.properties
plugins
mods
config
ops.json
whitelist.json
banned-players.json
banned-ips.json
usercache.json

For plugin servers, also back up:

plugins

For modded servers, also back up:

mods
config
defaultconfigs
kubejs

Not every modded server will have all of these folders, but if they exist, they should be included.

For Paper and Spigot servers, the plugins folder is especially important because it often contains permissions, economy data, claims, ranks, homes, warps, and other community-critical information.

Step 4: Compress the Backup #

After downloading the files, compress them into a single archive.

Good backup file formats include:

.zip
.tar.gz
.7z

Use a clear backup name, such as:

minecraft-server-backup-2026-05-06.zip

or:

survival-smp-before-update-2026-05-06.zip

A clear name helps you avoid guessing later.

Step 5: Store the Backup Somewhere Safe #

Do not keep your only backup inside the active server folder.

Store local backups in at least one safe location, such as:

• your computer
• an external drive
• cloud storage
• remote object storage
• a backup folder outside the live server directory

A good backup strategy includes both remote panel backups and local downloads for important milestones.

What Files Matter Most? #

If you are not sure what to save, use this quick reference.

If your server uses LuckPerms, EssentialsX, GriefPrevention, CoreProtect, WorldGuard, or similar plugins, make sure the plugin data folders are included.

How to Restore a Manual Minecraft Server Backup #

Creating backups is only half the job. You should also understand how to restore one.

Step 1: Stop the Server #

Stop the Minecraft server completely before restoring files.

Never restore files while the server is running.

Step 2: Make a Safety Copy of the Current Files #

Before replacing anything, make a quick copy of the current server files.

Even if the server is broken, this gives you a fallback if you accidentally restore the wrong backup.

Step 3: Delete or Replace the Current Files #

Remove or replace the files you want to restore.

For a full restore, this usually means replacing the current server folder with the backup copy.

For a world-only restore, replace the world folders:

world
world_nether
world_the_end

Step 4: Upload the Backup Files #

Upload the backup files through the File Manager, SFTP, or your panel restore tool.

Make sure the folder names match the server’s expected world names.

Step 5: Start the Server #

Start the server again and check that everything loaded correctly.

After restoring, verify:

• the correct world loads
• player inventories are present
• plugins start correctly
• permissions still work
• no major console errors appear

Restoring From a Game Panel Backup #

If you created a backup through the Game Panel, restoring is usually easier.

In the panel:

1. Stop the server
2. Open the Backups section
3. Select the backup you want to restore
4. Choose the restore option
5. Confirm the restore
6. Wait for the process to complete
7. Start the server

Because these backups are stored remotely in S3, they are useful when you need a clean restore point that is separate from the live server files.

Always confirm the restore finished before starting the server.

How Often Should You Backup a Minecraft Server? #

Backup frequency depends on how active your server is.

A good starting point:

For active servers, keep multiple backup versions. Do not overwrite your only working backup.

A simple retention plan could be:

• keep the latest daily backups
• keep a few weekly backups
• keep a special backup before major updates
• delete old backups only after confirming newer ones work

When You Should Always Create a Manual Backup #

Create a manual backup before:

• updating Minecraft
• updating Paper, Spigot, Forge, or Fabric
• installing a new plugin
• removing a plugin
• changing permissions
• adding mods
• removing mods
• editing major config files
• resetting or trimming a world
• migrating to a new host
• troubleshooting corruption

If you are asking yourself whether you should make a backup first, the answer is usually yes.

Common Backup Mistakes to Avoid #

Only Backing Up the Main World Folder #

On many Paper and Spigot servers, the Nether and End are stored in separate folders. If you only download world, you may miss important dimension data.

Back up all world folders.

Forgetting Plugin Data #

Plugins often store important server data. If you forget the plugins folder, you may lose ranks, claims, economy balances, homes, warps, and moderation data.

Keeping Backups Only on the Server #

A backup stored only on the same server is better than nothing, but it is not ideal. If the server storage fails or the folder is deleted, that backup may be lost too.

Use remote S3 backups through the Game Panel and keep local copies for major milestones.

Restoring While the Server Is Running #

This can cause file conflicts and corrupted data.

Always stop the server before restoring.

Not Testing Restores #

A backup should not be trusted blindly. If possible, test important backups on a separate server or test environment before relying on them.

Helpful Internal Links to Add #

Add internal links to related Minecraft guides on your site:

• How to Move a Minecraft Server to a New Host
• How to Edit server.properties on a Minecraft Server
• How to Change Player Slots on Your Minecraft Server
• How to Reduce Minecraft Server Lag by Adjusting View Distance
• Minecraft Server Hosting

A Simple Backup Routine for Server Owners #

For most Minecraft server owners, the best routine is simple:

1. Use the Game Panel to create a manual backup before major changes.
2. Let the panel store that backup remotely in S3.
3. Download a local copy before large updates or migrations.
4. Keep multiple backup versions.
5. Restore only while the server is fully stopped.

A few minutes spent backing up your Minecraft server can save days or weeks of lost progress. Whether you are running a small private world or a growing public SMP, regular backups are one of the easiest ways to protect your server and your players’ work.