Valheim Dedicated Server: How to Set Up Your Own Viking World

Valheim is one of the more forgiving survival titles to host — its stylized low-poly art direction keeps hardware demands low compared to Unreal Engine 5 competitors, and Iron Gate has kept the dedicated server binary stable since launch. That said, "forgiving" doesn't mean "zero-thought" — a badly sized box will still stutter once your group starts building large bases near Mistlands, and world-save corruption from ungraceful shutdowns is a real, avoidable risk if you skip backups.

This guide covers realistic hardware sizing for Valheim specifically (much lighter than ARK or Palworld at equivalent player counts), the start_server.sh launch flags that matter, crossplay setup for Xbox/Game Pass players, BepInEx modding, and the backup habits that prevent losing a world your group has spent 100+ hours building.

Because Valheim is so much cheaper to host well than its survival-genre peers, a lot of first-time admins under-invest in the one area that actually matters: backup discipline. The game itself won't punish you with the crashes and memory pressure you'd see in ARK or Palworld, but a single corrupted world file with no recent backup can undo months of building in an instant — and that risk exists regardless of how modest your hardware is.

What Is a Valheim Dedicated Server?

It's the standalone server binary (SteamCMD app ID 896660) that runs a persistent Valheim world independent of any player hosting from their own game client. Compared to the in-game "join a friend's world" option:

• Stays online 24/7 without requiring any specific player to be logged in
• Supports the game's practical multiplayer cap more comfortably since the server isn't also rendering a player's own view
• Enables crossplay between Steam, Xbox, and Game Pass players when configured correctly
• Supports mods via BepInEx, a widely-used Unity mod loader
• Gives you control over world seed, backups, and admin/ban lists independent of any player's local files

System Requirements and Pricing

Valheim's Unity-based engine is genuinely lighter than its UE5/UE4 survival-genre peers, which shows up directly in hosting cost.

World file size (and therefore backup time and disk I/O) grows steadily as players terraform terrain and build large bases — a year-old heavily-modified world can be significantly larger than a fresh one, so don't size storage only for launch day.

Why Valheim Is So Much Cheaper to Host

Valheim's Unity-based engine renders terrain and structures with a deliberately low-poly art style, and its physics and building-integrity systems are noticeably lighter than the voxel or Nanite-driven terrain systems in ARK Ascended or Enshrouded. The practical result: a server that would need 16+ GB of RAM to comfortably host a given player count in ARK often needs a third of that in Valheim. This doesn't mean Valheim can't stutter under bad conditions — a huge, sprawling base near the world's edge still taxes physics calculations — but the baseline cost of entry is genuinely lower across the board.

Step-by-Step Setup

1. Install via SteamCMD

steamcmd +force_install_dir ./valheim +login anonymous +app_update 896660 validate +quit

1a. Choose Between the Standard and Playtest Branches

Iron Gate occasionally runs public playtest branches for major content updates before they hit the stable branch. For a community server hosting real player progress, stay on the default stable branch — playtest branches can introduce save-incompatible changes that get reworked before the final release, and a world created on a playtest build isn't guaranteed to carry forward cleanly.

2. Understand start_server.sh Flags

Valheim's server launches via a shell script with these key flags:

A typical launch command: ./valheim_server.x86_64 -name "My Viking World" -port 2456 -world "Midgard" -password "changeme123" -public 1 -crossplay -saveinterval 1800 -backups 4 -backupshort 7200 -backuplong 43200

2a. Picking a World Seed and Understanding Generation

The -world flag's name determines both the save file and, on first creation, prompts a fresh procedurally-generated map. If your community wants a specific seed (shared from a build video or a known-good layout), that has to be set at world creation time through the server's console or a companion tool — you cannot retroactively apply a seed to an already-generated world. Decide on this before your first players log in, since regenerating later means starting over.

3. Open Firewall Ports

Valheim needs UDP 2456-2457 open at minimum (2456 game, 2457 Steam query). If using crossplay, also ensure your provider doesn't block the additional platform-networking ports crossplay relies on. With UFW: sudo ufw allow 2456:2457/udp.

4. Set Up Admin and Ban Lists

Create adminlist.txt, bannedlist.txt, and permittedlist.txt in the server's save data folder, each containing Steam64 IDs (or Xbox equivalents for crossplay) one per line. Admins can use in-game console commands like kick, ban, and save once added to adminlist.txt.

5. Install BepInEx for Mods

BepInEx is the standard Unity mod-loader framework the Valheim modding community has standardized on. Install the dedicated-server-specific BepInEx pack (different from the client-side pack) into the server directory, then drop compatible server-side mods into BepInEx/plugins/. Note that many Valheim mods require matching versions on both server and client — a mismatch typically shows as a version-check disconnect rather than a crash, which is at least easy to diagnose.

5a. Popular Server-Side Mod Categories

