Guide Minecraft

Back Up and Restore a Minecraft Java Server

Back up a Minecraft Java server safely, including worlds, mods, plugins and configuration. Restore complete Paper, Fabric or NeoForge installations after failed updates.

Minecraft Java Edition game artwork
Source: coop-legends.de

Overview

A Minecraft server backup should exist before a major update or mod causes trouble. For Paper, Fabric, and NeoForge, the most reliable simple manual approach is to shut the server down completely and then copy the entire server directory. This keeps the world, server configuration, plugins or mods, and related files together.

PaperMC specifically warns against modifying server files while the server is running because files can become corrupted. For a straightforward manual backup, Paper also describes archiving the complete server folder as a ZIP file.

Last restore procedure review: September 3, 2026, using Minecraft Java Edition 26.2 with Paper, Fabric, and NeoForge. Minecraft Java 26.3 was released September 15, 2026. The procedure below has not been retested for every 26.3 mod-loader build; check the corresponding loader and server versions before restoring or upgrading.

What should a Minecraft server backup include?

For a complete restore, the simplest choice is the entire server directory. Paper recommends protecting the world, server configuration, plugins, and plugin configuration before updates. A Fabric or NeoForge installation likewise needs its mods and mod configuration preserved alongside world files.

  • World files and dimensions.
  • server.properties and other server configuration.
  • Paper plugins and their settings.
  • Fabric or NeoForge mods and their configuration files.
  • Launch scripts and JVM settings.
  • Allowlist, operator, and ban lists, if stored in the server directory.

A complete copy is especially helpful for migrations because world storage and directory layout can vary between server implementations and Minecraft releases. Paper has specific migration procedures and expressly recommends a full backup before changing server software.

Create a complete backup step by step

  1. Warn players about the restart and let them finish what they are doing.
  2. Stop the server cleanly using stop in the server console or your hosting panel's stop function.
  3. Wait until the server process has fully exited. Do not archive files while they are still being written.
  4. Copy the entire server folder to a separate location or create a ZIP archive.
  5. Give the backup a descriptive name, for example minecraft-server_2026-10-19_before-update.zip.
  6. Inspect the archive to make sure worlds, configuration, and plugin or mod files are present.
  7. Restart the production server only after the backup has finished.

The file-naming example is a practical organizational suggestion; Paper does not require a particular naming convention.

Why you should stop the server before copying files

PaperMC warns that changing server files while they are in active use can corrupt data. A manual file backup taken during a save operation can likewise capture files from inconsistent points in time.

For a basic manual backup, do not simply kick every player: shut down the actual server process. This is especially important before updating Minecraft, replacing a mod loader, changing plugins or mods, or moving from Vanilla to Paper.

Back up before updating Paper, Fabric, or NeoForge

Paper

Paper recommends having working backups before upgrading. It highlights world directories, server configuration, plugin JARs, and plugin settings. Do not replace the Paper JAR while the server is still running.

Fabric

Fabric explicitly recommended making world backups for the Minecraft 26.2 transition. With a modded server, keep the installed mod JARs and their matching configurations together with the world so you can reproduce the previous working setup.

NeoForge

NeoForged's official server documentation recommends backing up worlds before updating NeoForge or its mods. For a reliable full rollback, preserve the whole server directory as well.

Restore your Minecraft server from a backup

  1. Shut down the server completely.
  2. Save the current broken state separately if you might need logs or files for diagnosing the failure.
  3. Move aside or remove the current server directory. Avoid selectively overwriting files in a partly upgraded installation.
  4. Extract the full backup into a clean server directory.
  5. Check the server software and Java versions. Ideally, start the backup using the Paper, Fabric, or NeoForge release it was originally made for. Minecraft 26.2 uses Java 25.
  6. Start the server and watch the console for world, mod, plugin, or missing-dependency errors.
  7. Test the restored server before deleting the previous backup or the damaged installation.

Restoring only the world while combining it with plugins, mods, or configuration from a different version is not a full rollback. A mismatched mod release may be enough to prevent the server from starting or alter the world's content.

Do not mix Paper world layouts and Minecraft versions

Paper documents separate migration instructions for switching to and from Vanilla or other server variants. Minecraft 26.1 also changed aspects of world storage. Do not assume that copying a few dimension directories from an old tutorial will recreate a complete world correctly.

For the procedure described here, the safer default is intentionally simple: stop the server, archive the whole directory, and test the restore in a separate copy first. If you are moving between Paper, Vanilla, Fabric, NeoForge, or another server implementation, follow that project's up-to-date migration instructions in addition to taking the backup.

Keep backups away from the production server

A backup inside the same server folder does not protect against a failed storage drive or accidental deletion of that entire installation. Keep at least one recent backup separate from the live server. Paper recommends retaining several backup points, and rotating backups is a common strategy.

The right number of generations and storage locations depends on your world and available storage. What matters is having more than one untested archive and knowing that you can actually restore a working copy.

Minecraft server backup FAQ

For a simple manual file backup, yes. PaperMC warns that modifying server files while they are running can cause corruption. Wait for a complete shutdown before copying the server directory.

It may be enough for a world-only copy, but not for fully restoring the server. Keep configuration files and, for Paper, plugins; for Fabric or NeoForge, keep the mods and their settings.

Yes. PaperMC describes archiving the whole server folder as a suitable simple manual backup method.

Minecraft Java Edition 26.2 requires Java 25. For other Minecraft versions and mod loaders, verify the matching Java requirement before restoring.

Yes. NeoForged's official server documentation warns users to back up their world before updating NeoForge or mods.

For co-op modes and platform support, see the Minecraft game profile.

Sources