How to Set Up a Valheim Dedicated Server for a Small Community (2026)

Running a Valheim world that your friends can drop into any time, without you having to be online, is one of the best upgrades you can make to a small group playthrough. In this guide I will walk through exactly how to set up a Valheim dedicated server for a small community, from choosing between self-hosting and managed hosting, all the way through configuration, port forwarding, admin setup, crossplay, backups, and troubleshooting the connection problems that trip most people up.

By the end you will have a persistent world that 3 to 10 players can join whenever they want, with you (or whoever you delegate) holding the admin keys. I have kept the steps specific to small communities, since most existing guides are written for big public servers and overcomplicate things for a tight group of friends.

Self-Hosted vs. Hosted: Which Path Fits Your Community?

Before any installation, you need one decision: run the server on hardware you control, or rent a managed Valheim server. There is no universally right answer, but for a small community of 3 to 10 players the trade-offs are pretty clear.

Self-hosting means installing the Valheim dedicated server software on a PC, a spare machine, or a Linux box you already own. You pay nothing beyond your existing electricity and internet, and you keep total control of the world files. The catch is that the host machine needs to stay on, port forwarding has to be configured on your router, and your home upload speed directly limits how smoothly friends connect.

Managed hosting means paying a provider to run the server in a data center. You get a control panel, automated backups, a fixed IP, and a network already tuned for game traffic. You also pay a monthly fee and have slightly less direct file access.

For most small communities, I recommend trying self-hosting first if anyone in the group has a spare PC and is comfortable with router settings. If port forwarding fails or your home upload is weak, a managed Valheim server for around $10 to $15 a month is the simpler path. The rest of this guide covers the self-hosted route in detail, since that is where most of the setup work actually happens, but the configuration values apply to both.

Server Requirements for a Small Community

One of the most common questions I see on the Valheim subreddit is “how much RAM do I actually need?” The honest answer depends on your player count and how explored your world is, but for a small community the numbers are modest.

RAM is the resource that scales hardest with player count and world age. A fresh world with 3 players runs fine on 4 GB, but a heavily built-out world that has been running for months with 8 players will chew through 6 to 8 GB and start swapping if you cut it close. Allocate more RAM than you think you need.

An SSD matters more than raw disk size. Valheim constantly writes world save data, and on a mechanical hard drive that write load causes noticeable lag spikes for connected players. Any cheap SATA SSD handles it without issue.

Upload speed is the requirement most people underestimate. Download speed is irrelevant for a server, what counts is how fast your connection can push data to every connected player at once. Test your real upload speed with any speed test tool, and assume each connected player uses roughly 1 to 2 Mbps of sustained upload during active play.

For operating system, Windows 10 or 11 works fine and is the easiest path for beginners. Ubuntu Server 22.04 LTS is the most common Linux choice if you want to run the server headless on a spare box or a VPS. The same SteamCMD-based install process applies to both.

How to Set Up a Valheim Dedicated Server for a Small Community: Step-by-Step

This is the core walk-through. I am going to cover the Windows path using the Steam library tools, then note the SteamCMD alternative that works on both Windows and Linux. Follow each step in order, since later steps depend on earlier ones.

Step 1: Install the Valheim Dedicated Server Tool

The dedicated server is a separate free program from the Valheim game itself. You do not need to own Valheim twice, but you do need this tool on the machine that will act as the server.

If you already have Steam installed on the host machine, open your Steam Library, click the “Games” dropdown at the top, and select “Tools.” Scroll to “Valheim Dedicated Server,” right-click it, and install it like any other Steam entry. This downloads the server executable and the default configuration files into your Steam folder under steamapps/common/Valheim dedicated server.

If you are running on a Linux box or a VPS without the Steam desktop client, use SteamCMD instead. Download SteamCMD from the official Valve developer page, extract it, then run:

steamcmd +login anonymous +app_update 896660 validate +quit

App ID 896660 is the Valheim dedicated server. The anonymous login works because the dedicated server tool is free, so no Steam account credentials are needed on the server side.

Step 2: Edit start_headless_server.bat (or the Linux equivalent)

