How to Make a 7 Days to Die Server, Step by Step
How to make a 7 Days to Die server: dedicated server setup with SteamCMD, serverconfig.xml settings, port 26900, admins, mods and save backups.

Contents
Making a 7 Days to Die server comes down to four steps: you download the free dedicated server files with SteamCMD, set the server options in the serverconfig.xml file, start the server and wait for the world to be created, and open the 26900 ports. On your own server, your bases and your world are always online; your friends can join whenever they want and prepare together for the blood moon on the seventh day.
This guide covers setting up a 7 Days to Die server on Linux from scratch, the most important settings, admins, the web dashboard, mods and backups.
Requirements
- Operating system: 7 Days to Die Dedicated Server runs on 64-bit Linux and Windows. We use Ubuntu and Debian in this guide.
- RAM: For a default 8-player server and a medium-sized map, 8 GB is a good start. Large maps and mods need 12–16 GB.
- CPU: On blood moon nights, the movement of hundreds of zombies and the physics of structures push the server hard. High single-core speed and at least 4 cores are recommended.
- Storage: Set aside a few tens of GB of free space for the server files, randomly generated maps and saves.
All you need to know is how to connect to a server over SSH; we give every other command step by step.
Downloading the server files with SteamCMD
For security, run the server as a separate user instead of root:
sudo apt update
sudo apt install lib32gcc-s1 curl tmux telnet
sudo useradd -m -s /bin/bash sdtd
sudo su - sdtd
mkdir ~/steamcmd && cd ~/steamcmd
curl -sqL "https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz" | tar zxvf -
The Steam app ID for 7 Days to Die Dedicated Server is 294420:
~/steamcmd/steamcmd.sh +force_install_dir /home/sdtd/server +login anonymous +app_update 294420 validate +quit
Run the same command again after every game update to keep the server up to date.
Settings with serverconfig.xml
The serverconfig.xml file that comes in the server folder can be overwritten with every update. To keep from losing your settings, make a copy and edit that instead:
cd ~/server
cp serverconfig.xml myserver.xml
nano myserver.xml
Every setting in the file has the form <property name="..." value="..."/>. The most important settings:
| Setting | What it does |
|---|---|
ServerName | The name shown in the server list |
ServerPassword | The password players need to join; if empty, anyone can join |
ServerVisibility | 2 public, 1 friends only, 0 not shown in the list |
ServerMaxPlayerCount | The maximum number of players (default 8) |
GameWorld | Navezgane for the fixed map, RWG for a randomly generated map |
WorldGenSeed | The word or number that generates the random map |
WorldGenSize | The size of the random map (for example 6144, 8192, 10240) |
GameName | The name of the save; changing it starts a new game |
GameDifficulty | The difficulty (0 easiest, 5 hardest) |
DayNightLength | The length of one in-game day in real minutes |
BloodMoonFrequency | How many days apart blood moons come |
Example:
<property name="ServerName" value="Your server name"/>
<property name="ServerPassword" value="secret123"/>
<property name="ServerVisibility" value="1"/>
<property name="GameWorld" value="RWG"/>
<property name="WorldGenSeed" value="nodesty"/>
<property name="WorldGenSize" value="8192"/>
Larger maps mean more RAM and a longer first startup. For a small group of friends, 6144 or 8192 is enough.
Starting the server
Start the server in a tmux session with your own settings file so it doesn't shut down when you close your SSH connection:
tmux new -s sdtd ./startserver.sh -configfile=myserver.xml
If you chose a random map, the world is generated on the first launch, which can take anywhere from a few minutes to half an hour depending on the map size and the CPU. Once the console shows the server is ready to accept players, you can connect. Press Ctrl + B and then D to leave the session, and use tmux attach -t sdtd to come back.
Ports and firewall
By default, a 7 Days to Die server uses these ports:
- 26900 TCP and UDP: The game and Steam query port.
- 26901–26903 UDP: Additional game traffic.
If you use ufw on Ubuntu:
sudo ufw allow 26900/tcp
sudo ufw allow 26900:26903/udp
Open the web dashboard and telnet ports (8080 and 8081 by default) only to your own IP address, not to everyone. We explain how ports work in What is a port?
Connecting to the server
In the game, go to the Join a Game screen and use the Connect to IP option to enter the server's IP address and port 26900. If the server is public, you can also search for it by name in the server list.
Admins and server management
The admin list is kept in the serveradmin.xml file in the save folder. The easiest way to make yourself an admin is through the server console. With the TelnetEnabled setting turned on, connect to the server with telnet:
telnet localhost 8081
Then add yourself at the highest permission level with your Steam ID:
admin add 76561198000000000 0
Permission level 0 is the highest. Other commonly used console commands:
| Command | What it does |
|---|---|
listplayers | Lists connected players |
kick name | Kicks a player from the server |
ban add name 1 year | Bans a player for the given length of time |
say "message" | Sends a message to all players |
saveworld | Saves the world |
shutdown | Saves the world and shuts the server down |
Always use the shutdown command to stop the server; killing the process can lose the progress made since the last save. To manage the server from your browser, turn on the WebDashboardEnabled setting and use the web dashboard.
Mods
Mods go in the Mods folder in the server folder. Mods that only change the game's XML files (modlets) usually only need to be installed on the server. Large mod packs that add new models, interfaces or code (DLLs), however, also need to be installed by every player, and the EACEnabled setting must be turned off on the server. Before using a mod, check which game version it supports; after major updates, mods need to be updated too.
Backups and updates
World and player data are kept in the save folder (on Linux, ~/.local/share/7DaysToDie/Saves by default). Before major updates, make a copy of this folder:
tar -czf ~/7dtd-backup-$(date +%F).tar.gz -C ~/.local/share/7DaysToDie Saves
Major version updates are sometimes incompatible with old worlds. Read the release notes before updating; if a new world is needed, you can start a new game by changing the GameName value and keep the old save as a backup. We cover taking regular backups that are independent of the server in our Server backups guide, and restarting the server at set times in What is cron?
Nodesty for your 7 Days to Die server
On blood moon nights, 7 Days to Die is one of the most CPU- and memory-hungry game servers. Nodesty AMD Ryzen 9 9950X VPS plans deliver smooth gameplay even during zombie hordes with single-core speeds up to 5.7 GHz, and run in Frankfurt and New York with NVMe storage, L3–L7 nShield DDoS protection and free daily backups kept for 7 days. For other games, take a look at our Palworld, Valheim and Rust guides, and for a ready-made server, check out our game server plans.
7 Days to Die is a trademark of The Fun Pimps Entertainment LLC; Steam is a trademark of Valve Corporation. Nodesty is not affiliated with or endorsed by these companies.
Frequently Asked Questions
Does it cost anything to make a 7 Days to Die server?
No. The 7 Days to Die Dedicated Server software is free and downloads anonymously with SteamCMD. You only pay for the machine that keeps the server online 24/7. Players just need to own the game.
How much RAM does a 7 Days to Die server need?
For a default 8-player server and a medium-sized random map, 8 GB is a good start. With large maps, more players and mods, the RAM requirement rises to 12–16 GB. Keep in mind that blood moon nights are the server's busiest moments.
Should I choose Navezgane or a random map?
Navezgane is the fixed map hand-designed by the developers and is the same in every game. A random map (RWG) creates a different world every time based on the seed value and adds replayability. Navezgane is a good choice for a group playing for the first time, and RWG for experienced players.
How many players can a server have?
The default limit is 8 players and is changed with the ServerMaxPlayerCount setting in serverconfig.xml. Higher values are possible, but because hundreds of zombies spawn per player on blood moon nights, crowded servers put a heavy load on the CPU.
The game was updated and we can't join the server. What should I do?
Stop the server and update it by running the SteamCMD command again. Major version updates may not be compatible with old saves; back up your save folder before updating and check the release notes to see whether a new world is needed.
Where are saves kept?
On Linux, saves are kept by default in the .local/share/7DaysToDie/Saves folder in the user's home folder, and generated random maps in the GeneratedWorlds folder. You can change this location with the UserDataFolder setting in serverconfig.xml.
About the author
Nodesty Team · Infrastructure & Support
The Nodesty team runs our servers, network and DDoS protection day to day and answers customer support requests around the clock. These guides come from that work.
Related articles

Minecraft Server Lag: Low TPS and How to Fix It
Why does your Minecraft server lag? TPS and MSPT, measuring with spark, chunk generation, view distance, entities, plugins and the fix with Aikar's flags.

Game Server Plan or VPS? Which One Should You Choose?
Game server plan or VPS? A comparison of ready-made setup, supported games, location, operating system and running multiple servers, and which to pick.

How to Make a Project Zomboid Server, Step by Step
How to make a Project Zomboid server: dedicated server with SteamCMD, admin password, servertest.ini, port 16261, Workshop mods, RAM and backups.