How to Recover a Corrupted Game Server World (Before You Start Over)

To recover a corrupted game server world, stop the server, copy the whole save folder as it is, then look for the backups the game made by itself: many games keep rolling copies (.old, .bak, .sav.1, numbered autosaves) right next to the main save. Restore the newest one that loads. If none load, some games let you remove just the damaged part, such as a single Minecraft region file. Never keep restarting on a broken save, because each attempt can overwrite the good copies.

Signs the world is corrupted

The server crashes or hangs while loading the world, but starts fine with a new world name.
The log mentions corrupt, failed to load, unexpected end of file, invalid or a checksum error.
The save file is 0 bytes, or far smaller than usual.
Parts of the map are missing, reset, or crash the server when someone walks there.
Players load in with empty inventories or at spawn, while the world itself is fine (this is player data, not the world).

The usual causes are a server killed mid save (power cut, out of memory, a host restart), a full disk during saving, opening the world in a newer or beta version, and mods that write bad data.

Step 1: stop and copy everything

Stop the server and make sure it stays stopped. If it is stuck restarting, see game server stuck in a crash loop.
Copy the entire save folder, including any backup files, to somewhere else. Work on copies from now on.
Check free disk space. A full disk often caused the damage and will cause it again.

Step 2: look for the game's own backups

Many games quietly keep older copies. Check before you give up:

Game	Where to look	What to do
Minecraft: Java Edition	`level.dat_old` in the world folder	Rename `level.dat` aside, copy `level.dat_old` to `level.dat`
Valheim	`.db.old` and `.fwl.old` next to the world, plus timestamped `_backup_auto` files in `worlds_local`	Copy the backup pair over the main `.db` and `.fwl` with the same base name
Rust	`.sav.1`, `.sav.2` and so on next to the main `.sav`	Rename the damaged `.sav` aside, rename the newest numbered copy to `.sav`
Terraria	`.wld.bak` next to the world	Rename it to `.wld`
Factorio	`_autosave1.zip` to `_autosave5.zip` in `saves`	Load the newest autosave that works
Satisfactory	Several rotating autosaves per session	Load an older autosave from the server manager
Project Zomboid	`Zomboid/backups/` (startup and periodic backups if enabled)	Copy the backup's save folder back
ARK	Timestamped copies of the map save in `Saved/SavedArks`	Rename the latest good copy to the main map file name
Palworld	`backup/world` folder inside the world's save folder	Copy a timestamped backup's files over the main save

Match file names exactly, including case on Linux. Always keep the damaged original in case you need it later.

Step 3: restore your own backup

If you or your host made backups, restore the newest one from before the trouble began. The steps are the same for every game: stop, move the current save aside, copy the backup into place, start and check. Our guide on how to restore a backup on a game server covers it in detail, including player data stored outside the world.

Pick a backup from before the first sign of trouble, not just the most recent. A world that was half broken for a day may have been backed up broken.

Step 4: salvage what you can

When no backup loads, some games let you cut out just the damaged part.

Minecraft

The world is split into region files (region/r.X.Z.mca), each holding 32 by 32 chunks. If the crash log names a chunk or region, or the server crashes when players enter one area:

Find the region file for that area. Region X equals chunk X divided by 32, rounded down, and the same for Z.
Move that one .mca file out of the folder. The game regenerates that area fresh, and the rest of the world is untouched.
Tools like MCA Selector let you see and delete individual chunks instead of whole regions.

Player data lives in playerdata/<uuid>.dat. If one player crashes the server on join, move their file aside. They respawn with an empty inventory, but the server starts.

Games with per player saves

In Valheim, characters are stored on each player's own PC, not the server, so a world rollback does not touch them. In 7 Days to Die and Project Zomboid, player data lives on the server and rolls back with the world. Know which before you restore.

When the main save is truncated

A save of 0 bytes, or cut short, cannot be repaired by hand. Go back to Step 2 and Step 3.

Step 5: test before players return

Start the server with the restored world and watch the console.
Join, walk around the main bases, and check inventories.
Let it autosave once and restart it, to prove it saves and loads cleanly.
Then tell everyone it is back, and which point in time it was restored to.

How to stop it happening again

Back up automatically and often, and keep several older copies, not just the latest. See how to back up a game server.
Shut down cleanly. Use the game's save and stop commands instead of killing the process.
Watch disk space and RAM. Full disks and out of memory kills cause most corruption.
Back up before every update or beta, since newer versions can convert saves in ways older versions cannot read.
Tune autosaves. Frequent saves mean less lost progress. See game server autosave interval settings.

A Minecraft world with builds, the kind of save that region files let you partly repair

Backups that just exist

The best fix for corruption is a backup you did not have to remember to make. On a GamezServers server backups are one click from the panel, the file manager and SFTP give you access to every save file, and the live console shows exactly what happens when you load a restored world. It works the same for Valheim, Rust and our other games.

FAQ

Can a corrupted game server world be fixed?

Often. Many games keep automatic backup copies next to the main save, and some, like Minecraft, let you remove only the damaged region. A completely truncated save can only be replaced from a backup.

What causes world corruption on a server?

Mostly a server stopped in the middle of saving: a crash, power loss, out of memory, or a full disk. Version changes and broken mods are the other common causes.

Will restoring a backup roll back my players?

It depends on the game. Where player data is saved on the server (7 Days to Die, Project Zomboid, Minecraft), it rolls back too. Where characters live on players' PCs (Valheim), only the world changes.

Should I keep the corrupted save?

Yes. Keep a copy until the restored world has run fine for a while. You may need it to recover a build or check what went wrong.