Once the tool is installed, locate the file named start_headless_server.bat in the install folder. On Windows, right-click it and choose Edit to open it in Notepad. This is the script that launches your server, and it is where you set the core identity of your world.

The default file contains a long command line with several flags. You need to edit the following values:

• -name — the display name shown in the server browser (e.g. “Weekend Vikings”).

• -world — the internal world save name. Use a single word, no spaces (e.g. “friends_world”).

• -password — the password every player must enter to join. Pick something non-obvious.

• -port — leave as 2456 unless you are running multiple servers on one machine.

• -public — set to 1 to list the server in the browser, or 0 for a private server only joinable by direct IP.

• -crossplay — add this flag to enable crossplay between Steam and Xbox players.

Here is an example of what the edited line should look like for a small private community with crossplay enabled:

valheim_server -nographics -batchmode -name "Weekend Vikings" -world "friends_world" -password "longboat2026" -port 2456 -public 1 -crossplay

On Linux, the equivalent script is start_server.sh, and the same flags apply. Make sure the script has execute permissions with chmod +x start_server.sh before you try to run it.

Step 3: Set Up Port Forwarding on Your Router

This is the step that breaks more setups than any other. If your router is not forwarding the right ports to your server machine, friends will never see the server in the browser and direct IP connections will time out.

Valheim uses three consecutive UDP ports based on the -port value. With the default port of 2456, you need to forward UDP 2456, UDP 2457, and UDP 2458 to the local IP address of your server machine. Only UDP is required, not TCP.

The exact menu names vary by router, but the general process is:

1. Log into your router admin panel (usually 192.168.1.1 or 10.0.0.1).

2. Find the Port Forwarding, Virtual Server, or NAT section.

3. Create three new rules, one each for UDP 2456, 2457, and 2458.

4. Point each rule at the static local IP of your server PC.

5. Save and restart the router if prompted.

Before doing this, give your server machine a static local IP so the forwarding rules do not break when the device reboots. On Windows, you can set a static IP through Network Settings, Adapter Properties, IPv4 settings. On Linux, configure it through Netplan or your distribution’s network manager.

Step 4: Open the Firewall on the Server Machine

Even with port forwarding in place, the Windows Defender Firewall or your Linux firewall will block incoming UDP traffic by default. You need an inbound rule allowing UDP 2456 through 2458.

On Windows, open Windows Defender Firewall with Advanced Security, click Inbound Rules, then New Rule. Choose Port, UDP, Specific local ports “2456-2458”, Allow the connection, and name it something like “Valheim Server.” Do this once for each profile if your server sits on a network tagged as Private.

On Ubuntu, the equivalent is a single ufw command: sudo ufw allow 2456:2458/udp. Verify with sudo ufw status afterward.

Step 5: Launch the Server and Verify It Is Running

Double-click start_headless_server.bat on Windows, or run ./start_server.sh on Linux. A console window opens and you will see log lines scrolling as the world loads. The first launch takes longer because it generates the world seed.

The server is ready when the log shows a line like “Game server connected” or similar startup-complete message. Do not close the console window, that window IS the server process. On Linux, run the script inside a tmux or screen session so it survives your SSH session disconnecting.

To verify the server is reachable from outside your network, ask a friend to open Valheim, go to the Join Game tab, and search for your server name. Alternatively, have them try connecting directly with your public IP address and port 2456. If neither works, jump down to the troubleshooting section.

Step 6: Have Players Connect

Each player opens Valheim, clicks Start Game, then Join Game, and either finds your server in the community list or adds it manually by IP. They will be prompted for the password you set in the script. That password is the only barrier between the public internet and your world, so keep it private to your community.

If your server is set to -public 0, it will never appear in the browser. Players must use Add Server, enter your public IP and port, then enter the password. This is the right choice for a small private group that does not want randoms joining.

Admin Setup and Permission Management

Once your server is running, you want to lock down who can admin it and who can join. Valheim handles this with three text files in the server’s admin folder, which is created on first launch.

Locating the Admin Files