Most Valheim communities reach for mods in a few common categories: quality-of-life mods (extended building snap points, larger stack sizes), difficulty/balance mods (adjusted portal restrictions, boss scaling for smaller groups), and world-management mods (map-sharing plugins, expanded building area limits). Start with a small, well-documented mod list rather than a large curated pack on your first server — every additional mod is one more potential source of a version-mismatch disconnect for a player who forgot to update.

6. Run as a Persistent Service

Wrap the launch command in a systemd unit with Restart=on-failure so the server survives crashes and reboots without manual intervention, running under a dedicated non-root user.

7. Automate World Backups

World saves live in .valheim_server/worlds_local/ as a pair of files (.db and .fwl) per world. Because Valheim autosaves periodically per -saveinterval, schedule a backup job that copies both files together (never just one) a few minutes after each autosave interval, keeping at least a week of rolling daily snapshots.

8. Set Up a Whitelist for Private Servers

Valheim doesn't have a first-party whitelist system baked into vanilla the way some titles do — access control is typically handled via the server password itself, kept private and shared only with invited players, or via a BepInEx mod like a Steam-ID-based allowlist for tighter control. If you want granular per-player access control, plan on a mod rather than expecting a stock config option.

9. Monitor Disk Space for Automatic Backups

Valheim's own -backups, -backupshort, and -backuplong flags create their own rolling snapshot set in addition to anything you script externally — on a long-running world, these can add up. Periodically check that old automatic backups are actually being pruned as expected rather than accumulating indefinitely and quietly filling your disk.

Common Issues and Troubleshooting

"World Corrupt, Cannot Load"

This is the scenario backups exist for. It most commonly happens after an abrupt kill (out-of-memory, host reboot without a graceful stop) mid-save. Restore the most recent known-good backup pair (.db+.fwl) rather than trying to repair a corrupted file — third-party repair tools exist but are hit-or-miss.

Crossplay Players Can't Join

