Valheim Server Performance and Optimization

How Valheim Networking Works

Valheim uses a hybrid networking model: the dedicated server handles world state, but physics calculations are done client-side. The first player to enter an area becomes the "Zone Owner" responsible for synchronizing that zone. If that player has poor connectivity, everyone in the zone experiences issues.

World changes are synced via ZDOs (Zone Data Objects). If too many are sent at once, the server's data rate throttle kicks in and players desync (rubber-banding, objects appearing/disappearing).

Valheim caps its own outgoing data rate, and that cap is low for a full server. It is a game-level limit, not a GameGrid one, and it is the root cause of most desync. Community mods exist that raise it; they have to be installed on the clients as well as the server, so they lock out Xbox and Game Pass players.

The Ashlands biome sends significantly more data than other biomes. Expect higher network load if your players are in the Ashlands.

Common Causes of Lag

1. Building piece count: the number one cause of Valheim server lag. Each building piece is tracked and synced. Sprawling castles with thousands of pieces will cause lag, especially when players enter the area. There is no hard limit, but a single base with 3000+ pieces is a common threshold.

2. Tamed animals: each tamed creature is an active entity. A breeding farm with dozens of boars or wolves eats more performance than the same number of building pieces. Cull populations that are getting out of hand.

3. Terrain modifications: every terrain raise/lower is stored and synced. Extensive terraforming near a base increases load on every player who enters that zone.

4. Long-lived worlds: a world that has been explored for hundreds of hours has more ZDOs to sync. Periodic world resets can help if lag becomes unmanageable.

5. Ashlands content: the Ashlands biome is the most data-intensive area in the game. Expect performance dips when multiple players are in Ashlands simultaneously.

Reducing Lag

Keep building piece counts reasonable. A few hundred pieces per base is fine. 3000+ in a single area will cause noticeable lag for everyone who enters.

Limit tamed animal populations. A few pets are fine; a farm of 50+ animals is a performance drain.

Avoid excessive terrain modification. Flatten what you need, but do not reshape entire biomes.

If you have 10 players, try to spread out rather than clustering everyone in one base. Each zone with players in it adds to the server's sync load.

For an all-Steam modded group, a networking mod that raises Valheim's data-rate cap can reduce desync. It is a client-and-server mod. See the Mods guide.

Check your plan: the Resource Usage card on the server Overview tab shows live CPU and memory. If memory is consistently at the top of your allocation, a larger plan is the fix. Large, long-lived worlds need more.

Server Startup Time

A fresh world starts in under a minute. Loading a large existing world may take 30-60 seconds.

If the server takes longer than 2 minutes to start, check the Console tab for errors. A corrupted save file can cause the server to hang on load - restore from a backup if this happens.

Mod initialisation (BepInEx) adds to startup time. Every GameGrid Valheim server runs BepInEx and the GameGrid Bridge, which costs a moment; a heavily modded server may take 2-3 minutes to fully start.

Monitoring Resource Usage

The Resource Usage card on the server Overview tab shows live CPU and memory for the Valheim server process itself. It carries a LIVE badge while the figures are fresh, and switches to LAST KNOWN if the host stops answering, so you can tell a quiet server from a stale reading.

Beside it are player count, network in and out, uptime, thread count and connection count.

Memory climbing steadily with world age and building count is normal for Valheim; CPU sitting near the top of your allocation during ordinary play is not.

If CPU or memory is consistently pinned, either reduce the load (fewer buildings, fewer tamed animals, fewer concurrent players) or move to a larger plan.

Sudden CPU spikes during raids are normal and subside when the event ends.

When to Contact Support

If your server is lagging with few players and modest builds, the issue may be hardware-related. Open a support ticket with your server name, the number of players online when the lag occurs, and the Resource Monitor readings.

If the server crashes or hangs repeatedly, include the last 50 lines from the Console tab in your ticket so we can diagnose the cause.

For mod-related performance issues, try removing mods one at a time to isolate the culprit before contacting support.