- Self-Hosted vs. Managed: The Honest Comparison
- Self-Hosted: Running It Yourself
- Step 1: Install SteamCMD
- Step 2: Download the Server Files
- Step 3: Configure serverconfig.xml
- Step 4: Port Forwarding
- Step 5: Launch the Server
- Step 6: Updating the Server
- The Reality of Self-Hosting
- Managed Hosting: Skip the Infrastructure
- Essential First-Time Setup
- Set Up Admin Access
- Schedule Restarts
- Test a Blood Moon
- Next Steps
Running a 7 Days to Die dedicated server gives your group a persistent world that stays online and progresses even when you’re not playing. There are two paths: run it yourself on your own hardware, or use a hosting provider. Both get you the same result - the difference is how much setup and maintenance you want to handle.
This guide covers both options, starting with the self-hosted approach so you understand exactly what’s involved.
Self-Hosted vs. Managed: The Honest Comparison
| Self-Hosted | Managed Hosting | |
|---|---|---|
| Cost | Free (uses your hardware + electricity) | $6.97+/mo (3GB+) |
| Always online | Only when your PC is on | Yes, 24/7 |
| Setup time | 30-60 minutes | Under 5 minutes |
| Port forwarding | Required | Not needed |
| Updates | Manual (SteamCMD) | One-click or automatic |
| Mod support | Full control | Full control |
| Blood moon performance | Depends on your hardware | Dedicated resources, no CPU limits |
| Backups | Your responsibility | Automatic (every 12h on WinterNode) |
| Best for | Testing, small LAN groups | Long-term worlds, groups that want it “just working” |
Self-Hosted: Running It Yourself
Step 1: Install SteamCMD
SteamCMD is Valve’s command-line tool for downloading dedicated server files. Download it from the Valve Developer Wiki.
Windows: Extract the zip, run steamcmd.exe. It will update itself on first launch.
Linux:
sudo apt install steamcmdOr download manually and extract to a directory of your choice.
Step 2: Download the Server Files
Run SteamCMD and download the 7DTD dedicated server (App ID 294420 - separate from the game):
steamcmd +force_install_dir /path/to/7dtd-server +login anonymous +app_update 294420 validate +quitThis downloads the server files to your specified directory. The download is roughly 10-15 GB.
Step 3: Configure serverconfig.xml
Open serverconfig.xml in the server installation directory with a text editor. At minimum, change these settings:
<property name="ServerName" value="Your Server Name" />
<property name="ServerPassword" value="yourpassword" />
<property name="ServerMaxPlayerCount" value="8" />
<property name="WorldGenSeed" value="YourSeed" />
<property name="WorldGenSize" value="6144" />
<property name="GameName" value="YourWorldName" />For a full settings breakdown, see our server settings guide.
Step 4: Port Forwarding
For players outside your local network, you need to forward these ports on your router:
| Port | Protocol | Purpose |
|---|---|---|
| 26900 | TCP | Game connection |
| 26900-26903 | UDP | Game data |
| 8080 | TCP | Web control panel (optional) |
| 8081 | TCP | Telnet (optional, not recommended for public) |
The process varies by router, but the general steps:
- Find your PC’s local IP address (
ipconfigon Windows,ip addron Linux) - Log into your router’s admin panel (typically 192.168.1.1 or 192.168.0.1)
- Find the port forwarding section
- Create rules for each port above, pointing to your PC’s local IP
- Save and restart the router if prompted
Players connect using your public IP and port 26900.
Firewall Configuration
Your OS firewall also needs to allow these ports. On Windows, add inbound rules in Windows Defender Firewall. On Linux, configure iptables or ufw to allow the ports.
Step 5: Launch the Server
Windows:
Run startdedicated.bat in the server directory. Or launch manually:
7DaysToDieServer.exe -quit -batchmode -nographics -configfile=serverconfig.xml -dedicatedLinux:
./7DaysToDieServer.sh -quit -batchmode -nographics -configfile=serverconfig.xml -dedicatedThe first launch will generate the world, which can take several minutes depending on map size and your CPU. Don’t interrupt this process.
Step 6: Updating the Server
When The Fun Pimps (the 7 Days to Die developers) release an update, you need to update the server files manually:
steamcmd +force_install_dir /path/to/7dtd-server +login anonymous +app_update 294420 validate +quitBack Up Before Updating
Always back up your world save before updating. Navigate to the Saves directory (inside UserDataFolder) and copy the world folder. Updates occasionally change save formats, and a backup gives you a rollback point.
The Reality of Self-Hosting
Self-hosting works well for testing and small LAN groups. For a persistent server that your group depends on, the maintenance adds up:
- Your PC needs to stay on 24/7 (electricity costs, hardware wear)
- Updates require you to be present to run SteamCMD
- No automatic backups unless you set up scripts yourself
- Port forwarding exposes your home network
- If your ISP changes your public IP, everyone loses access until you share the new one
- Blood moon performance depends entirely on your hardware - 7DTD is CPU-hungry during hordes
None of these are deal-breakers, but they’re worth understanding before committing.
Managed Hosting: Skip the Infrastructure
If the self-hosted path sounds like more than you want to deal with, a hosted server gets you running in minutes without the infrastructure overhead.
With WinterNode, the process is:
- Pick 7 Days to Die from the game page and choose your RAM
- Your server is provisioned and running within minutes
- Configure settings through the Game Control Panel
- Share the IP and port with your group
What you get:
- Server online 24/7 on dedicated hardware
- No CPU limits - blood moons get the resources they need
- Automatic backups of your server files every 12 hours with 45-day retention. See our backup system guide for details.
- File Manager and SFTP access for mods and world files
- One-click settings through the control panel
- Unmetered storage
All game servers run at $1.99/GB of RAM. A 6GB server (solid starting point for small groups) is $11.94/mo. No extra charges for CPU, storage, or features other hosts mark up. Get your 7 Days to Die server →
Essential First-Time Setup
Whether self-hosted or managed, do these things after your server is running.
Set Up Admin Access
Add your SteamID64 to serveradmin.xml to run in-game commands. Our admin setup guide walks through the process and explains the permission system.
Schedule Restarts
7DTD has a known memory leak. Set up daily restarts to keep the server running smoothly. On WinterNode, use the Schedule Manager. Self-hosted, use cron (Linux) or Task Scheduler (Windows).
Test a Blood Moon
Let the server run through at least one blood moon cycle before inviting your full group. This lets you verify performance and tweak settings without an audience.
Next Steps
Once your server is running:
- Tune your settings - Our server settings guide covers configurations by playstyle
- Enable crossplay - Playing with console friends? Our crossplay guide covers the requirements
- Add mods - Our mod guide covers overhaul mods and modlets
- Optimize for blood moons - Our blood moon performance guide covers the settings that matter most
Support is available via ticket or Discord if you run into questions.
Frequently Asked Questions
Yes. The dedicated server is available through SteamCMD and can run alongside the game client. You'll need to forward ports 26900 TCP and 26900-26903 UDP and keep the PC running for others to connect.
TCP port 26900 for the game connection, UDP ports 26900-26903 for game data, and optionally TCP port 8080 for the web control panel.
Minimum 4GB RAM (6-8GB recommended), a modern multi-core CPU with decent single-thread performance, and SSD storage. The game is particularly CPU-hungry during blood moon events.
No. The dedicated server tool is free through SteamCMD using App ID 294420. You don't need a second game license to run a server.





7 Days to Die