Valheim Server Guide: Dedicated Hosting, Crossplay and Mods

Running a stable Valheim world for ten Vikings across PC and console is the difference between a smooth raid night and a constant stream of "are you seeing this lag?" messages. Dedicated hosting takes the load off the host machine, unlocks crossplay between Steam and Xbox after the post-1.0 unified multiplayer update, and gives you proper control over the world's rules. The trade-off is configuration: ports, world modifiers, difficulty settings, and hardcore mode all live in different menus, and the wrong combination can wipe a week of progress.

This Valheim server guide walks through every decision in order — picking a host option, opening UDP 2456, choosing world modifiers, enabling crossplay, and protecting save files so a corrupted seed doesn't end your run. It assumes a fresh install but works equally well for migrating an existing world.

Choosing Your Valheim Server Hosting Option

Before touching a single config file, decide where the server actually lives. Each option has real trade-offs in uptime, admin control, and how much you can customize the experience. Most solo or small-group players start with a self-hosted option and only move to a rented host once uptime and 24/7 availability start mattering.

Self-Hosting on a Spare PC

The cheapest path is a leftover desktop or an old gaming rig running the dedicated server tool, which is free on Steam for everyone who owns Valheim. The world keeps running even when the "host" player logs off, so your friends can keep building while you sleep. Performance scales with the machine: a modern CPU comfortably handles ten players, while an older i5 starts to sweat during Plains or Mistlands raids.

Self-hosting also gives you the most control. You can edit valheim_server.cfg directly, schedule automated backups, and add server-side mods before players connect. The downsides are uptime (the server stops when the PC reboots, loses power, or drops off Wi-Fi) and bandwidth — a residential upload pipe is the usual bottleneck for ten-player worlds.

Renting a Hosted Valheim Server

A third-party host trades money for reliability. Plans start around $10/month for ten slots, include a control panel for restarting, wiping, or upgrading the world, and usually keep the box online with redundant power and a fat upload link. For groups that play three or more nights a week, the subscription pays for itself in fewer "wait, who's hosting tonight?" moments.

The trade-off is configuration depth. Hosted panels expose most of the same settings as a self-host — world name, password, world modifiers — but direct file access varies by provider. Mod support is usually possible but occasionally requires a specific tool (e.g., ValheimPlus or OdinPlus) and a plan tier that allows it.

Hosting Through the In-Game Server Browser

Valheim's built-in server list lets you create a community server without installing the dedicated tool, and friends can join by searching for the world name. It's the easiest path for casual play but the most limited: the host player must be online, configuration is restricted to the in-game menu, and you cannot easily schedule automated backups.

For most Vikings, self-hosting on a spare PC or a $10–25/month rented Valheim host both hit the sweet spot, and the SteamCMD-based configuration steps covered later in this guide (port 2456–2458 forwarding, server-adminlist.txt, world-gen modifiers) apply identically to both setups. The only meaningful difference is the backup section: dedicated hosts like BisectHosting or GPortal expose a one-click snapshot button tied to their control panel, whereas self-hosters need to schedule manual .db and .fwl copies via a cron job or a simple rsync script to a NAS or cloud bucket.

Configuring the Valheim Dedicated Server

Once you've picked a host type, the actual setup is a short sequence: install the tool, edit the config, open the right port, and verify the world is reachable. Most "my friends can't connect" issues come from a single misconfigured line in valheim_server.cfg or a router that hasn't been told to forward UDP 2456.

Installing the Server Tool

Search Steam for "Valheim Dedicated Server" and install it. The tool ships as a separate app so you can run it on a headless box without launching the game client. The first run creates a default world in the server's profile directory, which you can replace with an existing save later if you want to migrate.

If you're using a hosted provider, the panel handles installation — skip to the config section. For self-hosters, set the server to launch on boot (a simple Windows Task Scheduler task or Linux systemd unit) so power blips don't leave the world offline until you wake up.

Editing the Core Config File

