A Valheim world hosted from your own game only exists while you are online. A dedicated server keeps the world running around the clock, so your friends can log in, farm and build without waiting for the host. This guide walks through everything that matters when you set one up: the startup parameters, the password rules that trip most people up, moving an existing world across, backups, mods with BepInEx and how players connect.
What a Valheim dedicated server is
Iron Gate ships a free, separate program called Valheim Dedicated Server (Steam app ID 896660). It has no graphics and no player of its own. It loads a world, listens for connections and saves the world to disk at regular intervals. Your players connect with the normal game client, exactly as they would join a friend.
You can run it on a spare PC, a VPS or a hosted game server. On a hosted server the installation and updates are done for you, and you change settings from a control panel instead of editing a start script by hand. The parameters below are the same either way.
The startup parameters
The server is configured almost entirely through command line parameters. On Windows they live in start_headless_server.bat, on Linux in start_server.sh. A typical line looks like this:
valheim_server.x86_64 -nographics -batchmode -name "Ironbeard Hall" -port 2456 -world "Midgard" -password "frost-axe-77" -public 1| Parameter | What it does |
|---|---|
-name | The server name shown in the community server list and the join screen. |
-world | The world to load. If no world with this name exists, a new one is generated with a random seed. |
-password | The password players must enter to join. |
-port | The game port, 2456 by default. The server also uses the next port up (2457) for Steam queries. |
-public | 1 lists the server in the in-game community browser, 0 hides it so only people with the address can join. |
-crossplay | Lets Xbox and Microsoft Store players join alongside Steam players. |
-savedir | Changes where worlds and the admin lists are stored. |
-saveinterval | Seconds between world saves. The default is 1800 (30 minutes). |
-backups | How many automatic backups to keep. The default is 4. |
-preset / -modifier | World modifiers, such as -preset hardcore or -modifier raids none. |
Wrap any value that contains spaces in double quotes. A missing quote is the most common reason a server starts with the wrong name, or creates a brand new world named after only the first word of your world name.
Public or private
A public server appears in the community list, which is convenient but also invites strangers to try your password. For a group of friends, -public 0 plus a shared address is usually the better choice. You can still join a private server by IP, as shown further down.
Crossplay
Adding -crossplay switches the server to the PlayFab networking backend, which Xbox and Game Pass players need. When the server starts, it prints a join code in the console. Console players cannot type an IP address, so they join by entering that code. Two things to keep in mind:
- Xbox players cannot install mods, so a crossplay server should only run mods that are purely server side.
- Player IDs in the admin, ban and permitted lists look different on a crossplay server, because players are identified per platform. Check the IDs in the in-game connection panel (F2) rather than guessing.
Password rules
Valheim is strict about passwords and simply refuses to start if they break the rules. Before you go hunting through logs, check these:
- The password must be at least 5 characters long.
- The password cannot appear in the server name. A server called
Vikingswith the passwordVikingsorVikingwill not start. - Avoid using the world name as the password too. It is the first thing people guess.
- Stick to letters, numbers and simple symbols such as hyphens. Quotes and some special characters break the command line.
A passphrase of two or three words with a number, like frost-axe-77, is easy to share with friends and hard to guess.
Moving an existing world to the server
If you already have a world from playing with friends, you do not need to start over. A Valheim world is two files with the same name:
Midgard.fwlholds the world metadata, including the name and seed.Midgard.dbholds everything that has changed: your buildings, chests, terrain edits and explored areas.
You need both. On Windows, local worlds are stored here:
%USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_localPaste that path into the File Explorer address bar to open it. On Linux the equivalent is ~/.config/unity3d/IronGate/Valheim/worlds_local.
Cloud saves
If the world was created with Steam Cloud saving enabled, it will not be in worlds_local. Open Valheim, go to the world selection screen, select the world and use the option to move it to local storage. The two files then appear in the folder above.
Uploading the world
- Stop the dedicated server first. If it is running, it will overwrite your upload with its own copy on the next save.
- Copy
Midgard.fwlandMidgard.dbinto the server'sworlds_localfolder. On a hosted server, use the file manager in the control panel. - Set
-worldto exactly the file name without the extension, in this exampleMidgard. It is case sensitive on Linux. - Start the server and check the console. You should see it load the world rather than generate a new one.
Characters are stored separately on each player's own PC, so nobody loses their gear or skills when the world moves.
Backups
Valheim keeps a few automatic backups on its own. Every save also leaves the previous version as .db.old and .fwl.old, and the server writes timestamped copies based on these settings:
-saveinterval 1800 -backups 4 -backupshort 7200 -backuplong 43200That means: save every 30 minutes, keep 4 backups, take the first one after 2 hours and later ones every 12 hours. For an active group, a shorter -saveinterval such as 900 means less lost progress after a crash, at the cost of a brief stutter during each save on big worlds.
The built-in backups sit on the same server as the world, so they will not help if the files are deleted or corrupted together. Every so often, and always before a game update or a big mod change:
- Stop the server, or wait for a save message in the console.
- Download the
.dband.fwlfiles to your own computer. - Keep a few dated copies, not just the latest one.
Restoring a backup
Stop the server, rename the backup files so they match your world name exactly (for example Midgard.db and Midgard.fwl) and put them in worlds_local, replacing the current files. Start the server again and the world is back to that point.
Admins, bans and whitelists
Three text files sit next to the worlds folder:
adminlist.txt- players who can use admin commands such askick,banandsavein the in-game console.bannedlist.txt- players who are blocked from joining.permittedlist.txt- if this has any entries, only those players can join, even with the right password.
Add one player ID per line. For Steam players this is the 17 digit SteamID64. Restart the server after editing these files. Admins open the console with F5, which needs the -console launch option set on their game in Steam.
Mods with BepInEx
Most Valheim mods are built on BepInEx, a mod loader. The standard package is BepInExPack_Valheim on Thunderstore, which comes preconfigured for the game.
- Install BepInEx on the server. It adds a
BepInExfolder and a start script that loads it. On a hosted server, this is usually done through the panel rather than a manual upload. - Start the server once so BepInEx creates its folders, then stop it.
- Put each mod's
.dllfile inBepInEx/plugins. - Start the server again. Most mods create a config file in
BepInEx/configthat you can edit.
Server side and client side mods
This is where most modded servers go wrong. Some mods only need to be on the server, but many, especially anything that adds items, creatures or building pieces, must be installed on every player's game with the same version. A mismatch usually shows up as players failing to connect or items disappearing. Tips that save a lot of trouble:
- Share a mod list with exact version numbers, or a Thunderstore profile code, with your players.
- Add mods one or two at a time and test, so you know which one causes a problem.
- Back up the world before adding or removing a mod that adds content. Removing such a mod can delete the items and pieces it added.
- After a Valheim update, wait for mod authors to catch up before updating a modded server.
Joining by IP
The community list can be slow and does not show private servers, so joining by address is the most reliable option:
- In Valheim, choose Start Game, select your character and open the Join Game tab.
- Click Join IP.
- Enter the address and game port, for example
203.0.113.10:2456. - Enter the server password when asked.
On Zettako you can use a free yourserver.zettako.app subdomain, or your own domain, instead of a raw IP, which is easier to remember and share. If you see "Failed to connect", check that the server has fully started (the console shows the world loaded), that you are using the game port and not the query port, and that your game and the server are on the same Valheim version.
Hosting it on Zettako
A Zettako Valheim server is ready the moment you order. You set the name, world, password and other options from the control panel, update the game with one click, manage mods and edit config files without touching a command line. Every server includes DDoS protection, and memory limits are enforced proactively so a big base does not get your server killed mid raid. Premium plans add faster processing power and DDR5 memory for large, heavily built worlds. If you get stuck moving a world or setting up mods, our support team is available 24/7.