Free tools Windows power users keep installed
One-click scans. No signup required.
Improve a Valheim server by identifying the bottleneck before changing hardware. First separate client frame-rate problems from server simulation, network delay, save-time stalls, and mod incompatibilities. A dedicated server can move persistent-world hosting away from the player who is also running the game, but it cannot repair a weak client GPU or a poor internet connection.
Playing with friends? Godlike.Host runs hosted Valheim servers from 10 data-center locations, with free DDoS protection.
Use the sequence below: reproduce and classify the symptom, measure CPU, memory, disk and network activity, verify the server’s connection path, remove competing traffic, then adjust save behavior or mods one change at a time.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What “server performance” means in Valheim
Players use “lag” for several different failures. Treating them as one problem leads to expensive upgrades that change nothing. Record exactly what happens and who experiences it.
Client frame-rate drops
If one player sees a low or unstable frame rate while other players move normally, the problem is usually on that player’s computer: rendering load, graphics settings, thermal throttling or another local process. Moving world hosting to a dedicated machine may free CPU time on the gaming computer, but it does not make a weak graphics processor render frames faster.
Rubber-banding and desynchronisation
Characters snap backward, creatures teleport, or actions appear to happen several seconds late when state updates are delayed or lost between a client and the server. Check latency, packet loss, Wi-Fi quality, tethered mobile connections and upload contention before buying more memory.
Delayed interaction
Opening a chest, placing a building piece or picking up an item may take a long time even when frame rates look normal. This can indicate a busy simulation thread, a saturated host, a congested uplink or a mod that is spending too long in an update loop.
Recommended Free Tools
Save-time hitching
If everyone freezes at regular intervals and the pause coincides with a save, inspect disk activity, world size and save settings. A save operation is different from continuous simulation load; reducing unrelated background activity can help you determine which one is responsible.
A whole-party slowdown
When every connected player reports the same delay at the same moment, start with the server process and the network path. When only one player is affected, compare that player’s route and local connection with another player before changing the server.
Rank #2
- Viking Game laminated laptop stickers All approx 3"-4" in length
- Laminated, Not UV Proof. Will fade in sun. Best used indoors.
- Great for Laptops, Phones, Computers, Tablets and more!
- Handmade by a Stay at Home Small Business Mama!
What a dedicated server can and cannot fix
Iron Gate describes a dedicated server as a way to provide a persistent world that friends can play in at any time. The server process keeps the world available independently of a player’s game client. That separation is valuable when the usual host has to leave, restarts frequently, or is running the game and the server on the same machine.
It is not a universal lag cure. A dedicated process cannot correct a bad last-mile connection, packet loss on Wi-Fi, a client-side frame-rate problem, or a mod mismatch between players. Decide whether you need persistent availability, more predictable resources, or simply a better connection before selecting a hosting arrangement.
Measure the bottleneck before upgrading
Reproduce one failure consistently
- Write down the symptom in plain language: for example, “all players freeze during an automatic save” or “one player rubber-bands while others are fine.”
- Reproduce it in the same area of the world with the same number of players if possible. Note the time, nearby structures, active events and whether a save message appears.
- Watch the server process and the host while the problem occurs. Record CPU utilisation, memory in use and available, disk activity, network upload and download, and the process log.
- Have at least two players report whether they see the same delay. A shared symptom points toward the server or common network path; an isolated symptom points toward that player’s route or client.
Interpret the measurements
| Observation while the problem occurs | Most useful next check | What not to assume |
|---|---|---|
| CPU is consistently saturated by the server process | Reduce competing processes, test with mods disabled, and compare load in a simpler area before considering more CPU capacity. | Do not assume more RAM will solve a CPU-bound simulation. |
| Memory is nearly exhausted or the system is swapping | Check world growth, other services and process limits; test additional memory only after confirming sustained pressure. | Do not treat a community sizing estimate as an official requirement. |
| Disk activity spikes at the same time as a freeze | Correlate the pause with the save schedule and backup activity; change one save setting at a time. | Do not claim a particular drive will fix every save hitch without measuring. |
| CPU and memory are quiet, but players rubber-band | Check latency, packet loss, Wi-Fi, tethering, firewall rules and competing uploads. | Do not buy hardware before testing the network path. |
| Only one client has low FPS | Diagnose that client’s graphics load and background applications. | Do not call a local rendering problem a server bottleneck. |
Use the small-VPS estimate correctly
No official minimum server specification is published in the sources reviewed for this guide. A community guide gives 2 virtual CPU cores and 4 GB of RAM as a consensus starting point for a small Linux VPS, while warning that memory use can rise as a save becomes more complex. Treat those numbers as an initial estimate for a small world, not a guarantee, baseline for every player count, or requirement from Iron Gate.
Measure your own world before resizing. A larger map, more explored area, more structures and additional services can change resource use. If the measured bottleneck is not CPU or memory, adding either resource is unlikely to improve the symptom.
Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Verify the network path and server backend
Steam backend: forward the default ports
With the Steam backend, Valheim uses UDP ports 2456–2457 by default. Forward both ports from the router to the server host and allow them through the host firewall. Test from outside the local network; a connection that works only for devices on the same LAN has not verified the public path.
Crossplay backend: use the relay path
When the Crossplay backend is selected, the server transmits data through a relay server. External players therefore do not need router port forwarding to reach the server from outside the local network. You still need a running server, compatible clients and a network connection that can sustain the traffic.
Running more than one server
Do not casually change ports when several instances share one public IP address. Give each instance a distinct port range and configure a distinct instance identity wherever the server setup requires one. Document which range belongs to which world so that a router or firewall change does not silently send players to the wrong instance.
Remove competing traffic
Pause torrents, cloud-sync uploads, game downloads and video streams on the host network while testing. A small server upload can suffer when another application consumes the uplink or fills the router’s queue. Test traffic-shaping or packet-modifying utilities separately; utilities that alter or prioritise traffic can interfere with games.
Rank #4
- Valheim Boar Loves You quote. A perfect design for fans of the best selling Viking game.
- An amazing and unique design which is also perfect as a gift.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Use wired Ethernet for the server whenever practical. Ask the most affected players to test a wired connection as well. A tethered mobile connection may have variable latency and packet loss even when a speed test reports a high peak rate. These are diagnostic steps, not a universal hardware prescription.
Configure saves and backups deliberately
Know the documented defaults
| Setting | Documented value | Meaning |
|---|---|---|
-saveinterval |
1800 seconds (30 minutes) |
Automatic world-save interval by default. |
-backups |
4 |
Number of automatic backups documented by the guide. |
-backupshort |
7200 seconds |
Interval for the short-backup cycle. |
-backuplong |
43200 seconds |
Interval used for subsequent long-backup cycles. |
Those values describe the documented defaults, not a promise that every world will save without a pause. A shorter save interval limits how much progress could be lost after a crash, but it can also cause save activity more often. Change one value, reproduce the hitch, and compare logs and disk activity rather than changing every backup option at once.
Apply and test a save change
- Stop the server cleanly and copy the world and current backup files to a separate location.
- Record the existing startup arguments so you can restore them exactly.
- Change only the relevant argument, such as
-saveinterval 1800, in the server’s launch configuration. Keep the documented value unless you have a measured reason to test another interval. - Start the server, let players reproduce the same activity, and note the timestamp of each save and any pause.
- If the change is worse, stop the server and restore the previous argument and world copy before testing a different variable.
Practice restoration, not just backup creation
Backups are useful only if they can be restored. Test on a copy with the server stopped: identify a backup, place it in the expected world-save location, start the server, and verify the world and player access. Never overwrite the only current world while experimenting. Keep multiple restore points so a corrupted or unwanted change is not copied over every backup.
Audit mods and version compatibility
Establish a clean baseline
Before tuning a mod, back up the world and record the Valheim version, server build, BepInEx version and installed plugins. Have all clients use the versions required by the server. If the problem disappears with the server-side mods disabled, re-enable them one at a time to identify the change responsible.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Dedicated Simulation
Dedicated Simulation is a server-side tuning option documented with queue and target-FPS controls. Its listing requires BepInExPack_Valheim 5.4.2350 or newer. That requirement is a compatibility prerequisite, not evidence that a particular target-FPS value will improve every world. Change one control, observe CPU use and player symptoms, and keep a rollback profile.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
SmoothServer
SmoothServer documents adaptive budgets, asynchronous saving and telemetry. Its repository states that it targets Valheim 1.0.14, network version 40 and BepInEx 5.4.2350. Those declarations identify the versions the project is designed for; they do not guarantee an improvement on a different game build, mod collection or world.
Safe mod rollout
- Stop the server and make a verified world backup.
- Write down the current plugin list and versions.
- Install or update one plugin only, matching its stated Valheim and BepInEx targets.
- Start the server without allowing players to make irreversible world changes until loading and logs look normal.
- Reproduce the original symptom and compare CPU, memory, save timing and network behaviour with the clean baseline.
- If errors, desynchronisation or new stalls appear, stop the server, remove the change and restore the rollback profile.
Choose a hosting arrangement based on the measured problem
| Arrangement | Compute and uptime | Network and ports | Control and troubleshooting |
|---|---|---|---|
| Home machine | You supply the hardware, power and restarts. Performance depends on what else runs on the machine. | Steam backend normally requires forwarding UDP 2456–2457; Crossplay uses a relay for outside-LAN access. | Maximum access to logs, saves and mods, but you handle firewall, backups and recovery. |
| Small Linux VPS | Provider supplies virtualised CPU, memory and data-centre power. The 2 vCPU/4 GB figure is only a community starting estimate. | Configure the provider firewall and the selected backend’s network path; latency depends on player geography and route. | Good shell-level access and repeatable snapshots, but you administer the operating system and updates. |
| Managed dedicated service | The service supplies persistent availability and server administration according to its plan. | Port-forwarding and firewall work may be reduced, depending on the backend and service design. | Convenient controls and support, with less control over the underlying host and diagnostic tooling. |
Compare these choices on four questions: who supplies compute and uptime, which network path players use, how much control you retain over saves and mods, and how much troubleshooting work you want to perform. Move to another arrangement only after measurements show that the current one is the limiting factor or that administration time is the real cost.
Symptom-based troubleshooting playbook
Everyone rubber-bands or actions arrive late
- Check whether the server process is CPU-bound or memory-starved at the exact time of the event.
- If resource use is normal, test the server and affected players without Wi-Fi, tethering, downloads or uploads.
- Confirm that Steam-backend ports are forwarded correctly, or verify that the Crossplay relay is selected when you intend to avoid forwarding.
- Review logs for mod errors and compare the server and client versions.
- Only after these checks, test a different host size or location.
One player has low FPS while others are fine
Have that player monitor local rendering and background processes, lower an appropriate graphics setting for a test, and compare the result in the same scene. A dedicated server is not a substitute for client-side graphics troubleshooting.
The whole group freezes during saves
- Correlate the freeze with the documented save and backup intervals.
- Watch disk activity and available memory while the save runs.
- Pause other disk-heavy services and test with the existing world backup.
- Change one save or backup argument, then repeat the same scenario.
Performance worsened after an update
Record the new Valheim and BepInEx versions, disable newly changed plugins, and compare with the rollback profile. A mod that targets Valheim 1.0.14 or network version 40 may require a compatibility review after a game update. Do not mix server and client plugin versions while diagnosing.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Operational checklist
- Keep a written map of each server instance, port range and world identity.
- Record CPU, memory, disk and network observations whenever a player reports a stall.
- Keep the documented backup count and intervals until testing shows a reason to change them.
- Make a world backup before every mod, BepInEx or major Valheim update.
- Change one variable at a time and retain the previous launch arguments.
- Test restoration with the server stopped instead of assuming a backup is usable.
- Ask whether the symptom is shared by all players before changing server hardware.
- Remove competing uploads and downloads before drawing conclusions from a network test.
Bottom line
The reliable way to improve Valheim server performance is a measurement-led diagnosis. Classify the symptom, observe the server and network during reproduction, verify the backend’s port or relay path, remove traffic interference, then adjust saves or mods with a tested rollback. Use 2 vCPU and 4 GB RAM only as a community starting estimate for a small Linux VPS, not as an official minimum. A dedicated server is most valuable for persistent availability and separation from a player’s game client; it cannot fix every client, connection or compatibility problem.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