Open valheim_server.cfg in a text editor. The file lives in the server install directory. The most important fields for a stable, friendly world are shown below — leave the rest at their defaults until you've tested a few sessions.

Set crossplay 1 in valheim_server.cfg to enable Xbox players — and PlayStation or Switch 2 players after the post-1.0 unified release — to join your PC-dedicated world through a single Steam-hosted instance. Because the server binary reads this flag once at launch and caches it in memory, editing the value while the dedicated server process is running has no effect; you must stop the service (or Ctrl+C the console window), confirm no orphan valheim_server.exe remains in Task Manager, and relaunch before the new setting is broadcast to the Steam networking layer. Leave crossplay 0 only if your group is exclusively PC and you want to sidestep the platform-account pairing step, which otherwise prompts connecting console users to link their Steam friend invite.

Opening UDP Port 2456

Friends outside your home network connect through your public IP, and the router needs to know which machine to hand the traffic to. Log into your router, create a UDP port forward on port 2456 to the server's local IP, and (ideally) assign the server a static DHCP lease so the IP doesn't drift.

Verify the port is open using a tool like canyouseeme.org or your provider's port-check utility. If the check fails, the most common cause is double NAT (your router behind an ISP gateway) or a firewall on the host machine itself. A community-tested port-forwarding walkthrough for the most common router brands lives on the Valheim Wiki, which is a useful sanity check before you blame the config file.

Crossplay Setup: PC, Xbox, PlayStation, and Switch 2

Valheim's 1.0 launch unified multiplayer across every supported platform, which means a single world can host PC, Xbox, PlayStation 5, and Switch 2 players at the same time. Getting crossplay working is mostly about making sure every player is on the latest patch and the server has the flag enabled.

Enabling Crossplay on the Server

Crossplay is a single line in the config, but the underlying unified multiplayer system only became fully functional after Valheim's 1.0 release in 2024, so it requires a post-1.0 dedicated server build — not the older Legacy branch that early admins may still be running.

Locate the crossplay line in the adminlist-adjacent config block near the bottom of valheim_server.cfg and flip it from 0 to 1; this single edit is what enables the unified multiplayer system to broadcast the world to PC, Xbox Series X|S, and PlayStation 5 clients simultaneously, since the post-1.0 netcode routes all connection handshakes through the same Steamworks-based relay rather than platform-locked matchmaking.

Restart the server, then check the in-game server browser — crossplay-enabled worlds are tagged with a small platform icon. According to the official Valheim page on Steam, the post-1.0 unified multiplayer system supports up to 10 players across all platforms on a single world. If the tag doesn't appear, the server is still on a pre-1.0 build or crossplay was left at the default 0.

Crossplay-Specific Caveats

Console players cannot use the server browser to discover community servers — they can only join via invite or direct IP. This means PC players hosting a public community server will only see other PC players in the list, while the same world accepts console guests if invited.

A second quirk: crossplay worlds use a unified chat filter, which is stricter than the pre-1.0 PC filter. According to community testing on r/Valheim, a few otherwise innocuous world names get rejected by the filter; if your serverName refuses to save, shorten it or remove punctuation.

If you want to bring an existing single-player world into a crossplay session, the easiest path is to drop the .db and .fwl files into the server's worlds folder, set worldName to the file's prefix, and start the server. Existing characters tied to a Steam account do not transfer automatically — players will need to create new characters in the world.

World Modifiers and Difficulty Settings Explained

Valheim's world modifiers are the rules that define how a run feels, from the pace of resource respawn to whether death wipes a character. They're set when the world is first created and a few of them can be changed later from the in-game menu, while the rest require a fresh world.

The Core World Modifier Set

When you start a new world, the "Modify World" screen exposes a long list of toggles. The five most consequential ones for a server-hosted run are below. These are the same options exposed in valheim_server.cfg once you set enableModifyWorld 1.

