Valheim Dedicated Server: Hardware Requirements and Server Config Tuning

Valheim’s dedicated server is one of the least demanding game servers you can host, but it has one catch: it relies almost entirely on a single CPU core. A 10-player Valheim world runs comfortably on a modest 2-core VPS, while a heavily modded server with 20+ players needs a faster clock speed than a bigger RAM pool. This guide covers the exact hardware you need and the configuration settings that keep a server stable for months.

If you are comparing hosting options for Valheim or any other game title, you can compare dedicated server plans side by side on our comparison table — the spec requirements below will tell you exactly which tier you need.

Minimum and Recommended Hardware

Players	CPU	RAM	Storage	Bandwidth
2–5 (small group)	2 cores @ 2.5 GHz+	2 GB	5 GB SSD	20 Mbps
5–10 (standard)	2 cores @ 3.0 GHz+	4 GB	10 GB SSD	50 Mbps
10–20 (community)	4 cores @ 3.5 GHz+	8 GB	20 GB SSD	100 Mbps
20+ (modded)	6+ cores, high boost clock	12–16 GB	40 GB NVMe	200 Mbps

Valheim’s world saves are small — a heavily explored world rarely exceeds 1 GB — but modpacks, backups, and log growth add up fast. SSD is non-negotiable: the server streams terrain and structure data from disk constantly, and slow storage causes the ghost-sailing rubber-banding players complain about.

Installing the Valheim Dedicated Server

The official Linux dedicated server is distributed through SteamCMD. Installation takes about five minutes:

Install SteamCMD: apt install steamcmd (Debian/Ubuntu) or download the binary from Valve
Create a dedicated user: useradd -m -s /bin/bash valheim
Install the server: steamcmd +login anonymous +force_install_dir /home/valheim/server +app_update 896660 validate +quit
Run the server binary from /home/valheim/server/ — the executable is valheim_server.x86_64

Set the server to run under systemd so it restarts automatically after crashes or reboots. A simple Restart=on-failure directive with a 10-second restart delay is enough for a small community server.

Server Configuration Essentials

Valheim reads startup arguments (or a start_server.sh script) rather than a single config file. The settings that matter:

-name — the server name shown in the browser list
-password — 6+ characters; Valheim rejects short passwords
-world — the world name; changing it creates a new world, so pick once and keep it
-crossplay — enable to let Game Pass and Steam players join the same server
-public 1 — appear in the community list; set 0 for a private group
-savedir — point saves at a dedicated directory so backups are trivial

Tuning for Long-Term Stability

Save interval: Valheim autosaves every 30 minutes by default. For a busy server, script a manual save before shutdown using the in-game console or a watchdog that sends the save command.
Backups: copy the savedir world files (.db and .fwl) to a second location hourly — a corrupted world file is the most common cause of a dead server.
RAM headroom: the server uses 1.5–3 GB at rest but spikes during world saves and large base loads. Keep 1–2 GB of headroom above your peak usage.
CPU governor: on Linux, set the CPU governor to performance rather than ondemand — Valheim’s single-threaded simulation benefits from sustained boost clocks.

Monitoring and Backups

A Valheim server can run for weeks without attention, but two failures will kill it: a full disk and a corrupted world save. Set up a minimal monitoring loop so you hear about problems before players do.

Disk usage: a cron job that alerts at 80% capacity prevents the save-to-full-disk failure that corrupts worlds.
Process check: a watchdog that restarts the server binary if it exits, separate from systemd’s restart policy.
World backups: rsync the .db and .fwl pair to a second disk or object storage every hour; keep 24 hourly copies plus 7 daily copies.
Player log review: check the log for repeated join failures — usually a password typo or a banned IP range, not a server fault.

Troubleshooting Common Problems

Issue	Cause	Fix
Server not visible in browser	`-public 0` or firewall blocking UDP 2456–2458	Set `-public 1`; open UDP 2456–2458
Rubber-banding / ghost sailing	High latency or slow disk	Move to SSD; choose a host closer to players
High RAM usage over time	Memory leak in older builds; large worlds	Restart weekly; update the server binary
World resets to an old state	Corrupted or missing `.fwl` file	Restore from the most recent backup pair

For a group of friends, a 2-core / 4 GB plan is plenty and costs very little. For a public community server with mods, prioritize single-core clock speed over core count, keep 8+ GB of RAM, and automate backups from day one. See the full specs and pricing on our dedicated server comparison page to match your player count to the right plan.

Ready to launch? Check current dedicated server deals and availability: → Compare dedicated plans here