Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Jitter (creatures that stutter, terrain that does not)
The world itself is static and already on your disk, so terrain and buildings never lag. Everything that moves is being simulated by some machine and relayed to yours. When delivery is uneven, that split becomes visible: a perfectly solid world with greylings sliding around in it. That picture is a network symptom, not a performance one.
Packet loss (the raid killer)
Combat here is short, decisive and full of one-off events - a parry, a stagger, a troll's swing connecting. Those are discrete messages with nothing to interpolate from. A lost packet does not blur them, it removes them, and the first you know about it is being thrown across your own base by an attack you never saw start.
Ping (to a player, or to a box)
If your group plays on a dedicated server, your ping is to that machine and it is stable. If one of you hosts, your ping is to their living room, and it changes whenever the host does. Under 80 ms to the host keeps combat honest; the consistency matters more than the number.
What you see in game, and which number on this page explains it.
Most multiplayer games have exactly one authority. A server decides where everything is, clients display a prediction of it, and every player's experience is a function of their own path to that one machine. Valheim spreads the job out instead: the host owns the world, but responsibility for simulating any particular creature or object sits with whichever player is nearest to it, and it hands over as people move around.
That design is what lets a modest home machine host a world containing a great deal of active content - the work is shared rather than concentrated. The cost is that the quality of your experience is not determined by your own connection alone. If the player standing next to a troll has a poor line, that troll behaves badly for everyone, and their connection has become part of yours for as long as they are the nearest one.
This explains a pattern that groups find genuinely confusing: lag that follows a location or a person rather than a session. Everything is fine in the meadows and terrible in the swamp, or fine until a particular friend logs in. Neither observation makes sense in a normal client-server game, and both are the expected behaviour here.
It also changes what a fix looks like. Measuring your own line is still necessary - a bad connection makes you a bad neighbour as well as giving you a bad time - but it is not sufficient, and the group's overall experience is closer to the worst connection in it than the average. For a world that a group intends to keep, moving it onto a dedicated server and getting the regular attendees onto cables does more than any individual tuning.
If the chart above shows packet loss or high jitter, work through
these in order.
Why does one player make Valheim lag for everyone?
Because the simulation of creatures and objects is distributed across the players near them. A player with a poor connection who is closest to a troll is the machine simulating that troll, and everyone else sees the result of their line rather than their own.
Is a dedicated server better than hosting in-game?
For any world you intend to keep, yes. It removes the requirement that a specific person be online, it gives the world a stable address and latency, and it stops one player's household from being the group's bottleneck.
What causes the regular stutter in Valheim multiplayer?
Usually the periodic world save on the host, which grows with the size of the world and the number of structures in it. It is rhythmic rather than random, and it will not appear on this chart because it is not a network event.
Does high ping cause deaths in Valheim?
Loss and jitter cause more of them than raw ping does. Combat is built on discrete events - parries, staggers, swings - and a lost packet removes one entirely instead of delaying it. That is what being hit by an attack you never saw actually is.