On a Windows install, the files live in C:UsersYourUserAppDataLocalLowIronGateValheim by default. On Linux they sit under ~/.config/unity3d/IronGate/Valheim. Look for a subfolder named after your world, and inside or beside it you will find three plain text files: adminlist.txt, permittedlist.txt, and bannedlist.txt.

Making Yourself an Admin

To make yourself or a friend an admin, you need each player’s Steam ID (or PlayFab ID for Xbox crossplay players). Steam IDs are the long 17-digit numbers, not usernames. The easiest way to grab a Steam ID is to use a site like steamid.io, or run the in-game command players as an existing admin to list connected player IDs.

Add each Steam ID, one per line, to adminlist.txt, save the file, and restart the server. The listed players will now have access to admin commands like kick, ban, banned, unban, permitted, and imacheater for spawning.

The permittedlist.txt file is for whitelisting specific players when you have a private server. The bannedlist.txt file does the opposite. For a small friends-only community, you may never need to touch bannedlist, but it is there if someone proves disruptive.

Useful Admin Commands for Small Servers

The most commonly used commands for a small group are kick [name/ID] for removing a stuck or AFK player, banned to view the current ban list, save to force a world save before a restart, and info to print server details. Press F5 in game to open the console, then prefix commands with nothing on a dedicated server, you are already talking to the server console.

If the F5 console does not open in game, you may need to launch Valheim with the -console launch option in Steam. Right-click Valheim in your library, Properties, Launch Options, and add -console.

Crossplay, World Modifiers, and Small-Community Optimizations

This is the section most guides skip, and it is where the small-community experience really gets tuned. None of the top competitors cover small-community optimization tips, which is exactly why this section exists.

Enabling Crossplay Between Steam and Xbox

Crossplay lets Steam and Xbox Game Pass players share the same world. To enable it, just add the -crossplay flag to your server launch script as shown in Step 2. No extra configuration is needed.

The catch is that Xbox players authenticate through PlayFab, not Steam, so their IDs look different in adminlist.txt. When you run the players command as an admin, Xbox players show up with a different ID format. Copy that exact format into adminlist to grant admin rights to Xbox players.

If crossplay is not working, the most common cause is the server not actually being launched with the -crossplay flag, or the flag being added after the world was already created. Restart the server cleanly with the flag in place from launch.

Setting World Modifiers for Casual Co-op

World modifiers let you tune combat, resource rates, and other difficulty knobs without mods. From inside the game, an admin can open the world modifiers menu by pressing F5 and typing modifiers, or by using the in-game “World Modifiers” option on the pause menu in newer Valheim versions.

For a small community of friends who want to focus on building and exploring rather than brutal combat, the most popular tweaks are:

• Combat: Easy or Hard: Very Hard depending on group skill.

• Death penalty: Casual to keep inventory on death, huge for keeping the group motivated.

• Resources: 1.5x or 2x for groups with limited play time.

• Raids: Off if base defense events are causing drama, or leave on for tension.

• Portal iron/tin: On if your group hates the ore-smuggling grind.

The preset options include “Casual,” “Easy,” “Hard,” “Hardcore,” “Hammer,” and “Immersive.” Casual is a great starting point for a brand-new small group, then tune individual sliders from there once you see how the group plays.

Quality-of-Life Tips for a Tight Group

A few small-community conventions go a long way toward keeping the peace over a long playthrough. The Reddit community consistently recommends disabling fire hazards if your group has anyone prone to accidental base fires, since one careless campfire can torch hours of shared building work.

Set up a shared storage hub near spawn with named chests for wood, stone, metal, food, and valuables. Give each player a personal chest with their name on it for private items. This reduces the “who took my iron” arguments that sink small groups.

Use a shared online doc or Discord channel to coordinate big building projects and boss fight nights. A dedicated server means the world persists even when nobody is online, so players can drop in solo to grind resources between group sessions.

Backups and World Management

World saves are the heart of your community’s shared progress, and losing one to a crash or a bad mod is devastating. Backups are not optional for any server you care about.

Where World Saves Live

The same admin folder mentioned earlier holds the world files. Look for files named friends_world.db and friends_world.fwl (using whatever world name you set in the script). The .db file is the world database, the .fwl file holds metadata. Both are required to restore a world.

