Valheim Server Lost Progress After a Restart? Why and How to Fix It

When a Valheim dedicated server comes back after a restart missing the last half hour of building, a boss kill or a portal network, the server stopped before it saved. Valheim saves the world on a timer, every 30 minutes by default, and on a clean shutdown. A crash, a forced kill or a power cut throws away everything since the last save. Lower the save interval with -saveinterval, always stop the server cleanly, and have an admin run save before planned restarts.

Why it happens

A Valheim server holds the world in memory and writes it to disk in two situations:

1. On the save timer. The launch option -saveinterval sets it, in seconds. The default is 1800, so 30 minutes.
2. On a clean shutdown. Pressing Ctrl+C in the server window, or a stop signal from a host, makes the server save and then exit.

Anything else that ends the process skips the save: closing the window with the X button, ending the task in Task Manager, a crash, a server that runs out of memory, a reboot by Windows Update, or the PC losing power. The world reverts to the last timed save.

Players notice it most after a crash, because they remember what they built in the last few minutes and it is gone.

Characters and the world save separately

This is why a lost save feels so strange. Each player's character (skills, inventory, known recipes) is saved on their own PC, not on the server. The world (terrain, buildings, chests, portals, boss altars) is saved on the server.

So when the world rolls back 20 minutes and characters do not:

• A player who took copper out of a chest still has the copper, and the chest has it again. Items duplicate.
• A player who put ore into a chest no longer has it, and the chest is back to how it was. Items vanish.
• A boss kill can roll back while the player keeps the trophy.

Nothing is broken, the two saves are just from different times. Sort out duplicated or lost items as a group after any rollback.

Fix 1: Lower the save interval

Add or change -saveinterval on the server's start line:

valheim_server -nographics -batchmode -name "Viking Crew" -port 2456 -world "Midgard" -password "longsecret" -saveinterval 600

Each save causes a brief pause for everyone on the server, longer as the world grows. Pick the lowest value that does not make that pause annoying. Valheim 1.0's folder based save format writes only changed chunks, so saves are faster than they were on older worlds, but late game worlds still feel them.

Fix 2: Stop the server the right way

On a home server:

• In the server's console window, press Ctrl+C and wait. The log shows the world saving, then the server shuts down. Close the window only after that.
• If you run it from start_headless_server.bat, do not close the batch window with the X. Use Ctrl+C there too.
• On Linux, send SIGINT (Ctrl+C in the terminal, or kill -INT <pid>), not kill -9.
• Turn off automatic Windows restarts while hosting. The guide on stopping Windows from restarting covers the settings.

Fix 3: Save before planned restarts and updates

Admins on adminlist.txt can force a save from the in game console (F5):

save

Run it before restarting the server for an update or a settings change, and before boss fights if your group likes a safety net. The admin commands guide shows how to add yourself to the admin list.

Fix 4: Stop the crashes

A save interval only limits the damage. If the server crashes often, find out why:

• Out of memory. Big bases and modpacks push RAM use up. Watch memory before a crash. The requirements guide has realistic numbers.
• A mod. On a BepInEx server, check BepInEx/LogOutput.log for errors just before the crash. Mods that are not updated for the current Valheim version are the usual suspect after a patch.
• The host PC. Sleep, updates and power settings on a home PC end the server process without warning.

Recovering from a rollback

If you just lost progress and want it back, check the automatic backups. The server keeps copies next to the world on a schedule set by -backups (how many to keep, 4 by default), -backupshort (first backup after 2 hours) and -backuplong (then every 12 hours). They are older than the last timed save, so they do not bring back lost minutes. They help when the main world file is damaged after a crash and will not load. The world save location guide shows where these files are and how to restore one.

Hosting without the risk

On a GamezServers Valheim server, the Stop and Restart buttons shut Valheim down properly so it saves first, the server does not share a PC that can sleep or reboot for updates, and one click backups give you a restore point before boss fights or patches. If your group has lost one evening of building too many, see the Valheim server for friends page.

FAQ

How often does a Valheim dedicated server save?

Every 30 minutes by default (-saveinterval 1800), plus on a clean shutdown with Ctrl+C.

Why do we have duplicated items after a crash?

Characters save on each player's PC, the world saves on the server. After a crash the world goes back to its last save while characters keep what they picked up, so items exist in both places.

Can I make Valheim save every minute?

You can set -saveinterval 60, but every save causes a short freeze. On anything beyond a small world, 5 to 15 minutes is more comfortable.

Does closing the server window save the world?

No. Closing the window ends the process without saving. Use Ctrl+C and wait for the save to finish.