Confirm -crossplay is actually present in the launch command (it's opt-in, not default) and that your hosting provider's network doesn't block the additional platform-authentication traffic crossplay needs beyond the base UDP ports.

Server Not Appearing in the Public Browser

Check that -public 1 is set and that UDP 2457 (the Steam query port) specifically is open — many admins correctly open 2456 for gameplay but forget the query port, which is what actually populates the browser listing.

Lag Spikes When Approaching Large Bases

Valheim's physics-heavy building system (structural integrity checks, piece counts) can cause localized lag near very large builds. This is engine-level and mostly unavoidable at extreme base sizes; some server communities set soft build-size guidelines to manage it.

Mod Version Mismatch Disconnects

If BepInEx mods are installed server-side, every connecting player generally needs matching mod versions client-side — keep a pinned mod list and version document for your community to avoid this recurring support question.

Server Uses More RAM Than Expected on a Modest Plan

Check whether BepInEx mods are the cause first — some quality-of-life mods cache more data server-side than their small download size suggests. Vanilla Valheim rarely needs more than the numbers in the sizing table above; a mod-heavy server is the main reason to budget extra headroom.

Portal Network Causes Performance Issues on Large Worlds

An extensive portal network with many linked pairs is lightweight individually, but very large numbers of active structures across a sprawling base network can add up. This is rarely the primary bottleneck compared to raw base size, but worth checking if performance degrades specifically as your world map grows large.

Troubleshooting Reference Table

Common Mistakes to Avoid

The most common mistake is skipping backups entirely because Valheim "feels" stable compared to other survival titles — stability doesn't protect against a bad power event or host reboot mid-save, and the backup habit matters regardless of how reliable the game itself is. A second mistake is forgetting to open the UDP query port (2457) alongside the game port (2456), which makes a perfectly functional server invisible in the public browser while direct-connect still works, causing confused troubleshooting. A third is running BepInEx mods without keeping a written, version-pinned mod list for the community, which turns "why can't I connect" into a much longer conversation than it needs to be.

Buyer's Checklist

• Valheim doesn't need much CPU/RAM compared to peers — don't overpay for a plan sized like an ARK or Palworld server
• Confirm the host supports custom UDP ports for both game and query traffic
• Check whether crossplay traffic is supported without additional blocked ports
• Verify you have shell access to edit adminlist/bannedlist files and install BepInEx directly
• Ask about automated backup scheduling or confirm you can set up your own cron-based backup job
• NVMe storage is nice-to-have here more than strictly required, given Valheim's modest I/O profile — but still improves save/backup speed on large worlds

World Modifiers and Difficulty Presets

Since the world-modifier system was added, dedicated servers can adjust difficulty without mods via launch flags — a genuinely useful option for groups who found vanilla either too punishing or too easy. The -preset flag applies a bundled difficulty package (options include casual, easy, hard, hardcore, immersive, and hammer), while -modifier adjusts individual dials like combat difficulty, death penalties, resource rates, raid frequency, and portal behavior. The -setkey flag toggles specific world rules such as removing build costs or disabling map functionality for hardcore exploration groups.

Two practical cautions: first, decide these with your community before launch, since changing death-penalty or resource-rate rules mid-playthrough reliably generates more drama than any technical problem ever will; second, document exactly which flags your launch script uses, because a server migration that silently drops a modifier flag changes gameplay in ways players notice immediately but admins struggle to diagnose from the server side.

Performance Tuning Walkthrough

Valheim rarely needs aggressive tuning, but when a long-lived world starts to feel heavy, these steps isolate the cause in the right order.

Step 1: Watch the Right Metric

Valheim's bottleneck is almost always single-core CPU, not RAM — so a monitoring graph showing plenty of free memory doesn't rule out a performance problem. Watch per-core utilization during a busy session; one core pinned near its limit while others idle is the classic signature of a world simulation hitting its ceiling.

Step 2: Identify the Heavy Bases

Instance counts from large builds drive most late-world load. If lag consistently appears when players are at or near one specific mega-base, the fix is social rather than technical: community guidelines on build density (particularly item stands, torches, and tamed-animal pens, which accumulate quietly) do more than a hardware upgrade at the extremes.

Step 3: Sanity-Check Save and Backup Timing

The periodic world save causes a brief but real pause on large worlds. If players report a rhythmic hitch, check whether it aligns with your -saveinterval — lengthening the interval slightly, or making sure your external backup job isn't copying files at the exact moment the game is writing them, smooths this out without any gameplay cost.

Step 4: Isolate Crossplay Overhead

Crossplay routes traffic through platform networking rather than pure Steam sockets, and some groups on distant continents report higher latency with it enabled. If your community is entirely on Steam, try a session with -crossplay removed — when nobody needs Xbox/Game Pass access, leaving it off removes a variable from every future network complaint.

Real-World Scenario: A Clan's Journey From Meadows to Ashlands

A typical long-running Valheim server tells a predictable load story. In the first weeks, eight players in the Meadows and Black Forest barely register on a 6 GB plan — CPU idles, the world file is tiny, and backups take seconds. By the Mountain and Plains phase, the main base has grown into a walled town with dozens of buildings, portals to every corner of the map, and breeding pens; per-core CPU during full-house evenings starts becoming visible, and the world file has grown severalfold from terraforming alone. By Mistlands and Ashlands, the clan's sprawling infrastructure means approaching the main base causes brief loading hitches for players on older clients, and the admin has tightened build guidelines and moved the backup job to run just after the autosave rather than during play. The hardware never changed — the same modest VPS carried the entire journey — but the habits around it matured. That's the realistic Valheim hosting arc: light on money, heavier on stewardship as the world accumulates history.

Frequently Asked Questions

How much RAM does a 10-player Valheim server need?

6-8 GB comfortably covers a 10-player server with normal exploration and base-building, noticeably less than equivalent player counts on ARK or Palworld thanks to Valheim's lighter engine.

Can Xbox and Steam players play on the same dedicated server?

Yes, with the -crossplay flag enabled and both platforms' networking traffic allowed through your firewall.

Why does Valheim require a server password even for public servers?

It's a built-in requirement of the dedicated server binary — even "public" browser-listed servers need a password of a minimum length, which you then share openly with your community rather than keeping private.

How do I safely change the world seed on an existing server?

You can't change a live world's seed without starting a genuinely new world file — the -world flag points to a specific save name, so create a new one if you want fresh terrain rather than editing the existing save.

Do I need BepInEx if I only want vanilla gameplay?

No — BepInEx is only needed if you're running mods. A vanilla dedicated server works fine with just the base start_server.sh and no mod loader installed.

How many rolling backups should I actually keep?

A week of daily backups plus a few longer-interval snapshots (weekly, going back a month) is a reasonable default — Valheim world files are small enough that keeping generous backup history costs very little storage compared to titles with large voxel or UE5 saves.

Can I move a Valheim world to a different server later?

Yes — copy the matching .db and .fwl pair to the new server's worlds_local directory and point -world at the same name; make sure the new server is running a compatible or newer game version before loading it.

Does Valheim support dedicated server admin commands like Java's ops system?

Yes, via adminlist.txt populated with Steam64 (or platform-equivalent) IDs — admins get access to console commands like kick, ban, and save, though the command set is more limited than a heavily-plugin-extended Minecraft server's admin toolkit.

Why does my world file keep growing even though we haven't built much recently?

Terrain modification (terraforming, mining, raising/lowering ground) accumulates in the save file even without new structures — a group that spends a lot of time reshaping terrain for aesthetics will see file growth independent of raw building activity.

Valheim rewards a server that's properly backed up more than one that's over-provisioned — the game itself is light on hardware, but losing a hand-built world to a corrupted save with no backup is the mistake that actually ruins a community's week. WebsNP's VPS hosting plans are well-suited to Valheim's modest resource needs, and our Linux dedicated servers give larger public communities dedicated cores for mod-heavy setups — reach out if you'd like help picking a plan. If your group is deciding between survival titles, see our Palworld dedicated server guide and our SteamCMD guide for the shared install workflow both games use.