Valheim has no published numeric minimum for dedicated-server CPU, RAM, or storage. Iron Gate documents how to run the server, its network modes, save settings, and software dependencies, but it does not promise a hardware floor. A practical starting point reported by the community is a Linux VPS with 2 vCPU and 4 GB of RAM. Treat that as a sizing hypothesis, not an official requirement: measure a busy world and scale when CPU utilization, memory pressure, swapping, or disk space becomes a problem.
Storage must cover more than the initial server download. World files, logs, Docker data, and every retained backup consume space. The sections below explain what is known, how to choose a host, which packages and ports are needed, and how to tell when your server needs more capacity.
What are the official Valheim dedicated-server requirements?
Iron Gate has not published a numeric minimum for CPU cores, RAM, disk capacity, or player count for a dedicated server. Its documentation is authoritative for supported setup behavior, but it is not a hardware-sizing guarantee. Any specification presented as “the official minimum” is therefore overstated.
The most defensible baseline is the informal community consensus of 2 vCPU and 4 GB RAM on a Linux VPS. That figure comes from a community FAQ rather than Iron Gate, and it may be insufficient for an old, heavily built, modded, or unusually busy world. Start there only if you can monitor the machine and increase resources without rebuilding the world.
Baseline versus guaranteed capacity
- Officially established: no numeric CPU, RAM, or storage minimum is published.
- Practical starting point: 2 vCPU and 4 GB RAM for a Linux VPS, as informal community guidance.
- What changes the result: world age and size, construction density, mods, simultaneous activity, backup retention, and the quality of the host’s CPU.
- Community player guidance: a 10-player cap is commonly reported, but it should not be treated as an officially confirmed way to exceed or alter the supported limit.
For a self-hosted machine, compare the same factors you would compare on a VPS: single-thread CPU performance, available memory and swap headroom, SSD space, Linux library compatibility, port-forwarding capability, and the amount of administration you are willing to do.
How much RAM does a Valheim dedicated server need?
Use 4 GB as a starting allocation for a small Linux VPS, then watch actual memory use during the busiest period your players create. There is no published Iron Gate number, so neither 4 GB nor any larger figure can be presented as a universal requirement.
What consumes memory?
The running game process, loaded world state, connected players, operating-system services, logging, container overhead, and any mods all compete for memory. A world with extensive construction or several players active in different areas can behave differently from a new test world with one player.
How to tell when RAM is inadequate
- Physical memory remains nearly full while players are active.
- The operating system begins swapping frequently; swapping can keep a process alive but usually adds latency.
- The server process is terminated by the operating system or the container runtime.
- Save operations and player actions become erratic at the same time memory pressure rises.
Record memory use during exploration, building, combat, and a save cycle rather than checking only while the world is idle. Leave headroom for the operating system and backup process. If the host regularly swaps or runs out of memory, increase RAM before attempting to solve the problem with faster storage.
What CPU does a Valheim dedicated server need?
The community baseline is 2 vCPU, but the important characteristic is responsive per-core performance rather than a large virtual-core count alone. Iron Gate does not publish a CPU model, clock speed, or core minimum.
Why single-thread performance matters
Game-server simulation commonly places significant work on one or a few active threads. A host advertising many slow or oversubscribed vCPUs can therefore perform worse than a host with fewer, faster cores. Compare the provider’s CPU generation and shared-resource policy, not just the number printed in the plan name.
Signs that CPU is the bottleneck
- One core stays saturated while other cores are lightly used.
- Tick or simulation delays appear when several players load areas or perform busy-building activities.
- Latency rises even though RAM is available and the disk is not full.
- Reducing simultaneous activity helps immediately, while adding memory does not.
On a self-hosted machine, avoid running heavy unrelated workloads on the same cores. On a VPS, investigate noisy-neighbor or CPU-steal metrics if the provider exposes them. Scaling from 2 to more vCPUs may help only when the server and its workload can use them; a faster CPU tier can be the better upgrade.
How much storage should I reserve?
No official storage minimum exists. Reserve capacity for the server installation, world saves, logs, Docker images and volumes when applicable, and multiple generations of backups. The correct amount depends on how large the world becomes and how long you retain backups, so a single universal gigabyte figure would be misleading.
What belongs in the storage budget?
- Server files: the downloaded dedicated-server installation and any updates.
- World data: save files for every world you keep on the host.
- Logs: retained console or service logs, especially if rotation is not configured.
- Container data: Docker images, writable layers, and the volume that holds saves.
- Backups: every automatic and manual copy that you choose to retain.
Use an SSD where possible for predictable save and load times, but capacity and free-space monitoring matter more than buying a large drive blindly. Keep working space available; a disk that is technically large enough but nearly full can prevent saves, updates, or backup creation.
What do Iron Gate’s default save and backup settings mean?
Iron Gate documents these defaults as configuration values, not as storage requirements:
| Setting | Default | Storage implication |
|---|---|---|
| Save interval | -saveinterval 1800 (1,800 seconds) |
Creates a save every 30 minutes; more frequent saves can create more write activity. |
| Automatic backups | -backups 4 |
Keeps four automatic backup generations unless you change the value. |
| Short-backup interval | -backupshort 7200 (7,200 seconds) |
Runs the short backup cycle every two hours. |
| Long-backup interval | -backuplong 43200 (43,200 seconds) |
Runs the long backup cycle every 12 hours. |
The size of each world copy is not fixed in the documentation. Check the actual save directory, multiply by the number of generations you retain, and add room for logs and updates. An external drive can be useful for backup copies, but its required capacity depends on your world size and retention policy rather than on a standard Valheim number.
Which operating systems and software libraries are required?
Windows and Linux are the documented native environments, and Docker is an option when the host meets its library requirements. Choose the route that matches your administration skills and your ability to keep packages and backups current.
| Deployment route | Documented requirement or entry point | Important caveat |
|---|---|---|
| Windows native | Run start_headless_server.bat from the server installation. |
You must handle Windows firewall rules, port forwarding where required, updates, and backup storage. |
| Linux native | Run start_server.sh; install libatomic1, libpulse-dev, and libpulse0. |
Package names and availability can vary by distribution; install the matching versions before launch. |
| Docker | Use a container host meeting at least GLIBC_2.29 and GLIBCXX_3.4.26. |
Map a persistent volume for saves and account for image, volume, and log usage. |
These are runtime prerequisites, not performance guarantees. A machine can satisfy every library check and still need more CPU, memory, or disk once players and mods are active.
How do I configure networking for a dedicated server?
Steam-backend hosting uses the default port range 2456-2457 and requires that the selected range be reachable from the internet. Crossplay uses a relay, so outside port forwarding is not required, although the port still distinguishes servers sharing the same public IP.
Steam backend
- Choose the server’s port in the launch configuration, retaining the documented two-port range unless you have a reason to change it.
- Allow the range through the host firewall.
- If the server is behind a home router, forward the selected ports to the server’s local address.
- Verify that the public address and ports are reachable from outside the local network before inviting players.
Crossplay backend
- Enable crossplay in the server configuration.
- Allow the server process through the local firewall.
- Do not assume that a router port-forward rule is necessary; relay traffic is designed to avoid outside forwarding.
- Test joining from the target platforms, because a relay removes one networking dependency but does not fix a blocked process, incorrect world path, or failed launch.
Document the chosen port and backend for anyone administering the machine. A change from Steam backend to Crossplay can alter the connectivity test even when the server files and hardware stay the same.
Can Xbox players host or join a Valheim dedicated server?
Xbox consoles can join a dedicated server when crossplay is enabled, but an Xbox console cannot host a dedicated server itself. Microsoft Store users launch StartHeadlessServer.bat from the installed Server folder. Hosting therefore requires a supported Windows or Linux computer, VPS, or managed service rather than the console.
Before choosing a backend, list every platform that must connect. Crossplay is the relevant mode for mixed-platform groups; Steam-only groups can use the Steam backend and its normal reachability requirements.
How should I choose between self-hosting, a VPS, and managed hosting?
Self-hosting offers control but makes you responsible for hardware, power, firewall rules, updates, backups, and troubleshooting. A VPS removes the need to own a machine but still leaves operating-system maintenance and monitoring to you. Managed hosting trades some control for provider administration and support.
| Decision factor | Self-hosted machine | Linux VPS | Managed service |
|---|---|---|---|
| Hardware sizing | You choose and can upgrade physical parts. | Start around the informal 2-vCPU/4-GB baseline, then resize. | Compare the provider’s stated CPU, RAM, and slot policy. |
| Networking | Router forwarding may be required for Steam backend. | Usually controlled through provider firewall and public networking. | Provider handles much of the network layer; verify backend support. |
| Backups | You supply storage and retention procedures. | You configure local or external retention. | Check frequency, retention, restore process, and whether backups are separate from the server. |
| Administration | Highest responsibility for packages and failures. | Moderate responsibility; scripts and monitoring remain yours. | Lower routine administration, but support quality and mod policy vary. |
| Crossplay and mods | You control configuration and compatibility testing. | You control configuration if the host permits it. | Confirm crossplay, mod support, player-slot rules, region, and current price before purchase. |
Provider plans and prices change, so evaluate those details at the time of purchase. Do not assume a plan’s advertised player slots, backup policy, or mod support from the amount of RAM alone.
What is a reliable sizing and monitoring process?
Size from observed peak behavior instead of an idle benchmark. A simple process avoids both overpaying for unused capacity and discovering a full disk during a busy session.
- Start conservatively: use the 2-vCPU, 4-GB Linux baseline only when you can resize and monitor it.
- Load a representative world: test the actual save, construction density, mods, and number of simultaneous players you expect.
- Measure peaks: record CPU per-core use, total memory, swap activity, disk free space, and save duration during the busiest sessions.
- Set alerts: notify the administrator before memory exhaustion or disk-full conditions stop saves.
- Scale the correct resource: add RAM for sustained memory pressure, choose faster CPU capacity for a saturated simulation thread, or expand storage when world and backup retention consume the available space.
- Retest after changes: a larger machine does not remove the need to check ports, libraries, world paths, and backup creation.
What are the common failure modes?
The server will not start on Linux
Check that libatomic1, libpulse-dev, and libpulse0 are installed for the distribution. Confirm that you launched start_server.sh from the intended installation and that the service account can read and write the save directory.
A Docker deployment fails immediately
Verify the host meets the documented minimums of GLIBC_2.29 and GLIBCXX_3.4.26. Then check that the persistent volume is mounted where the container expects it; otherwise the server may start with an empty world or lose data when the container is recreated.
Players cannot connect through Steam backend
Confirm the configured ports, host firewall, and router forwarding. Test from outside the local network; a successful local connection does not prove that the public route is open.
Saves or backups fail
Inspect free disk space and the permissions on the save and backup locations. Review retention settings, because four automatic backups plus manual copies can consume substantially more space than the active world alone.
The server lags despite having free RAM
Check per-core CPU use and host CPU contention. If one core is saturated, adding memory will not address the simulation bottleneck; move to faster CPU capacity or reduce simultaneous heavy activity and retest.
Frequently Asked Questions
Is 4 GB of RAM enough for a modded Valheim server?
It may be a workable starting allocation, but no official figure guarantees it. Mods, large builds, and concurrent activity can increase memory use, so watch swap and peak usage rather than relying on the nominal plan size.
Can swap replace adding RAM?
Swap can provide emergency breathing room when physical memory is exhausted, but it is much slower than RAM and can introduce severe latency. Treat sustained swapping as a signal to reduce workload or increase memory, not as the target configuration.
How do I estimate backup storage before I launch?
Create the world, measure the save directory, and multiply that observed size by the number of backup generations and manual copies you intend to keep. Add separate allowance for logs, Docker data, updates, and free working space; the documentation does not define a fixed world-file size.
What should I verify with a managed-hosting provider?
Ask for the actual CPU allocation, RAM, region, backup frequency and restore method, crossplay support, mod policy, player-slot rules, and current price. These commercial details are provider-specific and cannot be inferred from Iron Gate’s server documentation.