Valheim Server Lag: Why It Happens and How to Fix It

How Valheim shares the work

The dedicated server stores the world and passes the data around, but it doesn't calculate everything: the physics, enemies and animals in each zone are simulated by the computer of the first player who reaches it. That player is the zone's “owner” until they leave.

That's why Valheim lag looks so specific: enemies teleporting, hits that don't deal damage until a second later, doors and chests that take a while to open, or a boat that jumps around. If the zone owner has a bad connection or a weak computer, everyone nearby suffers, even if the server has power to spare.

First, find out whose lag it is

1. Is it everyone or just one person?

   If only one person has problems, it's their connection or their computer. If it's bad for everyone at the base and fine for whoever is exploring far away, it's the zone: check who got there first.

2. Does it always happen with the same person nearby?

   If the base stutters when a particular friend joins (wifi, mobile data, another country) and runs fine when they're not around, they're the one who owns the zone.

3. Does it happen when you're alone too?

   If the base still stutters when you join alone, with a good connection, the problem is the base itself (too many objects) or the server. Read on.

Let the best connection own the zone

The most effective fix, and it's free: have the player with the most stable connection enter the base or the fight area first, ideally on a cable rather than wifi. If someone with a bad connection is already there, they should move away until the zone stops loading for them and then come back: when they leave, the zone passes to another player.

The same goes for raids and bosses: let the player with the best connection arrive first and the rest follow (the bosses in order and how to fight them as a group).

The game's data rate limit

Valheim limits how much data it sends to each player per second. With 10 players and a big base, that cap falls short, and you notice it as things popping in late when you reach the base.

The usual fix is a network mod. The classic one, BetterNetworking (on Thunderstore), raises that limit and compresses what gets sent, but its latest version is from November 2023, before 1.0. An up-to-date one is NetworkTweaks: it goes on the server and on the players, and its author warns that raising the limit only works without crossplay. Both, with their drawbacks, in the network mods in the guide to mods for playing with friends. Always check on Thunderstore that the version is newer than 1.0 (9 September 2026).

If someone in the group plays on console (Xbox, PlayStation 5 or Switch 2), this won't work: consoles have no mods, and a mod the players also need locks them out.

Huge bases: lag you build yourselves

Every building piece, every item dropped on the ground and every animal is something the game has to sync. A base with thousands of pieces, chests everywhere and a pen of boars or lox that have kept breeding weighs a lot, especially for whoever arrives first.

What helps most: stop breeding animals without limit (a few are enough), pick up or destroy whatever is lying on the ground, and spread the base over several areas instead of building everything in the same spot.

The stutter every half hour

The server saves the world every 30 minutes (a world saved message shows up in the console). With a big world, that moment can feel like a stutter of a few seconds for everyone. It's normal and doesn't mean anything is wrong.

On your own server you change it with the -saveinterval launch argument. On NapNodes, with “Save the world every (seconds)” in “Settings”: more time between saves means fewer stutters, but you lose more progress if something goes wrong. How those saves work, and the backups the game keeps, in the Valheim backups guide.

When it really is the server

If it's bad for all of you, even when only the player with the best connection is in, look at resource usage. The signs are memory stuck at your plan's maximum, stutters that get worse the longer it's been running, or a server that crashes on its own. It happens mostly with mods and with heavily explored worlds.

Before paying more, try the cheap fixes: restart the server, remove the mods you don't use and add new ones a few at a time. If it's still tight, the Valheim RAM guide tells you how much you need.

With NapNodes

1. Check memory and CPU

   Your server's “Home” shows live memory in use and the processor against what it has; “Performance” shows the graphs, with your server's limit as the ceiling. The RAM you pay for is reserved for you: no overselling, nobody shares it.

2. Install the network mod, if it suits you

   In your server's “Mods”, search for it and check its date: “Install” downloads it with what it needs (and BepInEx the first time). It loads on restart. More detail in the Valheim mods guide.

3. Pass it on to your friends

   The panel gives you an r2modman profile code (also in the “Installed” tab): each player imports it with “Import / Update” → “Import new profile” → “From code” and gets the same mods.

4. If it won't start with the mod

   Remove it from “Installed” and restart. Before trying new mods, make a backup in “Backups”.

5. If it falls short

   RAM belongs to your account, not to each server. In “My servers”, if you have spare RAM (or another of your servers has some to spare), give it to this one with “Adjust” on its card. If not, “Buy RAM” on that same screen, or “More RAM” in “My plan & invoices”, to go from Meadows (4 GB) to Mountain (6 GB) paying only the difference for the rest of the period. The new RAM arrives on restart, with the same world.

Frequently asked questions