If you already have a Valheim world running in single-player or local co-op, moving it to a dedicated server is one of the best upgrades you can make. A proper Valheim world transfer to dedicated server setup lets your world stay online even when the original host is offline, makes it easier for friends to join, and gives you a better foundation for a long-term multiplayer world.
This guide explains how to transfer a Valheim world to a dedicated server, which files you need, where those files usually live, how to avoid the most common mistakes, and how to make sure the server is actually loading the correct world after the move.
What you actually need to transfer #
A Valheim world is normally tied to two main files:
YourWorld.dbYourWorld.fwl
To move a world properly, you need both files. Community documentation for dedicated servers consistently notes that transferring both the .db and .fwl files is the standard way to move a world and its progress.
In simple terms:
- The
.dbfile contains the world save data - The
.fwlfile contains the world metadata and header information
If you only move one of them, the server may fail to load the world correctly or generate a fresh world instead.
Before you start the transfer #
Before beginning your Valheim world transfer to dedicated server, make a full backup of the existing world files. That means copying both the .db and .fwl files somewhere safe before you upload or replace anything. Community guidance around dedicated servers repeatedly recommends backing up first, especially because incorrect file placement or naming can cause the server to create a new world unexpectedly.
It also helps to check two things before you move the world:
- the exact world name
- whether the save is local or tied to Steam Cloud
Those two details cause a lot of the common transfer issues.
Where Valheim world files are usually stored #
On Windows, many players have historically found Valheim world files under the user profile path inside the IronGate Valheim folders. Community references point to locations such as the worlds folder under the Valheim AppData path, and later save handling discussions also reference worlds_local for local worlds.
In practical terms, the folders you should usually check are:
C:\Users\YourUser\AppData\LocalLow\IronGate\Valheim\worlds
C:\Users\YourUser\AppData\LocalLow\IronGate\Valheim\worlds_local
If your world is stored in the cloud, Steam Cloud behavior can affect what is stored locally and what gets uploaded automatically. The dedicated server documentation on Valheim Wiki notes Steam Cloud interaction with the worlds folder and also points to Steam Remote Storage for manually accessing cloud-backed files.
Local saves vs Steam Cloud saves #
This is one of the most important parts of a Valheim world transfer to dedicated server.
Valheim has used both local and cloud-linked save behavior, and community troubleshooting around dedicated servers shows that the difference between worlds and worlds_local matters. Several discussions and wiki references note that dedicated-server world loading problems often came down to files being in the wrong save folder or the server loading a different location than expected.
The practical takeaway is:
- Check whether your world is local
- If needed, move or export the correct world files before uploading
- Make sure the server is pointed at the same world name as the files you transfer
If you are unsure which copy is current, compare timestamps and file sizes and keep backups of both before making changes. That is the safest way to avoid overwriting the wrong save.
How to transfer a Valheim world to a dedicated server #
Step 1: Stop the dedicated server #
Before uploading or replacing world files, shut the server down completely. This prevents the host from writing new world data while you are replacing files and reduces the chance of corruption or mismatched saves. This is standard best practice for dedicated server world transfers.
Step 2: Find your current world files #
Locate the world you want to move and confirm you have both files:
YourWorld.db
YourWorld.fwl
Make a backup copy of both before continuing.
Step 3: Upload both files to the server #
Upload the .db and .fwl files to the world save location used by your dedicated server. Some server environments still reference worlds, while others may rely on worlds_local, and community troubleshooting shows that incorrect folder placement has been one of the biggest causes of missing-world issues.
If your provider has a file manager, upload them there. If you are running the server yourself, place them in the server’s Valheim world save folder.
Step 4: Make sure the world name matches #
This is where many people accidentally break the transfer.
The name used in your startup script must match the transferred world name without the file extension. Community guidance points out that many dedicated server issues happen because admins change the server name but not the -world value, or they use a world name that does not match the uploaded files.
If your files are named:
MyWorld.db
MyWorld.fwl
Then your startup script or server config should reference:
-world "MyWorld"
Not:
-world "My Server Name"
The server name and the world name are not the same thing.
Step 5: Start the server #
Once the files are uploaded and the world name matches, start the dedicated server again. If everything is correct, the server should load the transferred world instead of creating a fresh one.
Example startup parameter for the transferred world #
A typical startup format for a self-hosted Valheim dedicated server looks like this:
valheim_server -nographics -batchmode -name "My Valheim Server" -port 2456 -world "MyWorld" -password "StrongPass" -public 1
The important part for the transfer is this section:
-world "MyWorld"
That value should match the uploaded .db and .fwl filenames exactly, minus the extensions. Community server troubleshooting specifically highlights this as a common failure point.
How to verify the server loaded the correct world #
After the server starts, do not assume the transfer worked just because the server is online. A Valheim server can come online and still generate a brand-new world if the correct files were not loaded. Community troubleshooting posts describe this exact issue.
The easiest ways to verify are:
- join the server and check if your builds and map progress are there
- confirm the world seed and landmarks match what you expect
- check that the world name in the startup configuration matches the uploaded files
- compare the server-side file timestamps after startup
If you spawn into a fresh world, the server likely loaded the wrong world path or generated a new one because the filenames or folder placement were wrong.
Common mistakes during a Valheim world transfer to dedicated server #
Uploading only one file #
If you upload only the .db file or only the .fwl file, the transfer is incomplete. You should always move both together.
Using the wrong world name in startup settings #
The dedicated server must point to the world name, not the server display name. This is one of the most common causes of “my world is gone” problems.
Putting files in the wrong folder #
Because Valheim save handling has involved both worlds and worlds_local, placing files in the wrong folder can cause the server to ignore them and create a new save.
Replacing the wrong copy of the world #
If Steam Cloud or multiple backups are involved, it is easy to upload an outdated version. Always compare timestamps and keep a backup of every version before overwriting anything.
Starting the server before the upload is complete #
If the server starts before both files are in place, it may generate a new world with the same name or create confusion around which save is current. Back up first, upload both files, then start the server.
Moving a world from one host to another #
The process is almost the same if you are changing providers instead of moving from local play.
You still need:
- the
.dbfile - the
.fwlfile - the correct world name in startup settings
- the correct destination folder on the new server
This makes Valheim world transfer to dedicated server a useful guide not just for first-time setup, but also for migrations between hosting providers or from a local PC to a hosted machine. The same file-based transfer method is described across dedicated server references.
World modifiers and transferred worlds #
If you have changed world modifiers locally, those settings can persist with the world data, and community troubleshooting around dedicated servers has shown that admins often have to edit or save the world locally first and then upload the updated .db and .fwl files back to the server.
That means if you recently changed a world modifier and do not see it on the dedicated server, double-check that you uploaded the most recent pair of world files after saving the modified world locally.
When it makes sense to move from PC hosting to paid hosting #
A local PC-hosted Valheim world is fine for testing or a small group, but a dedicated hosted server becomes more practical when:
- you want the world online all the time
- your friends play at different hours
- you do not want to leave your home PC running
- you want easier backups and file access
- you plan to mod the server later
That is exactly why Valheim world transfer to dedicated server is such a useful topic for players who have already invested time into a world and want to keep it going long term. It solves a real pain point right when a casual world starts becoming a real community server.
If you do not want to handle the upload, configuration, and world-file management yourself, you can also point readers to your internal Valheim hosting page here.
