Valheim Server Requirements Calculator

Valheim Dedicated Server Requirements

Iron Gate's published minimums are very low: a quad-core CPU, 2 GB of RAM, and just 2 GB of free storage. Those numbers are technically true for a brand-new world with one or two players, but they are misleading for a server you actually intend to use. In practice, even a small world (around 25 MB on disk) with a couple of players idles at roughly 2-3 GB of RAM, and that figure climbs steadily as the world is explored and built up. Note that Iron Gate's own spec sheet lists 8 GB as the recommended RAM, which is the more realistic target.

RAM

For a vanilla server, the realistic guidance is:

• 2-4 players: 4 GB is comfortable (6 GB if you enable crossplay).
• 5-10 players: 8 GB is the sweet spot. More players means more spread-out exploration, which loads more world chunks (zones) into memory simultaneously.
• Lightly modded: 8-10 GB.
• Heavy modpacks / overhauls: 12-16 GB.

The single most underestimated factor is world age. A fresh world may sit at 3-4 GB, but the same world after weeks of terraforming, large bases, tamed animals, and dropped items can consume substantially more, because the server tracks every terrain modification and persistent entity. Size for where your world will be in a few months, not day one.

CPU

This is where Valheim is unusual. The core server simulation is effectively single-threaded, so clock speed beats core count. Two cores at 5 GHz will outperform six cores at 2.5 GHz once several players are online and combat or large bases are being simulated. A modern quad-core at 3.2 GHz or higher is the recommended target; 2 fast cores is a workable floor. Extra cores mainly help the host OS, autosave I/O, and running a second world. The application is headless, so no GPU is required. Be wary of cheap, heavily-oversubscribed shared vCPUs, which often deliver far less sustained single-thread performance than their advertised clock suggests.

Storage

Storage needs are small. The server install is roughly 1-2 GB, and world database files are typically 25-150 MB even for well-developed worlds. Adding automatic backups and logs, about 5 GB total is plenty for most setups (modded worlds and many backups can use more). Storage barely scales with player count. What matters most is disk speed: Valheim autosaves frequently (every 20 minutes by default, plus on shutdown), and a slow HDD can cause a brief hitch on every save. Use an SSD or NVMe.

Network

Bandwidth demands are modest: budget roughly 5-7 GB of egress per active player per month at default data-rate settings, scaling with player movement and the server's configured send rate. A 100 Mbit/s link is the practical minimum; 1 Gbps is what most hosts recommend. Latency matters more than throughput for how the game feels, so the biggest network decision is picking a server location physically close to your players. The dedicated server uses UDP ports 2456-2458 by default (2456 game, 2457 query, plus crossplay), which must be open/forwarded.

Player cap

The server is hard-capped at 10 concurrent players by default. Raising it requires a mod, and pushing beyond 10 stresses the single-threaded simulation more than the hardware, so expect desync at high counts regardless of specs.

Optimizing a Valheim Server

Because the simulation is single-threaded, you can't brute-force performance with more cores. Focus instead on these concrete levers:

• Pick the fastest available core, not the most cores. When comparing host plans, a higher base clock / better single-thread benchmark beats a higher core count. Dedicated or unshared vCPUs avoid the "noisy neighbor" problem that throttles busy servers.
• Tune the data rate. The launch flag and config control how aggressively the server pushes updates to clients. A higher dataRate (e.g. raising the per-client send rate) reduces desync and rubber-banding at the cost of more bandwidth, useful if players see entities lagging; lower it to save bandwidth on constrained links.
• Manage the world, not just the hardware. The biggest performance and memory drains are massive terraforming, sprawling bases, large numbers of dropped items, and many tamed animals or active spawners. Encourage players to pick up loose items, avoid excessive ground-flattening, and contain breeding animals. Periodically clearing abandoned structures keeps the world database lean.
• Keep autosaves on a fast disk. Frequent autosaves (every 20 minutes by default, plus on shutdown) on an HDD cause periodic hitches; an SSD/NVMe eliminates this. Don't disable autosave to fix stutter, fix the disk.
• Be deliberate with crossplay. Enabling Steam + Xbox crossplay (the -crossplay flag) adds RAM and CPU overhead via PlayFab routing. If all your players are on Steam, leaving it off is leaner and uses more reliable direct connections.
• Right-size RAM with headroom. Allocate enough that the process never swaps, but giving a 4-player vanilla server 32 GB does nothing, the engine won't use it. Spend the budget on clock speed and disk speed instead.
• Mod hygiene. Modded servers are the most common source of memory leaks and crashes. Add plugins one at a time, watch RAM over a few days, and keep backups before updating any mod or the game. Worldgen/overhaul mods can permanently bake heavier data into your save.
• Keep the game build updated. Server and all client builds must match (modded servers also need matching mod versions), and Iron Gate periodically ships networking/performance improvements.

What to Look For in a Valheim Host

Whether you self-host or rent, the same criteria separate a smooth Valheim server from a laggy one. Use these as a neutral checklist rather than chasing the cheapest plan.

• Strong single-thread CPU performance. This is the number-one factor for Valheim. Look for high clock speeds and, ideally, dedicated or unshared CPU resources. Plans that advertise many cores but oversell each one will underperform once your server is busy.
• Generous RAM headroom. Pick a plan a tier above your day-one needs so your world has room to grow over months and a misbehaving mod can't push the process into out-of-memory crashes.
• SSD/NVMe storage. Required for smooth, frequent autosaves. Avoid HDD-backed plans.
• Server location close to your players. Latency drives how the game feels far more than raw bandwidth. Choose a region near most of your group, and check the host offers locations that fit.
• DDoS protection. Public game servers are common targets; network-level mitigation prevents your server from being knocked offline.
• Easy mod and config management. If you plan to mod, look for one-click BepInEx/mod installation, FTP or SFTP file access, and an editable config so you can tune dataRate, world name, and player limit without support tickets.
• Automatic, restorable backups. Valheim worlds are precious and corruption happens. Scheduled backups you can roll back yourself are essential.
• Console/log access and crossplay support. Live console output speeds up debugging, and a crossplay toggle matters if you mix Steam and Xbox players.

If self-hosting on your own hardware, you're responsible for these yourself: a fast single-core box, an SSD, port forwarding (UDP 2456-2458), a backup routine, and a stable upload connection.

CPU note: Single-thread-bound. Valheim's server tick runs on essentially one core, so high clock speed (3.2 GHz+, ideally modern 4-5 GHz) beats core count. Two fast cores outperform six slow ones. Extra cores only help with the OS, autosave I/O, and a second world. Avoid cheap shared/oversold vCPUs.

Default player cap is 10 (raisable only via mods). Real RAM use is driven more by world age and build density than by raw player count, so a long-lived world needs more than these baselines suggest. Crossplay adds ~1-2 GB. Heavy worldgen/overhaul mods can push well past the listed tiers. Storage is small and barely scales with players, but an SSD/NVMe is strongly recommended for autosaves.