How to Transfer a Valheim World to a Dedicated Server

Identify whether your world uses legacy saves or Valheim 1.0 world folders

Valheim worlds created or converted under 1.0 may use directory-based, chunked world storage, while older guides describe the legacy .db and .fwl file pair.

This matters because a guide written before September 2026 may tell you to copy exactly two files even when your current world consists of a directory with multiple files. Treat the entire world as one unit, preserve its original structure and verify the resulting world loads.

Iron Gate confirmed a save-system rework during the 1.0 testing period. Its October 2026 patch notes also mention chunk splitting, which makes a complete backup especially important. The precise folder layout depends on the running build and hosting environment.

Find local Valheim world saves on Windows or Linux

Local Valheim world saves are commonly stored under the IronGate/Valheim application-data folder, but cloud saves and custom -savedir options can change their location.

Typical Windows local folder: %USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local. Typical Linux native folder: ~/.config/unity3d/IronGate/Valheim/worlds_local. Check the game’s Manage Saves interface or the configured save directory if the expected folder is empty.

Steam Cloud-backed worlds may be stored separately. The game UI may be the safer route for identifying the correct copy. Do not assume a directory modification timestamp alone proves which world is newest.

Windows local worlds:
%USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local

Linux native local worlds:
~/.config/unity3d/IronGate/Valheim/worlds_local

Back up both source and destination before migrating

A safe Valheim migration begins with two independently stored backups, one of the original world and one of anything currently on the destination.

Ask all players to disconnect, trigger a manual save where available, then stop the server normally. Copy the complete source world data to a separate local folder or offsite location. Keep the destination’s previous save until you have verified the replacement.

Use our backup and restore checklist before copying anything into the host’s live data directory.

Upload the world to a rented Valheim server

Most managed hosts support world imports through their panel or file access, but the exact upload folder and naming rules vary between providers.

Find the configured save root, often controlled by -savedir. Upload the whole current-format world folder or the legacy file set without flattening its internal structure. Some panels require an explicit “Import World” action instead of direct file copying.

Set the server’s -world name to match the imported world selection. If you cannot locate the upload destination, consult that provider’s documentation rather than guessing. The Valheim hosting comparison helps you shortlist providers with migration or file-access tools.

• Stop the destination server and preserve its existing world.
• Upload all source-world components, not only the first matching file.
• Choose or configure the imported world in the host panel.
• Restart once and inspect the startup log for file or version errors.
• Join and check known buildings, inventories and explored locations.

Move a world between two Valheim hosts

A host-to-host transfer follows the same data-integrity workflow as local-to-host migration, with particular care for source save roots and server build versions.

First export the current world from the old host and save it independently. Provision the new instance, confirm a compatible game version and shut it down before importing. Migrate server-specific configuration separately from world data; panel settings and permission files may not follow the world automatically.

Keep the old host active until you have tested the destination with other players and know how to revert.

Verify the Valheim world after migration

A successful server boot is not enough to prove the correct Valheim world transferred; test recognizable structures and actual multiplayer persistence.

Confirm the world name and seed match expectations, inspect an established base, place an unimportant object and verify it persists after a clean stop and restart. Check that permissions and crossplay settings still behave as expected.

If you see an empty world, stop immediately and verify the selected -world value and imported directory rather than continuing to overwrite the original.

What if the save is corrupt or the new server starts empty?

Migration failures are usually best handled by reverting to the preserved original, then diagnosing a missing component, mismatched save directory or incompatible server build.

Do not repeatedly convert the only source save or rename chunks blindly. Check server logs, confirm current 1.0 support, and use the host’s restore tool if you need to roll back. Our server setup guide covers the relevant launch arguments.