The vanilla valheim_server.cfg exposes a smaller subset directly; the full list of sliders (raid frequency, resource rate, build-damage modifier, etc.) lives in the in-game Modify World menu and is saved into the world's metadata when the world is generated. For full control, the Valheim Plus mod unlocks the entire set via server-side config.

Valheim Difficulty Settings Beyond Combat

The difficulty presets (Easy / Normal / Hard / Very Hard) are baked into the world at creation. They scale enemy HP, damage, and the number of stars on a hostile mob. A new server with a mixed-skill group usually starts on Normal and bumps up once everyone has Bronze-tier gear and a defensible base.

For non-combat difficulty, the world modifiers do most of the heavy lifting. No Map + Hardcore + No Boss Portals is a popular "true Viking" preset that triples the time it takes to clear a single biome and turns every death into a real decision.

Changing Modifiers After World Creation

Some modifiers can be flipped in the in-game menu (host player only): Build Mode, Passive Enemies, and the raid timer. World-wide options like No Map, Hardcore, and the boss-portal toggle are locked at creation. To change a locked modifier, the only option is a fresh world — which is why a sensible starting preset matters more than chasing a perfect one.

If your group is split on the right difficulty, run two worlds in parallel: a Normal "main" world for progression and a Hardcore "challenge" world for league nights. Players level different characters in each, and the progression world remains the safe repository for shared resources.

Hardcore Mode: Rules, Saves, and Backup Strategy

Hardcore mode is the single most destructive world modifier, so it deserves its own section. A character that dies in a hardcore world is deleted, including inventory and skill progress. The world itself survives, so other players on the server keep their characters.

How Hardcore Mode Actually Works

Hardcore applies per-character, not per-world. Enabling it when creating the world means every new character starts in hardcore rules; the modifier can be set independently of the world's other difficulty settings. There is no "downgrade" path — a hardcore character cannot be resurrected, revived, or migrated to a non-hardcore world.

Death mechanics are the same as vanilla, but the outcome is final. According to player reports on community forums, the most common hardcore deaths are fall damage during Mistlands exploration and surprise Deathsquito attacks while gathering in the Plains. Building a careful route and carrying a backup set of basic gear dramatically reduces the wipe rate.

Backup Strategy for Hardcore Servers

Backups are not optional on a hardcore server. The official approach is to copy the world files (<worldName>.db and <worldName>.fwl) while the server is stopped, then move the copy somewhere safe. Restoring a backup is the only way to recover a wiped character.

Set backupCount to 6 or higher so the rolling backup folder keeps a week's worth of saves. On a hardcore server, raising it to 12 buys you a safety net if a corrupted save isn't caught for a few days.

The Practical Hardcore Server Preset

This preset assumes a 10-player viking group committing roughly six hours weekly, with everyone online only on scheduled nights — the off-hours time lets the world rest and gives your hosting rig breathing room. It deliberately avoids the most punishing world modifiers (like noportal or deathpenalty all) so that a single bad night doesn't cascade into players quitting the long-running world. The settings below are tuned to keep the Meadows-to-Mountain progression feeling tense, not unfair, which is the sweet spot most experienced Valheim hardcore communities converge on.

• hardcore 1 in valheim_server.cfg (or set during world creation)

• passive 0 — keep enemies aggressive so deaths mean something

• nomap 0 unless the group specifically wants mapless exploration

• saveInterval 900 (15 minutes) so a hard crash loses at most a quarter-hour

• backupCount 12 with an off-site copy every Sunday

• A shared Discord channel for "I'm about to do something stupid" warnings

This combination respects the hardcore stakes while giving the group a realistic chance to recover from a corrupted world file. The single biggest mistake new hardcore hosts make is trusting the auto-save alone — a power loss between saves can corrupt a .db file, and a manual backup is the only reliable insurance.

Maintenance, Mods, and Long-Term World Health

A server that runs well on day one still needs occasional attention: restarts after patches, mod updates, and the slow drift of a world that has been played for hundreds of hours. The basics are short, but skipping them is how worlds get weird.

