Valheim Server

How to Reduce Lag on a Valheim Dedicated Server

“The server is laggy” describes at least three different problems, and they have opposite fixes. Network latency shows up as rubber-banding and delayed hits and is about the path between player and server. Server-side stutter — the world hitching for everyone at once — is about CPU, memory, or how much stuff exists in the world. Client frame-rate problems get blamed on the server constantly and have nothing to do with it. Diagnose which one you have before changing anything.

Tell the three apart

Ask who’s affected. One player lagging while everyone else is fine is that player’s connection or machine. Everybody hitching simultaneously is the server.

Use ping in the console. An admin with the console open can check latency to the server directly. High and variable ping for one person, with the server otherwise healthy, is a network problem on their side. Low ping while the world still stutters means the server is struggling to keep up, not to deliver packets.

Watch the server while it happens. Have someone play while you watch:

top -b -n 1 | head -20
uptime
free -h

A core pegged at 100% during the stutter is a server-side problem. An idle server during the stutter means the problem is the network or the client.

Fix server-side stutter

Check whether you’re CPU-limited. Valheim’s simulation leans heavily on single-thread performance. If top shows one core saturated while others idle, more cores won’t help — faster cores will. This is also why cheap instances with many weak vCPUs disappoint.

Check for memory pressure. A server that has grown into swap stutters in a way no network change can fix. Compare observed peak usage against capacity with free -h, and look for swap activity. If you find any, add RAM or reduce load; see How to Size Hardware for a Valheim Dedicated Server.

Get other work off the box. A server sharing a machine with backups running mid-session, another game server, or a media transcode will hitch during those jobs. Schedule heavy tasks for hours nobody plays — this alone fixes a lot of “random lag spikes at 9pm” reports.

Watch out for burstable cloud plans. If your provider talks about CPU credits, a server under steady load can exhaust its allowance and get throttled — which feels exactly like the server getting worse as the evening goes on. Check the provider’s CPU-credit graph before blaming the game.

Restart on a schedule. Long-running servers accumulate memory use. A nightly restart at a dead hour is a cheap, effective mitigation: Run a Valheim Server as a systemd Service has a timer for it.

Reduce what the world asks of the server

Often the server is fine and the world has become expensive. Things that genuinely add per-tick work:

  • Very dense builds. Huge numbers of individual pieces, especially with physics-relevant connections, are real work every tick. A sprawling megabase is the most common cause of a server that used to be smooth.
  • Large numbers of tamed creatures. Each one is an active entity with behaviour to simulate. Breeding pens that got out of hand are a classic.
  • Dropped items lying around. Piles of loose items in a busy area cost more than you’d guess.
  • Players spread across distant regions. The server keeps multiple areas active at once rather than one. Four people in four biomes is a heavier job than four in one base.

None of this means “don’t build”. It means that when a formerly-smooth server starts hitching, look at what changed in the world before you look at the hardware.

Fix network lag

Location matters more than anything you can buy. Host near the majority of your players. No CPU upgrade compensates for a transcontinental hop.

Prefer wired for the server, always. A server on Wi-Fi introduces jitter that looks exactly like server-side lag. Plug it in.

Look at upstream capacity, not download speed. A home server’s job is almost entirely uploading world state to clients. A connection with a thin upload is the classic bad fit for self-hosting — and it degrades most when other people in the house are uploading too.

Check for congestion at home. Someone streaming, backing up to the cloud, or on a video call will affect a self-hosted server. QoS rules on the router that prioritise the server’s traffic help materially. And rule out VPNs — a commercial VPN on either end routinely adds latency and breaks UDP behaviour, so turn it off for the test.

Confirm the port setup is clean. Odd, intermittent connection quality sometimes traces back to a partially wrong forwarding setup: How to Port Forward a Valheim Server.

Don’t forget the client side

If it’s one person, look at their end before touching the server:

  • Frame-rate problems in the game are client GPU/CPU, not server lag, and they feel similar enough that players conflate them constantly.
  • A full drive or an overheating laptop produces stutter that arrives with the game, not the server.
  • Client-side mods can be expensive. A visual mod at high settings is their problem, not yours.

Ask them for their in-game frame rate and their ping separately. Low frame rate with low ping is entirely a client issue.

Mods deserve their own look

Some plugins do real work every tick. If lag started when a mod list changed:

  1. Note the plugins added most recently.
  2. Read BepInEx/LogOutput.log for errors — a plugin throwing repeatedly is expensive.
  3. Remove plugins in halves and test, rather than one at a time.
  4. Check each mod’s own configuration under BepInEx/config; some have settings that trade performance for features.

Mod-management workflow: Installing Valheim Mods on Your Server with BepInEx.

A diagnostic order that works

  1. Is it one player or everyone?
  2. ping from the console — latency or simulation?
  3. What does top show on the server during the lag?
  4. Any memory pressure or swap?
  5. What else is running on the box, and is anything scheduled at that time?
  6. What changed recently — a mod, a big build, more tamed animals, a new player location?
  7. Only then consider hardware or a different host.

Most self-hosted lag turns out to be one of four things: a CPU that’s single-thread limited, a server sharing a machine with something noisy, a home connection with thin upstream, or a world that has quietly become much more expensive than it was six months ago.

performancetroubleshootingadmin