Menu
 

Valheim Server Performance 2026: Fix Desync, Lag & Unity 6 Stutter

Valheim Server Performance: Fixing Desync, Lag & Unity 6 Stutter (2026)

Valheim uses a networking design where the player who owns an area, usually the first one to arrive, runs the physics and creatures in that zone and sends the results to everyone else. It is efficient, but it causes desync and "rubber-banding" on dedicated servers when that player's connection is poor or the data queue fills up. This guide covers what the Valheim 1.0.17 server actually does with network data, the settings and mods that change it, the hardware that matters, and how to hold performance in the late-game biomes.

🔗 ZDO Data

Valheim syncs world changes via ZDOs (Zone Data Objects). When more of them are waiting than the game will queue for a player, updates are held back and that player desyncs.

🌀 Rubber-Banding

Happens when server and client disagree on a player's position: almost always a full send queue or a long route to the player who owns the area, not weak hardware.

The data limits in 1.0.17, and how to raise them

The old advice to hex-edit a 60 KB/s data cap is out of date: there is no such value in the 1.0.17 game files. What the dedicated server does instead, read from those files:

  • A fixed rate per connection: on the Steam backend the server sets every connection to send at 153,600 bytes a second (150 KB/s), with a 30-second connection timeout.
  • A small queue: it only queues more world updates for a player while less than 10 KB is still waiting to go out to them, and it works through the players one at a time, every 50 milliseconds.
  • SteamWorks: on the Steam backend, both the game port and the one above it have to be reachable; a server started with -crossplay goes through a relay instead.

Network mods raise those limits and add compression. Better Networking is the best known, but its original release has not been updated since November 2023; the versions built for 1.0 are forks by other authors, and newer mods such as Network Tweaks do the same job. Check any of them against the 1.0 mod compatibility tracker first, and see the Better Networking guide for how its settings work.

The Unity 6 engine upgrade (2026)

Patch 0.221.10 (February 2, 2026), "Five Years of Valheim!", moved the game to Unity 6. Iron Gate's notes list engine settings changed to improve performance in areas with many instances, massively reduced CPU use by armor stands, and a Performance mode that now reaches 60 fps. The 1.0.17 dedicated server runs on Unity 6000.0.75f1.

🚀 What it changed

Busy areas got cheaper: the patch notes name places with many object instances and armor stands specifically.

📏 What a server really uses

Measured on the Valheim servers we run: 1.8 GB of memory in a typical reading, and 3.2 GB at the 95th percentile with 6 to 10 players online.

Update mods before you patch. Engine and game updates are when BepInEx mods break: do not update a modded server until your plugins have releases for the new build, or you can hit crash loops on boot.

Step 1: Set the server's draw distance

Valheim 1.0's Draw distance graphics setting decides how many zones around each player are kept running, and the game itself warns that raising it may severely degrade performance. The server caps every player at its own value: a player who sets a higher draw distance gets the server's. The dedicated server takes it as a launch option, -simulationdistance followed by 0 to 6; without it the server uses level 2, the distance the game always had. A lower value means less for every zone owner to simulate and send.

Step 2: Keep the group in one place

Because the area's owner sends its state to everyone, the player with the best connection should lead the group into bases and fights, and a group spread over several busy areas multiplies the work.

Step 3: A network mod, if the queue is the problem

If the F2 panel (below) shows the send queue backing up, a network mod with a 1.0 build is the next step. Install the same version on the server and every client.

Hardware that actually matters

Before buying more hardware, confirm the bottleneck is real: paste the server log into the free Valheim log analyzer, which flags the mod, world-load and networking errors that produce symptoms people usually blame on the CPU.

Valheim leans on one main thread, so the spec that decides performance is single-core clock speed, not core count:

  • CPU: high single-core frequency (4 GHz+). On our servers the busiest 5% of readings with 6 to 10 players used about 3 cores.
  • RAM: measured 1.8 GB typical and up to 3.2 GB with 6 to 10 players; leave headroom for mods, which add their own.
  • Storage: an SSD shortens world saves and loads.
  • Network: each player's connection is capped at 150 KB/s, so even ten busy players stay around 12 Mbit/s up; latency to your players matters more than raw bandwidth.

For the full breakdown including client GPU notes, see the Valheim dedicated server requirements guide.

Holding TPS in the Ashlands & Deep North

Late-game biomes like the Ashlands and Deep North feature dense particle effects and high mob counts that spike CPU usage. To keep tick rate stable:

  1. Run on a high single-core CPU (4 GHz+).
  2. Use Expand World Data if you want to configure spawns, which reduces the number of active creatures and their ZDOs.
  3. Set -nographics -batchmode in your startup script so the headless server wastes no cycles on rendering.
  4. Test biome content on a staging copy first: combat density there can spike CPU in ways a quiet world never reveals.

Monitoring performance

Press F2 in game for the network panel: it shows data sent and received, the send queue, ping, frame rate and the number of ZDOs. A connection sending close to 150 KB/s all the time, or a send queue that keeps growing, is saturated: lower -simulationdistance on the server, or thin out active ZDOs. Track CPU, RAM, and average ping as a baseline before and after every change, and apply one change at a time so you can attribute any regression.

Managing save corruption

Desync can produce "ghost items" where a dropped item never appears for others, and a crash mid-write can reset a world. Always run automated world backups (the 1.0 world folder, or the .db and .fwl pair on older saves) (every 30 minutes is sensible), keep at least one off-node copy, and take a pre-change snapshot before any risky tuning so you can roll back in minutes.

Expert tip: a massive base is the heaviest thing a zone owner has to keep in sync, because every building piece is its own object. Spreading a large build over several areas, or trimming purely decorative pieces, is one of the biggest levers you have.

Related Valheim server guides

Lag-Free Valheim Hosting

Experience the Viking afterlife without the stutter. Supercraft's Valheim dedicated servers run on dedicated hardware with automated backups, and you can switch on BepInEx and 1-click Thunderstore mods, network mods included, from the panel.

Launch a Valheim server with this setup

Pick a preset and your new server boots preconfigured - rates, rules and mods already dialed in. Change anything later in the panel.

Browse all Valheim recipes →

Valheim Crossplay: Passive Mobs

Crossplay preset with the passive-mobs world modifier: creatures do not aggro unprovoked. Great for mixed-ski…

Valheim Crossplay: Scheduled Restarts

Crossplay-enabled server (Steam + Xbox/PC Game Pass) with a nightly restart window for stability. Use when yo…

Tired of fighting this issue every patch?

Run a managed Valheim server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Valheim hosting plans →
Top