Patch Day Routine

When Iron Gate ships a Valheim update, the dedicated server tool usually updates alongside the client within a few hours. The server won't auto-restart, and clients on the new build can't connect to a server on the old build (or vice versa). A simple patch routine:

1. Announce a maintenance window in your group's chat.

2. Stop the server cleanly so the in-progress .db flushes.

3. Update the server tool via Steam.

4. Verify the world boots and one test player can connect.

5. Make a manual backup before opening the doors.

This is also the right moment to back up any mod configurations. Valheim Plus and similar server-side mods occasionally need to be re-applied after a major patch because their config files can be reset by an Iron Gate update.

Recommended Server-Side Mods

Server-side-only mods are the safest to install because they alter dedicated server behavior without injecting assets or scripts into each player's client folder, which means no BepInEx plugin synchronization is needed during a crossplay session. This matters most in mixed groups where two or three friends play on Xbox or PlayStation while the rest are on PC. Community-curated surveys from 2023–2024 (Nexus Mods, r/valheim) consistently rank the same three names at the top of any server-side modlist:

Client-side mods (custom textures, additional biomes) require every player to install matching versions, which gets messy fast in a ten-player group. If you want client-side content, a small set of shared mods in a shared modlist keeps the group synchronized.

Restart Schedule and World Health

A long-running world slowly accumulates temporary data: dropped items, building pieces, tamed animal spawns, and event markers. The dedicated server cleans most of this up automatically, but a weekly restart during a low-traffic hour keeps memory usage predictable and surfaces any background errors in the log.

A world that has been played for 300+ in-game days occasionally starts to show slow hitches during boss fights. The usual fix is a fresh server install with the existing world files dropped in: same world, fresh process, no accumulated cruft. According to community data, this is the single most effective maintenance action a long-term host can take.

When to Start a New World

There is no in-game way to merge two worlds, and the Mistlands and Ashlands expansions both introduced mechanics that don't exist on pre-1.0 saves. A clean post-1.0 world is the only way to access Deep North, the latest biome, and the unified crossplay features. Most groups who want a long-running world plan their seed carefully (the valheim world seed guide covers seed selection) before committing to several months of play, while smaller groups just start a new world whenever the itch strikes.

Frequently Asked Questions

How many players can join a dedicated Valheim server?

Up to 10 players per world, including the host. The dedicated server tool supports the same 10-player cap as a community server, and post-1.0 crossplay lets you fill those slots with a mix of PC, Xbox, PlayStation 5, and Switch 2 players. The cap is hard-coded into the server and cannot be raised without server-side mods.

Does enabling crossplay expose my world to public players?

No. Crossplay only changes which platforms can connect, not who is allowed to connect. A world with public 0 and a serverPassword is invite-only on every platform. Setting public 1 lists the world in the PC community server browser but does not list it in the console storefront, so console players can only join by invite or direct IP.

Can I change world modifiers after creating the world?

Some of them, yes. Build Mode, Passive Enemies, and the raid timer can be toggled from the in-game menu while a host player is online. Locked modifiers — No Map, Hardcore, and the boss-portal toggle — are baked in at world creation. To change a locked modifier, the only option is a fresh world, which is why picking the right starting preset matters.

What's the best difficulty setting for a mixed-skill group?

Normal is the consensus starting point for groups of 4–10 players with mixed experience. Easy is friendlier for casual play but makes the late-game biomes feel empty. Hard and Very Hard are designed for fully geared groups who have already cleared the boss ladder; jumping straight to Hard is a common way to lose a week's worth of progress on a Plains raid night.

How do I roll back a corrupted hardcore world?

Stop the server, locate the worlds/<name>.db and <name>.fwl files in the server install directory, and replace them with the most recent backup from your backup folder. Restart the server. The hardcore wipe is tied to the world files, so restoring a pre-death snapshot brings the deleted character back. This is exactly why off-site backups (not just rolling ones) matter on a hardcore server.