Valheim Server Optimization

Building Piece Limits

Building piece count is the number one performance factor in Valheim. Each piece (wall, roof, floor, beam) is a tracked object that the server syncs to every player in the area.

Under 500 pieces per base: no noticeable impact.

500-2000 pieces: mild lag when entering the area, especially with multiple players.

2000-3000 pieces: noticeable lag and desync for all players in the zone.

3000+ pieces: significant lag, rubber-banding, and slow zone loading.

There is no hard cap - the server will not stop you from building. But performance degrades linearly with piece count.

Recommendation: keep main bases under 2000 pieces. Use multiple smaller bases rather than one megastructure. Outposts and satellite bases spread the load across zones.

Tamed Animal Management

Each tamed animal (boar, wolf, lox, etc.) is an active entity that the server tracks and syncs. A farm with 50+ tamed animals is a bigger performance drain than 500 building pieces.

Tamed animals breed if there is food and space. An unchecked breeding farm can quickly balloon to hundreds of entities.

Recommendation: limit breeding farms to 10-20 animals. Cull excess population regularly. If you do not need a breeding farm, do not feed the animals - they will not breed without food.

Save Interval Tuning

The default Save Interval is 1800 seconds (30 minutes). It is in Settings under Performance, and the panel accepts 600 to 86400 seconds. Like every Valheim setting it needs a restart.

For high-activity servers with frequent raids or combat, reduce it to 600-900 seconds (10-15 minutes). This reduces the maximum progress loss if the server crashes, at the cost of a brief lag spike every save. 600 is the lowest the panel allows.

For low-activity building servers, you can increase it to 3600 seconds (1 hour). The save lag spike is less frequent, but progress loss on crash is larger.

Save lag spikes last 1-3 seconds and cause a brief freeze for all connected players. This is normal and unavoidable in Valheim.

World Age and ZDO Count

As a world is explored, the number of Zone Data Objects (ZDOs) grows. Every modified terrain, dropped item, planted crop, and built structure adds ZDOs.

A world that has been played for 200+ hours with extensive exploration will have significantly more ZDOs than a fresh world, causing higher baseline CPU and memory usage.

If performance degrades over time despite stable building counts, world age is the likely cause. A world reset (generating a fresh seed) is the solution.

Before resetting, back up the old world. You can always restore it later.

Network Optimization

Valheim caps its own outgoing data rate, and that cap is low for a full server. It is the root cause of most desync and rubber-banding, and it is a game-level limit rather than a GameGrid one.

Community mods exist that raise it, and they are the most impactful performance mods for a large group. They must be installed on every client as well as the server, so they lock out Xbox and Game Pass players - do not use one on a crossplay server.

For servers with players on different continents, latency is unavoidable. The zone-owner model means the first player to enter an area is responsible for syncing it - if they have 300ms ping, everyone in that zone suffers.

A crossplay server also relays every player through PlayFab, which adds some latency for everyone. Turning crossplay off removes the relay, at the cost of locking out Xbox and Game Pass players.

Recommendation: choose the region closest to the majority of your players when you order. The order page only offers regions that currently have capacity.

Mod Performance Impact

Some mods are performance-heavy. Common culprits:

Epic Loot: adds item generation and tracking overhead. Noticeable on large servers.

Valheim Plus: configurable, but some features (plant growth, animal breeding) add entity processing load.

Server Devcommands: minimal impact unless cheats are actively used.

The GameGrid Bridge, which every Valheim server here runs, reads player positions on the game's own main thread. The panel polls it every five seconds for that reason rather than harder.

If you install a new mod and performance drops, remove it and test again. Isolate the cause before keeping the mod.

When to Upgrade Your Plan

Watch the Resource Usage card on the server Overview tab. If CPU or memory is consistently pinned during ordinary play, a larger plan is the fix.

Signs you need an upgrade: players desyncing with fewer than 5 players online, a server taking more than 60 seconds to start with no mods, or CPU spiking during normal gameplay.

Plan changes are made from the Manage Plan page, reached from the Manage Plan button on your dashboard. If you are unsure what your server needs, open a support ticket with your Resource Usage readings and we will tell you.