Rubber-banding while you swing an axe, a longship that teleports back across the ocean, doors that won’t open, builds that flicker in and out of existence — if your Valheim dedicated server feels like it’s fighting you, you’re dealing with lag and desync. The good news: almost all of it traces back to a short list of fixable causes. The bad news: most of the advice online points at the wrong one. This guide walks through every real cause of Valheim multiplayer desync and the concrete fix for each, using values verified against the official wiki and the most-cited community testing.
“Lag” and “desync” aren’t the same problem, and conflating them is why people throw RAM at an issue that more RAM can’t solve. Lag is latency — the delay between your action and the server registering it. Desync is when your client’s picture of the world disagrees with the server’s authoritative state: you see a creature in one spot, the server thinks it’s somewhere else, and the world snaps to reconcile them. The two often appear together, but they have different root causes and different fixes.
The single biggest cause: Valheim’s hard-coded 64 KB/s per-client limit
Before you touch your hardware, understand the bottleneck that affects nearly every multiplayer Valheim server. The dedicated server has a hard-coded per-client send/receive cap of roughly 64 KB/s. That is not your internet connection — it’s a limit baked into the server binary itself, applied to every connected player individually. When two or three players gather in a dense base, or when one player streams a lot of world data while sailing into freshly loaded terrain, that 64 KB/s ceiling gets saturated and the server starts dropping or delaying updates. The result is classic desync: rubber-banding, late hit registration, creatures snapping around.
There is no vanilla setting that exposes this cap. The community fix is the Better Networking mod, which raises the limit to 256 KB/s and higher. It’s a BepInEx plugin, and like most gameplay-affecting mods it must be installed on both the server and every connecting client at matching versions — a client without it will either fail to connect or revert to the bottlenecked behavior. If you only do one thing from this article and you run more than two players, raising this cap is the highest-leverage change available.
Because this is a mod, you’ll want BepInEx set up correctly first. We cover the full framework install in our guide on how to add and install mods to a dedicated Valheim server, and the equally important reverse — how to disable Valheim server BepInEx mods — which is your fastest way to isolate whether a mod is the thing causing desync in the first place.
The RAM and CPU reality (it’s not what hosts advertise)
Valheim’s dedicated server is memory-heavy and, more importantly, largely single-threaded. The main game loop runs on a single core. This one fact reshapes how you should buy and tune a server: a 16-core CPU at 2.4 GHz will run Valheim worse than a 6-core CPU at 4.5 GHz, because Valheim can only meaningfully use one of those cores at a time. CPUs below roughly 3.0 GHz single-core clock are repeatedly cited as a direct cause of rubber-banding and desync, because the simulation simply can’t keep up with player actions and the world snaps to catch up.
RAM is the other axis, and it scales with how much of your world has been explored and built. These are community-verified figures, not an official spec — Iron Gate doesn’t publish hard requirements — but they’re consistent across hosts:
| Scenario | RAM | CPU | Storage |
|---|---|---|---|
| Absolute minimum (1-2 players, small world) | ~2 GB | High single-core clock, ~3.0 GHz+ | SSD strongly recommended |
| Typical small server | ~3 GB | 4 cores, fast single core | SSD, ~60 GB free |
| 2-10 players | 4 GB+ | 4 cores, 3.5 GHz+ ideal | SSD on fast storage |
| 10+ players or heavy mods (Valheim Plus, Epic Loot) | 8 GB+ | Strongest single-core clock you can get | SSD, headroom for saves |
The practical takeaway: if you’re choosing hardware or a plan, prioritize single-core clock speed first, then RAM, then core count. SSD storage matters too — Valheim writes the world save (.db) periodically, and on a slow disk those saves can cause brief hitches for everyone connected. Point your save directory at fast storage with the -savedir launch parameter. Our dedicated vs slots Valheim server breakdown goes deeper on why slot-based pricing can hide the resource allocation that actually determines smoothness.
Bandwidth and the distributed-simulation trap
Hosts often quote a healthy upstream figure like 250 Mbit/s, and you do want decent bandwidth, but raw pipe size is rarely the real constraint — the per-connection 64 KB/s cap above hits long before your link does. What surprises most admins is that Valheim uses a distributed simulation model: some game logic runs on the players’ clients, not the server. Ownership of a given object (a creature, a cart, a dropped item) is assigned to a nearby client, and that client simulates it.
This has a blunt consequence: one player with a poor connection or a weak PC can cause desync for everyone near them. If a friend on satellite internet owns the simulation of the boar pen, those boars will stutter for the whole group. There is no clean server-side fix for this in vanilla — the levers are to make sure every player has a stable connection, to keep the slowest player from being the one loading new terrain or fighting in dense areas, and to raise the networking cap so the server can push corrections faster.
Too many builds, entities, and ground pieces
This is the cause people most underestimate, and it gets worse the longer a server runs. Every loaded area carries a count of active instances — structure pieces, creatures, dropped items, and terrain modifications. Valheim has to simulate, network, and save all of it. A sprawling mega-base with thousands of pieces, a hoard of tamed animals, or a swamp dredged into a flat island all multiply the work the single-threaded loop has to do every tick. Past a threshold, the server can’t finish a tick in time and everyone desyncs.
Two specific offenders:
- Structure/piece count. Each wall, beam, and decoration is a tracked instance. Decommission abandoned bases, demolish half-finished projects, and spread builds out so fewer pieces load into a single area at once.
- Ground modifications. Terrain raising, leveling, and digging are stored as edits on top of the base world, and excessive terraforming is a known, severe performance drain. Old saves from earlier game versions are especially heavy. The vanilla
optterraincommand (a player/utility command, safe to run) converts legacy terrain modifications to the newer, lighter format and can meaningfully reduce the load near heavily-terraformed areas.
Run optterrain while standing in your most-edited areas, and audit your largest bases. A tamed-animal cull also helps — every wandering boar and wolf is a simulated, networked entity. Penning animals tightly or thinning the herd cuts the per-tick cost directly.
lodbias: tuning client draw distance
The lodbias command is a client-side player/utility command (no devcommands required) that adjusts level-of-detail and draw distance. The wiki documents a range up to 7, while several sources cite 1-5; treat 1-5 as the safe documented range. Lower values render less distant detail, which reduces the load on weaker client PCs — and since some simulation is client-owned, a client that isn’t choking on rendering can keep up with the server better. Open the console with F5 (after adding -console to your launch options) and run:
lodbias 2This won’t fix server-side desync, but on a group where one player’s machine is the weak link, dialing their lodbias down is a quick, no-mod mitigation. For the full set of console and admin commands, see our Valheim console commands and prefab reference.
Dedicated vs P2P: stop hosting from your gameplay PC
If you’re hosting via the in-game “Start Server” / listen-server option, your machine is doing two jobs at once: running your client and running the world simulation for everyone. The two compete for the same single-threaded CPU budget, and when you load a busy area or get into a fight, the server half of the work suffers — desync for the whole group, triggered by you.
A true dedicated server is a standalone process that runs 24/7 independent of any player’s client. It stays up when everyone logs off, gives you control over RAM, CPU, and storage allocation, and lets you configure the admin list, save directory, world, and mods properly. Moving off P2P is one of the most reliable smoothness upgrades available, and it eliminates the “host’s PC is the bottleneck” problem entirely. If you’d rather not maintain the box yourself, a managed Valheim server with guaranteed dedicated resources gives you the high single-core clock and SSD storage this game actually needs, without the home-PC tradeoffs.
Version mismatches: a subtle desync source
If a connection fails outright or behaves erratically right after a patch, suspect a version mismatch. Client and server must be on the same branch and version. A client running the public-test beta cannot reliably join a server on the live build, and vice versa. After any Valheim update, make sure both your client and your server binary are updated before assuming the desync is a performance problem.
Update the dedicated server through SteamCMD. The dedicated-server app ID is 896660 (the game itself is 892970). A standard live update looks like this:
steamcmd +force_install_dir "path" +login anonymous +app_update 896660 validate +exitOne gotcha worth flagging: since late 2024, the anonymous SteamCMD download of the Valheim dedicated server has at times been restricted, and game ownership on the SteamCMD login may now be required. If +login anonymous fails to pull the server app, log in with an account that owns Valheim.
The public-test branch deserves its own warning because it’s a common source of “my server suddenly won’t connect.” It is code-gated — the access code is yesimadebackups, and there’s a reason that code exists: test builds can be unstable, buggy, or corrupt saves. To update the server onto the beta branch:
steamcmd +force_install_dir "path" +login anonymous +app_update 896660 -beta public-test -betapassword yesimadebackups validate +exitHosts have occasionally hit a bug where the server auto-loads public-test unintentionally; explicitly setting -beta public (or removing the beta flag and re-validating) pins it back to the live build. Always back up both .db and .fwl world files before opting into any beta. The full walkthrough is in our Valheim public-test beta install guide.
A practical desync-fixing checklist
Work this list top to bottom — it’s ordered by impact and ease:
- Confirm versions match. Update client and server to the same branch before anything else.
- Move off P2P to a true dedicated server if you’re still listen-hosting.
- Check single-core clock. Below ~3.0 GHz is a known desync cause — this is hardware, not config.
- Restart the server regularly. Memory use grows over time; a scheduled daily or weekly restart resets it.
- Cut instance count. Demolish abandoned builds, thin tamed animals, run
optterrainin heavily-edited areas. - Raise the networking cap with the Better Networking mod (server + all clients) if you run more than two players.
- Tune weak clients with
lodbiasand make sure no one is on an unstable connection. - Isolate mods. If desync started after adding a plugin, disable BepInEx to confirm whether a mod is the cause.
For the canonical configuration reference — launch parameters, admin setup, and save-directory handling — see the XGamingServer Valheim documentation.
Frequently asked questions
Why does my Valheim server rubber-band even though my internet is fast?
Because the bottleneck usually isn’t your internet. Valheim’s dedicated server has a hard-coded per-client send/receive cap of about 64 KB/s, applied to each player individually regardless of how fast your overall connection is. On top of that, the server is single-threaded, so a CPU with a low single-core clock (below ~3.0 GHz) can’t process actions fast enough and the world snaps to catch up. Fix the per-client cap with the Better Networking mod and make sure your CPU has a high single-core clock before blaming your ISP.
How much RAM does a Valheim dedicated server actually need?
Plan for about 2 GB as an absolute floor, ~3 GB for even a small world with a couple of players, 4 GB+ for 2-10 players, and 8 GB+ for 10+ players or heavy mods like Valheim Plus and Epic Loot. These are community-verified figures, not an official spec. RAM use grows as players explore more of the world and build more structures, so a server that ran fine at launch may need more after months of play.
Can too many buildings cause lag on a Valheim server?
Yes — this is one of the most common and underestimated causes. Every structure piece, tamed creature, dropped item, and terrain edit is a tracked instance the single-threaded server must simulate, network, and save each tick. Large mega-bases and heavy terraforming are particularly costly. Demolish abandoned builds, spread structures out, thin your tamed animals, and run the vanilla optterrain command in heavily-edited areas to convert legacy terrain modifications to the lighter format.
Does updating fix Valheim desync, and do client and server both need updating?
Both must be on the same branch and version, and a mismatch absolutely causes connection failures and erratic behavior. After every patch, update your client and your dedicated server (SteamCMD app ID 896660) before assuming you have a performance problem. If you’re on the public-test beta, the access code is yesimadebackups, and you should never mix a beta client with a live server. Note that anonymous SteamCMD downloads of the server may now require game ownership on the login.
Is a dedicated server better than hosting through the game for reducing lag?
Significantly. When you host through the in-game option, your PC runs both your client and the world simulation, and they compete for the same single-threaded CPU budget — so your own gameplay causes desync for the group. A true dedicated server runs as a standalone 24/7 process with its own RAM, CPU, and storage, eliminating that contention and the “host’s PC is the bottleneck” problem. Because Valheim favors single-core clock speed over core count, the quality of that one fast core matters more than slot count or raw core totals.
Will lowering lodbias fix my server desync?
Not server-side desync, but it helps on the client side. lodbias (documented range 1-5 safe, up to 7 on the wiki) lowers level-of-detail and draw distance, reducing the rendering load on a weaker PC. Since Valheim distributes some simulation to players’ clients, a client that isn’t struggling to render keeps up with the server better — which reduces the desync that one weak machine can spread to nearby players. It’s a useful no-mod mitigation, but the bigger fixes are the networking cap, CPU clock, and instance count.
Desync on Valheim is almost never one thing — it’s the combination of a hard-coded networking cap, a single-threaded loop that wants a fast core, and an instance count that creeps up as your world grows. Address them in order, keep your versions matched, and restart on a schedule, and a server that used to rubber-band will run clean even with a full group raiding the Ashlands.
Ready to play?
Run your own Valheim 1.0 server with XGamingServer
Spin up an always-on Valheim 1.0 server your friends can join in minutes — no port-forwarding, no tech headaches.
