Valheim Dedicated Server Setup: Hardware Requirements and Configuration Guide

Valheim is a rare case in the game-server world: its dedicated server is lightweight compared to Palworld or ARK, but it has quirks that punish the wrong hardware choices. The game runs on a custom Unity-based engine with a simulation loop that is surprisingly sensitive to single-core CPU speed, and its world saves can produce stutter spikes on slow storage. This guide covers the hardware requirements for 2–10 players, step-by-step server setup on Linux, the configuration options that affect performance, and the common mistakes that make Valheim servers lag even when the hardware looks adequate on paper.

If you are shopping for a dedicated server to run Valheim, compare configurations for your target player count before committing — the difference between a cheap low-clock CPU and a modern high-clock chip is immediately visible in Valheim’s tick rate.

Valheim Server Hardware Requirements

Valheim’s official minimum spec is modest: a 2.6 GHz dual-core CPU and 4 GB of RAM. In practice, those numbers are fine for a 2–3 player server with minimal building, but they fall apart quickly as the world accumulates structures, tamed animals, and explored terrain.

Player Count	CPU	RAM	Storage	Notes
2–4 players	2-core, 3.0+ GHz	4–6 GB	NVMe, 10 GB+	Fine for small bases; vanilla settings
4–6 players	4-core, 3.5+ GHz	6–8 GB	NVMe, 20 GB+	Moderate building; may need save interval tuning
6–10 players	4–6 core, 4.0+ GHz	8–12 GB	NVMe, 40 GB+	Heavy building; watch auto-save spikes

The key insight: Valheim is single-thread bound on the main simulation loop. The ZDO (Zombie Data Object) system that tracks every world object runs on one thread, and when that thread saturates, the server starts dropping ticks regardless of how many spare cores you have. This makes clock speed and IPC the dominant hardware factors — a 4-core CPU at 4.5 GHz will outperform an 8-core CPU at 2.8 GHz for Valheim every time.

Why NVMe Storage Matters for Valheim

Valheim’s world save system writes the entire world state to disk on each autosave. On a large world with extensive building, these saves can be 50–100 MB each. With a SATA SSD, a save of that size can take 2–4 seconds, during which the server simulation pauses — producing a visible freeze for all connected players. With an NVMe drive, the same save completes in under a second, and the freeze is barely perceptible. This is one of the few game-server workloads where the NVMe-vs-SATA difference is directly observable by players.

Installing the Valheim Dedicated Server on Linux

The Valheim dedicated server is distributed through SteamCMD. Here is the full installation process on Ubuntu 22.04 or 24.04 LTS:

Step 1: Install SteamCMD and Dependencies

sudo apt update && sudo apt upgrade -y
sudo apt install -y steamcmd lib32gcc-s1

# Create a dedicated user for the server
sudo useradd -m -s /bin/bash valheim
sudo passwd -l valheim

Step 2: Install the Valheim Server Files

sudo -u valheim -s
cd /home/valheim
steamcmd +login anonymous +force_install_dir /home/valheim/server +app_update 896660 validate +quit

Step 3: Configure the Server

Create a startup script at /home/valheim/start_server.sh:

#!/bin/bash
export templdpath=$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=/home/valheim/server/linux64:$LD_LIBRARY_PATH
export SteamAppId=892970

/home/valheim/server/valheim_server.x86_64 \
  -name "My Valheim Server" \
  -port 2456 \
  -world "MyWorld" \
  -password "YourPassword" \
  -savedir "/home/valheim/data" \
  -public 1 \
  -crossplay

export LD_LIBRARY_PATH=$templdpath

Make it executable: chmod +x /home/valheim/start_server.sh

Step 4: Set Up systemd Service for Auto-Restart

Create /etc/systemd/system/valheim-server.service:

[Unit]
Description=Valheim Dedicated Server
After=network.target

[Service]
Type=simple
User=valheim
WorkingDirectory=/home/valheim/server
ExecStart=/home/valheim/start_server.sh
Restart=on-failure
RestartSec=10
KillSignal=SIGINT

[Install]
WantedBy=multi-user.target

sudo systemctl daemon-reload
sudo systemctl enable valheim-server
sudo systemctl start valheim-server

Step 5: Open Firewall Ports

sudo ufw allow 2456/udp
sudo ufw allow 2457/udp
sudo ufw allow 2458/udp
sudo ufw reload

Valheim uses three consecutive UDP ports: 2456 for gameplay, 2457 for Steam query, and 2458 for the next player connection slot. If you configure a different base port, increment the range accordingly.

Configuration Tuning for Performance

Valheim’s server configuration is minimal compared to other games, but a few settings directly affect performance:

• Save interval: The default 1800 seconds (30 minutes) is reasonable. Lowering it increases save-related stutter. Raising it to 3600 seconds reduces stutter but risks more data loss on a crash.
• World backups: Valheim saves to http://savedir/ with .db and .fwl files. Set up a cron job to copy these off-box hourly. A corrupted world save on a 500-hour Valheim world is devastating.
• Crossplay: The -crossplay flag enables both Steam and Xbox/Game Pass clients to connect. It adds a small amount of CPU overhead for protocol translation. If you only need Steam players, omit this flag.
• Public vs. private: Setting -public 1 makes the server visible in the community browser, which adds a small query-handling overhead. For private servers, set -public 0.

Common Performance Issues and Fixes

Save stutter: The most common Valheim performance complaint. The server pauses during world saves. Fix: use NVMe storage, and increase the save interval to 3600 seconds. If the stutter persists, check whether the server is running out of RAM — Valheim on a memory-constrained system will page during saves.

Late-game lag: As the world grows, the ZDO thread saturates. Fix: reduce the number of tamed animals, limit terraforming (which creates many ZDOs), and avoid building massive structures with thousands of instances. There is no server-side setting that fixes this — it is a game engine limitation.

Connection refused: Usually a firewall or port-forwarding issue. Verify with ss -ulpn | grep 2456 that the server is listening on 0.0.0.0, and check that the three UDP ports are all open.

High CPU usage at idle: Valheim’s server does not idle well — it continues running the full simulation even with no players online. If you are running a dedicated box for multiple games, allocate Valheim to specific cores using CPU pinning to prevent it from competing with other game instances.

Monitoring Your Valheim Server

The server logs to /home/valheim/data/valheim_server_Data/output_log.txt. Watch for lines containing “ZDO” — they indicate how many world objects the server is tracking. A healthy server for 6–10 players should stay under 50,000 ZDOs. Above 100,000 ZDOs, expect tick-rate degradation regardless of hardware.

For a quick health check, connect to the server and run info in the in-game console (F5). The displayed FPS is the server’s tick rate, not your client’s. A stable 20+ FPS means the server is healthy. Below 15 FPS, players will notice rubber-banding and delayed interactions.

Summary: What to Rent for Valheim

For a 2–6 player Valheim server, a 4-core CPU with boost clocks above 3.5 GHz, 6–8 GB of RAM, and NVMe storage is sufficient. For 6–10 players, step up to a 6-core CPU at 4.0+ GHz and 12 GB of RAM. Avoid low-clock server CPUs regardless of core count — Valheim’s single-threaded simulation will not use them effectively. Prioritize NVMe storage over raw CPU core count, because save stutter is the most visible problem players experience.

If you are planning to host Valheim alongside other game servers on the same machine, give it dedicated CPU cores and its own NVMe partition. The game does not share resources gracefully. For hardware comparisons across providers, check dedicated server configurations for Valheim before you rent.