Ready to play?
Your Server Is
One Click Away.
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!
Ready to play?
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!
By Team BruceNode·June 14, 2026·5 min read·7 views
To host a Valheim dedicated server in 2026, run valheim_server through SteamCMD or a managed panel, open UDP ports 2456 to 2458, and set a password of at least 5 characters that does not match the server or world name. Budget 1 to 4 GB of RAM, and install BepInEx on the server and every client if you want mods.
A dedicated Valheim server keeps your world running whether or not the host is online, which is the whole point once your group is past the first few bosses. Setting one up is straightforward, except for two traps that stop more new admins than any hardware problem: the password rule and the world-name collision. This guide covers how to host a Valheim server in 2026, how to install mods with BepInEx, where your saves live, and the gotchas that keep a fresh server from booting.
Valheim is lighter than Rust or Palworld, but it gets heavier than you might guess as a world grows:
This is the part that wastes an evening. Valheim has two boot-blocking rules that fail quietly:
If a fresh server starts and immediately stops with no one able to join, it is almost always one of these two. Check them first, before you touch hardware or ports.
Valheim mods run on BepInEx, the standard mod loader for Unity games. The key difference from a game like Hytale, where mods stream from the server: BepInEx has to be installed on the server AND on every player's client, on the same versions, or people cannot connect.
On a managed host, steps 1 to 3 are usually a one-click BepInEx toggle in the panel.
Your world is not in the same folder as the server binary. It lives in the valheim_storage directory, alongside adminlist.txt, bannedlist.txt, and permittedlist.txt. The world itself is two files in the worlds folder: a .db file (the actual world) and a .fwl file (the metadata).
Back both up regularly. Valheim is known for occasional save corruption if the server crashes mid-write, and the .db file is your entire world. A managed host with scheduled automatic backups saves you from learning this the hard way. If you self-host, script a copy of the worlds folder on a timer.
Self-hosting through SteamCMD is free and teaches you the internals, but you own the updates, the port forwarding, the BepInEx version matching, and the backups. A managed host gives you a panel with one-click BepInEx, scheduled backups, automatic updates, NVMe storage, and DDoS protection, so you spend the evening playing rather than debugging the password trap.
For most groups, 1 to 4 GB of RAM is enough. A 2 to 3 player duo runs on 1 to 2 GB, and 4 GB comfortably handles 5 to 10 players on a normal world. Valheim's memory use grows as the map is explored, so large worlds or heavy BepInEx mod lists want 8 GB or more, and a big public community is happier on 12 GB. Start at 4 GB for a typical group and scale up only if you actually see memory pressure.
Most Valheim server headaches are not hardware, they are the password rule, the world-name collision, and mismatched BepInEx versions. Get those three right and the rest is easy. If you would rather skip the SteamCMD setup and get a one-click BepInEx panel with scheduled backups, start a Valheim server on BruceNode from $2.50/mo, with NVMe storage and DDoS protection on every plan. Use code BRUCE20 for 20% off your first month and have your world up before the next raid night.
