7 Days to Die Servers: Dedicated, P2P and serverconfig.xml Explained

A 7 Days to Die server is either a peer-to-peer (P2P) session hosted from a player's machine — fine for 2–4 friends — or a dedicated server that runs 24/7 even when nobody's online, either self-hosted (free, via SteamCMD app 294420) or rented from a hosting provider. All of it is controlled by serverconfig.xml, the file that sets the world, difficulty, Blood Moon schedule, loot, PvP rules and crossplay. This guide covers choosing between P2P and dedicated, the settings that matter, how to install and update a dedicated server, admin setup, and the commands for the everyday admin tasks like buffing players and applying config changes.

Official resources: Steam store page · Official wiki: Server · Official wiki: Setting up a dedicated server · Official wiki: Command Console (admin commands)

P2P vs Dedicated: Which Do You Need?

The official docs recommend 8 players as the supported maximum on a server (ServerMaxPlayerCount default 8; going far past it risks save corruption). For a persistent world with strangers, admins and scheduled restarts, you want dedicated — for a weekend with friends, P2P is fine. If your group includes console players, both routes need the crossplay requirements (EAC on, vanilla, world ≤ 8192) — see the crossplay guide.

Installing a Dedicated Server (Self-Hosted)

The dedicated server is a separate, free Steam application (app 294420) — you don't need to own the game to run it. The standard install via SteamCMD:

steamcmd +force_install_dir "C:\Servers\7dtd" +login anonymous +app_update 294420 validate +quit

Linux is the same with a Linux path. The client (app 251570) and server must be on the same build — if players run V3.1 stable, the server must run V3.1. To pin another branch (experimental or an old version for a mod), add -beta <branch> to the command.

Per the official dedicated server guide: "never edit the shipped serverconfig.xml directly. The game overwrites it on every update. Put your settings in your own file and point the server at it" via the -configfile= launch argument.

Rented hosting (WinterNode, PingPerfect, 7d2d.net, GTXGaming and dozens more) skips all of this: the panel installs the server, exposes the config in a web editor, and gives you a console for commands. For most groups that aren't comfortable in a terminal, renting is the sensible path — the config knowledge below transfers either way.

The serverconfig.xml Settings That Matter

Everything below matches the current defaults documented by the official wiki and hosting-provider references (WinterNode / LOW.MS / PingPerfect), verified against V2.x-era serverconfig.xml:

The file lives in the server install root. Stop the server, edit, start — 7 Days to Die rewrites serverconfig.xml on clean shutdown, so editing a live file gets your changes overwritten.

How to Reload the Config (and What Reloads Live)

The honest answer to "how do I reload config in 7 Days to Die": serverconfig.xml changes require a restart — there is no live reload for the main config file. The sequence: say a restart warning → saveworld → cleanly shut the server down (the shutdown console command) → edit the file while it's stopped → start it again. Live-reloadable things are limited to the console commands themselves: cp list/add/remove updates command permissions instantly, admin add takes effect immediately, and the xui reload command reloads the UI without a restart. For everything else, restart.

Admin Setup and Everyday Commands

Admins are declared in serveradmin.xml (permission levels: 0 = full admin, 1000 = guest) or via the console: admin add <entityid> 0. Get IDs from lpi (list player IDs). Then the everyday commands:

The full command reference — including giveself, settime, spawnentity and the debug/creative menus — is on the console commands guide. If you're running mods, drop the mods into the server's Mods folder and keep client/server on the same branch; the mod launcher guide covers the pack side.

FAQ

How do I host a 7 Days to Die server?

For friends: host a world from the game menu (P2P). For a persistent server: install the free dedicated server via SteamCMD (app_update 294420), configure serverconfig.xml, and open TCP 26900 + UDP 26900–26903, or rent one from a hosting provider.

What are the best server settings in serverconfig.xml?

Start with the defaults: ServerMaxPlayerCount 8, WorldGenSize 6144, GameDifficulty 2, BloodMoonFrequency 7. Tune from there — lower MaxSpawnedZombies if performance sags, raise LootAbundance for friendlier groups, set PlayerKillingMode 0 for PvE.

How do I reload the config without losing changes?

You can't live-reload serverconfig.xml — stop the server, edit the file, start it again. Editing a running server's config gets overwritten on clean shutdown. Live-only tools: cp, admin, and xui reload for the UI.

How do I buff other players on my server?

Use buffplayer <entityID> <buffID> — e.g. buffplayer 171 CoffeeStaminaBoost. Get the ID from listplayerids (lpi). You need admin permission (level 0 by default for buff commands).

How do I add a friend from Steam to my 7 Days to Die server?

On PC, friends join through the server browser (search your server name) or via Steam overlay invite if you're hosting P2P. Set ServerVisibility to 1 (friends only) to hide the server from strangers, or 2 for public. Console friends join via the crossplay browser — see the crossplay guide.

Related guides: 7 Days to Die Console Commands — admin & cheat list · 7 Days to Die Crossplay — PC, PS5 & Xbox · 7 Days to Die Land Claim Block — destroy and settings · 7 Days to Die Mod Launcher — install and use · 7 Days to Die Map — Navezgane, RWG and Pregen

Last updated: August 13, 2026.

Related Guides

• 7 Days to Die Console Commands — Full Admin & Cheat List
• Is 7 Days to Die Crossplay? PC, PS5 & Xbox Guide
• 7 Days to Die Land Claim Block — Destroy & Settings Guide
• 7D2D Mod Launcher — How to Install and Use It (2026)
• 7 Days to Die Map — Navezgane, RWG and Pregen Worlds