Valheim also auto-saves on a regular interval controlled by the saveinterval flag, which defaults to 1800 seconds (30 minutes). You can lower this if your group does high-stakes building, or raise it if you want less disk write load.

A Simple Backup Strategy

For a small community, a simple strategy is enough. Once a day, stop the server cleanly with the save command, copy the .db and .fwl files to a dated folder, then restart. Keep at least the last seven daily backups plus a couple of weekly snapshots.

On Windows, a small PowerShell or batch script scheduled with Task Scheduler can do this automatically. On Linux, a cron job with rsync to a remote location, or even just a timestamped copy to a backup folder, covers it. The key is making it automatic so you do not forget.

To restore a backup, stop the server, drop the backed-up .db and .fwl files back into the world folder (overwriting or renaming the current ones first), and restart. The world will load at the state captured in that save.

Troubleshooting Common Connection Issues

This is the section I wish existed when I first set up my own server. Connection problems are the top complaint on the Valheim subreddit and the Steam community forums, and almost every issue traces back to one of a handful of causes.

Server Not Showing Up in the Browser

If friends cannot find your server in the Join Game community list, work through this checklist in order:

1. Confirm the server is actually running and the console shows “Game server connected.”

2. Verify -public 1 is set in the launch script (or the equivalent checkbox in a hosted panel).

3. Wait 5 to 10 minutes after launch. New servers take several minutes to register with the community list.

4. Check that UDP 2456, 2457, and 2458 are forwarded on the router AND open in the host firewall.

5. Try connecting directly with the public IP and port 2456. Direct IP rules out browser indexing as the problem.

If direct IP works but the browser does not, the server is reachable but not being indexed. This is usually temporary and resolves within 30 minutes. Tell friends to use Add Server with your IP in the meantime.

Connection Timeouts from Outside Your Network

If you can connect from a device on the same network but friends elsewhere time out, the problem is almost always port forwarding or firewall. Re-check that the local IP in your forwarding rule matches the server’s actual current local IP, especially if you skipped setting a static IP earlier.

Some ISPs use Carrier-Grade NAT (CGNAT), which means you do not have a real public IP and port forwarding on your router does nothing. If your public IP starts with 100.64.x.x, you are behind CGNAT and self-hosting will not work without a VPN tunnel or a hosted server. This is increasingly common on cellular and some fiber ISPs.

Crossplay Players Cannot Join

If Steam players connect fine but Xbox players fail, confirm the -crossplay flag is in the launch script and the server was restarted after adding it. Also check that the server is publicly listed, since Xbox players find servers through the community browser rather than direct IP.

If Xbox players see the server but get rejected at the password screen, double-check the password has no special characters that the Xbox keyboard handles oddly. Simple alphanumeric passwords avoid this entirely.

Lag and Rubberbanding

If players experience heavy rubberbanding or delayed interactions, the host machine is overloaded or the upload bandwidth is saturated. Check Task Manager or htop for RAM and CPU usage. If RAM is maxed, allocate more or reduce the player cap.

If the host has spare capacity, the issue is likely your home upload speed. Run a speed test during peak evening hours, since ISPs often throttle upload at night. If sustained upload is below 5 Mbps, a managed server in a data center will feel dramatically smoother for everyone.

World Not Loading or Save Corruption

If the server crashes on startup or loads a fresh world instead of your existing one, the world save files are either missing from the expected location or corrupted. Restore from your most recent backup (see the Backups section). If you have no backup, there is unfortunately no way to recover a fully corrupted save, which is why the daily backup habit matters.

FAQs

Conclusion

You now have the full picture on how to set up a Valheim dedicated server for a small community, from choosing self-hosted versus managed hosting, through SteamCMD installation, start_headless_server.bat configuration, UDP port forwarding, admin permissions, crossplay, world modifiers, backups, and the troubleshooting steps that solve most connection problems.

For a small group of friends, the payoff is huge: a persistent Viking world anyone can drop into, with you in full control of the rules, mods, and player list. Get the server running, get your first backup done, then invite the crew and set sail.