Valheim 1.0: update a server and keep your existing world

Prepare a recoverable copy

Tell players about the maintenance window, close access and stop the server properly. Export the complete world, including its matching .db and .fwl files, launch settings and mod versions. Keep the archive outside the server.

Record the exact world name and useful landmarks: the main base, storage, portals and expected progression. Characters have their own saves, so ask players to protect those as well. A backup stored only on the disk you plan to reinstall is not an adequate rollback plan.

Check Deep North and mod compatibility

New biome content depends on unexplored areas. Do not assume previously generated northern terrain will automatically be rebuilt. If the group explored much of it, compare continuing the world with starting another one while retaining the original.

A mod working before 1.0 does not establish current compatibility. Check the author's supported release and test the intended combination on a copy. Removing content mods directly from the main world can affect objects and structures that depend on them.

Update and run an acceptance check

Update the server through its panel and align client versions. Open a small test session first. Visit the recorded landmarks, check permissions and crossplay connections, then complete a save-and-restart cycle.

Keep the logs if loading fails. If a fresh world starts while the copied world fails, investigate saves and mods. If neither starts, examine installation and startup configuration.

Keep rollback realistic

Restoring requires an earlier backup and a compatible server environment. Do not mix an old world file with another file from a different snapshot. If the provider no longer offers the previous server version, establish the available recovery options before reinstalling.

Frequently asked questions