SERVER SETUP
New here? Open The Basics first. Already know your game? Pick it below.
What a dedicated server is
A game server is a computer that keeps a game world running so other people can join it over the internet.
A dedicated server is a copy of the game made only for that job. It has no screen and no player in it. It just runs the world and lets people in.
Why not host from inside the game? Some games let you do that, but the world closes when you quit. A dedicated server stays up, so your friends can play when you are not.
That is all it is: a program on a computer that stays on.
Self-host or paid host
You have two choices for where the server runs.
Self-host means it runs on a computer at your home.
- You do not pay a host each month. You do pay for power, and the computer has to be on whenever friends want to play.
- You set up your own router (the next section explains how).
- Your friends connect to your home internet address, so only share it with people you trust.
- Your home internet speed and any limits from your ISP (internet service provider, the company you pay for internet) apply.
Things that can get in the way at home. You do not need to understand these yet. If something stops working, open the list.
Double NAT, CGNAT, DHCP and ISP limits explained
- Double NAT (double network address translation). NAT is how a router shares one internet connection between all your devices. If two routers are chained (for example, your ISP's box plus your own router), each one does this, and the doors you open on one are still shut on the other.
- CGNAT (carrier-grade NAT). Some ISPs share one public address between many homes. Then your home has no public address of its own to open doors on.
- DHCP (Dynamic Host Configuration Protocol). This is the router feature that hands out addresses to the devices in your home. It can give your server computer a new address after a restart, and then your door rule points at the wrong place. Step 3 of the next section fixes this.
- ISP limits (internet service provider limits). Some ISPs block certain doors (ports) or limit what you can open.
How to check for each of these is in the box at the bottom of Ports and port forwarding.
Paid host means you rent a server from a company.
- It is on all the time and there is no router to set up.
- Most hosts have a panel where you click to start, stop and change settings.
- You pay every month, and you are limited to what your plan allows.
Not sure which? If you do not want to touch your router, rent one. If you have a spare computer and like to tinker, self-host. Neither choice is wrong, and you can switch later.
Ports and port forwarding
Think of your home internet address as a building's street address. A port is a numbered door on that building. A game server listens at certain door numbers, and each game uses its own (the game tabs list them).
Your router is the front desk. By default it does not let strangers in. Port forwarding is telling the router: "When someone knocks on door number X, send them to the server computer."
You only need this if you are self-hosting. A paid host does it for you.
Words you will see
- IP address (Internet Protocol address): the number address of a device on a network, such as 192.168.1.20.
- Local address: the IP address your router gave a device in your home. It only works inside your home.
- Public address: the IP address your home shows to the internet. Your friends use this one.
- Router: the box that connects your home to the internet. Its own address is also called the gateway.
- LAN (local area network): your home network. WAN (wide area network): the internet side of your router.
- DHCP (Dynamic Host Configuration Protocol): the router feature that hands out local addresses.
- MAC address (media access control address, also called the physical address): a built-in ID number on every network device. Your router uses it to tell devices apart.
- TCP (Transmission Control Protocol) and UDP (User Datagram Protocol): two ways of sending data. The game tab says which one a port uses (some use both).
Where each step happens. Steps 1 and 5 happen on the server computer itself. Steps 2, 3 and 4 happen on your router's settings page, which you open in a web browser (the server computer is fine to use). Step 6 is a test with a friend. Each step tells you where you are at the top. First, we are going to find your server computer's addresses.
- On the server computer: find its addresses. You need three numbers from the computer, so write them down.
1. Press the Windows key, type cmd, and open Command Prompt.
2. Type ipconfig /all and press Enter.
3. Find the section for the connection this computer uses (a cable is Ethernet; Wi-Fi is Wireless LAN). Write down: IPv4 Address (your local address, like 192.168.1.20; IPv4 is the common version of an IP, Internet Protocol, address; ignore the word "(Preferred)" after it), Default Gateway (your router's address), and Physical Address (the MAC, media access control, address: letters and numbers).
A cable connection is usually steadier than Wi-Fi for a server. Wi-Fi and cable have different physical addresses, so write down the ones for the connection the server will use.
Next step: we leave the server computer's settings and open your router's page. - On your router's settings page: open it and log in.
1. On the server computer, open a web browser. In the address bar, type the Default Gateway number from step 1 and press Enter.
2. Log in. The login is often printed on a sticker on the router. If you changed it, use yours.
3. Some routers (certain mesh systems, for example) use a phone app instead of a web page. The same settings exist there, but the names can differ.
If the page will not open, try the address on the router's sticker, or search the router's brand and model plus "login". Do not change anything yet.
Next step: on this same page, we make sure the server computer's address never changes. - On your router's settings page: keep the server's address from changing. This is the DHCP (Dynamic Host Configuration Protocol, the router feature that hands out addresses) problem from earlier. Your router may hand the server computer a different address after a restart, which would break the rule you make in step 4. A reservation tells the router to always give this computer the same address.
1. Look for a page or section called Address Reservation or DHCP Reservation. (Different brands use different names. Search your router's brand and model plus "address reservation" if you cannot find it.)
2. Add a new reservation. Choose the server computer from the list of connected devices, or type its physical address (the MAC, media access control, address) from step 1. Use the local address the computer already has (the IPv4 Address from step 1).
3. Save or apply.
4. Restart the server computer. Then run ipconfig /all again (step 1) and check the IPv4 Address is the same. Some routers only apply a reservation the next time the computer reconnects, so this restart matters.
Next step: still on the router's page, we add the door rule. - On your router's settings page: add the port forwarding rule. This is the step that does the real work. Take it one box at a time.
1. Find the right page. Common names: Port Forwarding, Virtual Server or NAT Forwarding (NAT is network address translation, how a router shares one internet connection). If you cannot find it, search your router's brand and model plus "port forwarding".
2. Click Add (or New rule).
3. Fill in the boxes. Their names change by brand, so here is what each one means:
• Name (or description): anything you like, such as the game's name.
• Protocol: TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), or "Both". Use what the game tab lists. If the game lists both and your router has no "Both", make two rules.
• Port: some routers show two boxes, one called external (or public, or WAN: the wide area network, meaning the internet side) and one called internal (or private, or LAN: the local area network, meaning your home side). Put the game's port number in both. If there is only one box, put it once. If the game uses a range (for example 2456 to 2458), enter the first and last number.
• IP address (or device): the server computer's local address from step 1.
• Enabled: turn it on.
4. Save or apply. Some routers restart to apply the change.
5. Repeat for every port and protocol the game tab lists.
Do not use an option called DMZ (demilitarized zone) or exposed host. It opens every door on the computer, not just the game's.
If the rule is in and it still does not work, open the box at the bottom of this section.
Next step: we go back to the server computer itself. - On the server computer: allow the game through Windows Firewall. The firewall is a second guard on the computer itself. Even if the router lets a visitor in, the firewall can still turn them away. These steps are from Microsoft's own instructions for adding an inbound rule (a rule about visitors coming in).
1. Press the Windows key, type wf.msc, and press Enter. A window called Windows Defender Firewall with Advanced Security opens. If Windows asks for permission, allow it.
2. In the list on the left, click Inbound Rules.
3. In the menu at the top, click Action, then New Rule.
4. For the rule type, choose Custom, then Next.
5. On the Program page, choose All programs, then Next.
6. On the Protocol and Ports page, set the protocol to TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), whichever the game tab lists. Set the local port to the game's port number (Specific Ports, then type it; a range like 2456-2458 works). Then Next.
7. On the Scope page, leave the defaults and click Next.
8. On the Action page, choose Allow the connection, then Next.
9. On the Profile page, tick the network types the rule applies to. Windows 11 treats a new network as Public by default, so for a home server tick Private and Public. (Domain is for work networks.) Then Next.
10. Give the rule a name you will recognize, such as "Valheim UDP", then click Finish.
11. Make one rule per protocol if the game uses both, and one per separate port if the game lists several.
If you use antivirus software that has its own firewall, it has its own list. Allow the same ports there too.
Next step: the test. - Test it from outside your home.
What does your friend connect to? They connect to your home's public address, the one the internet sees, plus the port if the game asks for one. They do not use the local address that starts with 192.168 (that only works inside your home). The router receives their knock on the door and, because of the rule from step 4, passes it to the server computer.
1. Start the server (see Start your server below, or the game's own tab).
2. On any device on your home internet, search what is my IP (IP is Internet Protocol). The number it shows is your public address.
3. Check it against your router: open the router's status page (step 2) and find the Internet or WAN (wide area network) address. The two numbers should match. If they do not, open the box at the bottom of this section, because you are probably behind double NAT or CGNAT.
4. Send your friend the public address (and the port, if the game asks for it; the game tab shows how to type it in).
5. Ask a friend who is not on your home internet to try to join. Many games use UDP (User Datagram Protocol), and most port-check websites cannot test UDP, so a friend trying is the best test.
You and the people in your home join with the server computer's local address instead. Some routers cannot send you to your own public address from inside your home.
If friends who could join suddenly cannot, check your public address again. Your ISP (internet service provider) can change it from time to time.
More: if your router will not let you forward a port, or the test fails
My router won't let me forward a port, or friends still cannot join
First, the easy causes. The rule points at the wrong computer address, the type is wrong (TCP instead of UDP or the other way around), the firewall on the server computer is blocking it, or the router needs a restart to apply the rule.
Your ISP may be the problem. Some ISPs (internet service providers) block certain ports or limit what you can forward. A call or chat to them will tell you.
You may be behind double NAT or CGNAT. NAT (network address translation) is how a router shares one internet connection between your devices. Behind CGNAT (carrier-grade NAT), your ISP shares one public address between many homes. With double NAT, a second router sits in front of yours. Either way your home has no public address of its own to open doors on. With double NAT there are two walls, so the rule has to be made on the router in front too, or that router has to be switched to "bridge mode" so it stops being a second wall.
To check: find the "Internet" or "WAN" (wide area network) address on your router's status page and compare it to what a "what is my IP" website shows. If they are different, you are behind one of these. Addresses that start with 10., 192.168., 172.16 through 172.31, or 100.64 through 100.127 are private and are another sign.
What you can do: ask your ISP for a public address (some charge for it, some don't offer it), or, if a second router or modem of yours is in front, switch it to "bridge mode". If neither works, renting a server skips the problem.
RAM and CPU basics
RAM (random-access memory) is the computer's working memory. A server uses more of it as more players join, as the world grows, and as you add mods. If it runs short, the game lags or crashes.
CPU (central processing unit) is the part that does the thinking. Many game servers depend most on how fast a single core is, not on how many cores there are.
How much do you need? It depends on the game, the number of players and any mods. Each game tab and the hosting comparison show what real plans offer.
Signs you have too little: the game stutters or rubber-bands, players get kicked, or the server crashes when the world gets big. On a paid host you can usually upgrade the plan with a click.
How to see what your home server is using (Windows). Do this while the server is running with players on it. A quiet server tells you little. First, we are going to open Task Manager.
- Open Task Manager. Press Ctrl + Shift + Esc. (Or right-click the Start button and choose Task Manager.) If you only see a small window, click More details at the bottom.
Next step: we look at the overall numbers. - Look at the overall numbers. Click Performance in the list on the left. Click CPU: the big graph is how busy the processor is, as a percent. Click Memory: it shows how much of your RAM is being used.
Next step: we look at the server by itself. - Look at the server by itself. Click the Processes tab. Find the server program in the list (it is named after the game or its server tool; start the server and watch which entry appears). Click the Memory column heading to put the biggest memory users on top.
How to read it. These are rules of thumb. If Memory sits close to full while players are on, you need more RAM, or you need to close other programs. If the CPU graph is pinned at 100 percent, the processor is the limit. To check whether one core is the problem, right-click the CPU graph and choose Change graph to, then Logical processors. If one box is maxed out while the others are idle, the server is waiting on a single core.
Remember that a home server shares the computer with everything else running on it, including your own game if you play on the same machine.
You made it through the setup.
Start your server
This is the part you came for. The server is a separate download from the game you play. You download the server software, give it your settings (a name and a password), and start it. This section works for any game on Windows. Games hand out their server software in one of two main ways, so you pick the route that matches yours.
Only download server software from the game's own website or from Steam. Files from other sites can carry malware.
First, we are going to find out which route your game uses.
- Find out which route your game uses.
1. Search for the game's name plus "dedicated server". Use the game's own website or help pages, not a random site.
2. If that guide mentions Steam, SteamCMD or an app ID, use Route A, the next section.
3. If the guide says to download a file from the game's website (a .zip, an installer or a .jar), use Route B.
Next step: we pick up at the start of your route.
Route A: Steam games (SteamCMD)
SteamCMD is Valve's free, text-only version of Steam. It downloads server software straight into a folder you choose. It works the same for every Steam game, so you learn it once. These steps are for Windows. Wherever you see a capital-letter stand-in like MYGAME or APPID, type your own game's name or number instead. First, we are going to make two folders: one for SteamCMD itself and one for your server's files.
- On the server computer: make two folders.
1. Open File Explorer and go to your C: drive.
2. Make a folder named steamcmd (it will be C:\steamcmd).
3. Make a folder named servers (C:\servers). Inside it, make a folder named after your game, such as C:\servers\MYGAME (use your own game's name instead of MYGAME).
Short names with no spaces are easier to type into commands later.
Next step: we download SteamCMD into the first folder. - On the server computer: download SteamCMD.
1. Open Valve's SteamCMD page and use its Windows download link. The file is called steamcmd.zip.
2. Right-click the zip file and choose Extract All. Pick C:\steamcmd as the place to extract to.
Next step: we find your game's server number. - Find the server's app ID. Every Steam product has a number called an app ID. The server is its own product with its own number, not the same as the game's.
1. Look in the game's official dedicated server guide first. It usually gives the number.
2. If it does not, Valve keeps a Dedicated Servers List.
3. Write the number down. This is your APPID in the next step.
Next step: we download the server. - On the server computer: download the server.
1. Press the Windows key, type cmd, and open Command Prompt.
2. Type the line below and press Enter. It moves Command Prompt into the SteamCMD folder:cd C:\steamcmd
3. Type this line and press Enter. Before you do, replace APPID with your game's number and MYGAME with your folder's name:steamcmd +force_install_dir C:\servers\MYGAME +login anonymous +app_update APPID validate +quit
Here is what the finished line looks like, using made-up values: if your game's number is 999999 and your folder is C:\servers\mygame, you would type this. Use your own number and folder, not these:steamcmd +force_install_dir C:\servers\mygame +login anonymous +app_update 999999 validate +quit
What the pieces mean: force_install_dir is where the files go. login anonymous logs in without an account. app_update downloads the server (and updates it later). validate checks every file is correct. quit closes SteamCMD when it is done.
4. Wait. The first time, SteamCMD updates itself and then downloads, which can take a while. When it finishes you are back at the Command Prompt.
A few servers do not allow an anonymous login. If yours asks for an account, open the box at the bottom of this route.
Next step: we find the file that starts the server. - Find the file that starts the server.
1. Open your server folder in File Explorer (for example C:\servers\MYGAME).
2. The game's official guide names the file that starts the server. It ends in .exe (a program) or .bat (a batch file, a saved list of commands).
3. If the guide does not name one, look for a file ending in .exe or .bat with "server" in its name.
Do not start it yet. It needs your settings first.
Next step: we set the server's name and password. - Set the server's name and password. Servers read their settings from a file (or from launch options, which are extra words added to the start command). The official guide names the file and what goes in it, because every game does it differently.
1. Open the settings file with Notepad (right-click it, then Open with, then Notepad).
2. Fill in what the guide asks for. Typical settings are the server's name, a password, the world's name, and sometimes the port.
3. Use a password you do not use anywhere else. Save the file.
If the settings file is not there, the official guide says how to create it.
Next step: we start the server. - Start the server.
1. Double-click the file you found two steps ago.
2. A black window opens. This is the server's console, and it shows what the server is doing. Leave it open. Closing it stops the server.
3. If the guide lists launch options, add them as it says.
Next step: we check that it is really running. - Check that it is running.
1. Watch the console. The game's guide shows what its "ready" message looks like, because the wording is different for every game.
2. If you see an error, copy the exact words. Searching them with the game's name often finds the fix.
3. To let friends in, go back to Ports and port forwarding and finish the test in step 6.
To update later, see Keeping your server updated. Do not just rerun the long command: it has validate in it, which can overwrite settings files you changed.
More: if SteamCMD or the server will not work
"steamcmd is not recognized"
Command Prompt is not in the SteamCMD folder, or the zip was not extracted there. Type cd C:\steamcmd and press Enter, then try the long command again. Check that the folder contains steamcmd.exe.
The server asks for a Steam account
Valve says some servers do not allow an anonymous login. In that case use a Steam account made only for servers, not your main one. Steam Guard may email you a code the first time. Type your login at the prompt SteamCMD shows, and do not save the password in a script or file.
The server window opens and closes at once
Start it from Command Prompt instead, so the message stays on the screen: type cd and your server folder, press Enter, then type the file's name and press Enter. Copy the error text it shows.
Route B: games that give you a download from their website
Some games hand you the server as a file from their own website. Minecraft: Java Edition is the best-known example, so we use it to show the pattern. Other games differ in the details, so check each game's own guide. We have not tested these steps ourselves yet. First, we are going to download the official server file.
- Download the official server file.
1. On the server computer, make a folder such as C:\servers\minecraft.
2. Open the official Minecraft server download page and download the server file. It is a .jar file (a Java program file). Downloading means you agree to Minecraft's license and privacy terms.
3. Save it in the new folder.
Next step: we check that Java is installed. - Check that the right Java is installed. The Minecraft: Java Edition server runs on Java, and each Minecraft version needs a certain Java version.
1. Press the Windows key, type cmd, and open Command Prompt.
2. Type java -version and press Enter.
3. Compare the number it shows with the table on the Minecraft Wiki's server tutorial. When we checked (September 2026), it listed Java 25 for Minecraft 26.1 and newer. These numbers change with new versions, so check the table for the version you downloaded.
4. If you get an error, or the number is too old, install the Java version you need before you continue.
Next step: we run the server once to set it up. - Run it once and accept the license.
1. In Command Prompt, move into the folder:cd C:\servers\minecraft
2. Run the server. If your file is not named server.jar, use its name instead:java -jar server.jar --nogui
3. It shuts itself down right away and creates two files, eula.txt and server.properties. That is normal on the first run.
4. Open eula.txt with Notepad. Change eula=false to eula=true and save. Only do this if you agree to the Minecraft EULA (end user license agreement).
Next step: we start the server for real. - Start the server.
1. Run the same line again:java -jar server.jar --nogui
2. The first time, Windows may show a firewall prompt for "OpenJDK Platform binary". The Minecraft Wiki says that if you allow it for public and private networks, Windows manages the firewall rules for you.
3. Leave the window open. It is the server's console, and closing it stops the server.
4. The server's settings live in server.properties (open it with Notepad). The port is the server-port line, and the Minecraft Wiki lists the default as 25565.
Next step: we let friends in. - Let friends in. Go to Ports and port forwarding. In step 4, use port 25565. The Minecraft Wiki says to pick "TCP/UDP" or "Both" as the type (TCP is Transmission Control Protocol, UDP is User Datagram Protocol). Then finish the test in step 6.
Optional: a start file. To start the server with a double-click, make a new text file in the folder named start.bat (in Notepad, choose Save as, set the type to All files) with these three lines:@ECHO OFFjava -Xms1024M -Xmx2048M -jar server.jar --noguipause
The two numbers are the least and most RAM (random-access memory) the server may use, in megabytes (MB). Change them to fit your computer; see RAM and CPU.
Careful: a wrong change can stop your server working.
Changing a setting later
Game servers do not have a settings screen inside the game. Their settings live in a plain text file on the server computer. First, we are going to see the pattern, which is the same for every game.
- The pattern.
1. Stop the server. Some games lose changes made while the server is running.
2. Copy the settings file and rename the copy with today's date. That copy is your way back.
3. Open the file with Notepad, change only the value, and save.
4. Start the server and join it to check.
5. If it works, keep the new file as your backup. If not, put the old one back.
Next step: finding the file for your game. - Where each game keeps its settings.
Valheim: the long line in your copy of the start file. Dragonwilds: the file DedicatedServer.ini. 7 Days to Die: your copy of the settings file, myserver.xml. Minecraft: a file named server.properties in the server folder (the Minecraft Wiki's tutorial describes it). Each game tab has a section called Changing settings later with the exact steps and the choices we know about.
Switching hosts?
Moving your world between a paid host and your own computer
You can move a world from a paid host to your own computer, or the other way round. First, we are going to see what moving a world involves.
- A world is saved as files. Moving it means copying those files from one place to the other, then telling the new server the world's name.
- Every host has its own control panel. Look for a file manager, backups or FTP (File Transfer Protocol, a way to copy files to and from a server) page. If you cannot find it, ask the host's support how to download and upload your world.
- Stop the server first, so no file is half-written. Copy, do not move, and keep your own backup.
- Which files, and where they go, depends on the game. The game tabs for Valheim and Dragonwilds each have a section called Moving your world between a paid host and your own computer, with the exact files.
- We have not tested moving a world between a host and a home computer.
Every time a game updates, come back here.
Keeping your server updated
Games update often. When a game updates, your players' copies of the game usually update by themselves. If your server stays on the old version, it can refuse them (players may see a message about an older or incompatible version). An update can also put some of the server's files back to how they came, which can wipe out settings you changed.
This section explains how to update safely and how to keep your settings. It works for any game. Each game's tab has the exact steps for that game. First, we are going to find out which way your server gets its updates.
- Find out how your server gets updates. There are three ways. You used one of them when you set it up.
1. Installed through Steam (a tool in your Steam Library). Steam updates it, like it updates games.
2. Installed with SteamCMD (Route A above). You update it by running a SteamCMD line again.
3. Downloaded from the game's website (Route B above). You download the new file and swap it in.
Next step: before any update, we make a backup. - On the server computer: back up before you update. A backup is a copy of your files kept somewhere else, so you can put things back if an update goes wrong. Make one every time.
1. Stop the server first. Click its black console window and close it the way your game's tab says (some games need Ctrl+C so the world saves).
2. Find your world and save files. Your game's tab says where they are.
3. Find the file where you set your server's name and password. That might be a .bat file, an .ini file or a properties file, depending on the game.
4. Copy both into a new folder somewhere else, such as Documents\server-backups\2026-09-30 (use today's date). Copy, do not move.
Next step: we keep your own changes safe from the update. - Keep your settings in a file the update will not touch. The update can replace files that came with the game. Valve's SteamCMD page says that checking the files with validate "will overwrite any files that have been changed," and that files which are not part of the default installation are not affected.
1. If you edited a file that came with the server, make a copy of it with a new name and keep your changes in the copy. Start the server from your copy.
2. Keep one more copy of your edited file in your backup folder (the one from the last step).
3. After every update, open your settings file and check that your name, world and password are still there.
Next step: we do the update. - Run the update. The server must be stopped first.
1. Installed through Steam: open Steam on the server computer and go to your Library. Click the server tool. If it shows an update, let it finish. Steam also has a setting for each game or tool that controls when it updates. Right-click it, choose Properties, and look in the Updates section. The wording changes between Steam versions, so read the options and choose the one that keeps it up to date.
2. Installed with SteamCMD: open Command Prompt (press the Windows key, type cmd, open it). Type the first line and press Enter, then replace MYGAME with your server's folder name and APPID with your game's number, and press Enter on the second:cd C:\steamcmdsteamcmd +force_install_dir C:\servers\MYGAME +login anonymous +app_update APPID +quit
Use the same folder and the same number you used when you installed. They are the MYGAME folder and APPID number from Route A. Example with made-up values: steamcmd +force_install_dir C:\servers\mygame +login anonymous +app_update 999999 +quit
This line has no validate on purpose. Validate checks every file and can overwrite ones you changed. Only add it if the server is broken.
3. Downloaded from the website: download the new file from the game's website, put it in the server folder in place of the old one, and keep your world and settings files. Check the Java version too (see Route B).
Next step: we check that it worked. - Check that it came back.
1. Start the server the way you normally do.
2. Look at your settings: the server name, world and password should be yours, not the defaults.
3. Join the server from the game. If the game says the server is running an older version, the server did not update. Go back to the update step.
4. If something looks reset, open the "More" box below.
Optional: if you used SteamCMD, you can make the server update every time you start it. Open your start file (right-click it, then Edit) and put the update line from the SteamCMD step above the line that starts the server, then save. We have not tested this exact setup, so test it with a backup first.
More: if your settings or world look reset after an update
Your server name, world name or password went back to the defaults
The update probably replaced the original settings file. Your edits are not lost: open the copy you made, or the one in your backup folder, and put your name, world and password back in the file you start from. Then restart the server.
The server starts, but the world looks brand new
Most games make a new world when the world name in the settings does not match an existing one. If the settings went back to the default name, the server may have made a new, empty world. Your old world is usually still in the saves folder. Set the world name back to the old one, restart, and it should load. Do not delete anything until you have checked.
Players are told the server is on an older version
The server did not update, or was not restarted after updating. Stop it, run the update again, and start it.
The update stopped halfway or shows errors
Run the update again. If it still fails, copy the error text and search it with your game's name.
Before you start
The Valheim Dedicated Server is its own tool in Steam. It is separate from the Valheim game you play, and it has no screen. It only runs the world.
This guide is for Windows. If you are new to servers, the pieces it leans on (router, ports, firewall) are explained in The Basics.
Decide how people will join. Valheim has two ways, and the choice changes how much setup you do.
- Crossplay on. Players on any platform can join. Valheim's own guide says this mode sends data through a relay (a middle server run for the game, which the guide calls the PlayFab backend), so you do not need port forwarding. This is the easy way. Xbox players can only join with crossplay on.
- Crossplay off. Players join through Steam, and you do need port forwarding on your router.
Valheim 1.0 is also on PlayStation 5 and Nintendo Switch 2. Valheim's pages only confirm Xbox joining a dedicated server. The owner of a working server reports that Xbox, Switch 2 and PC players all join. We have not tested PlayStation 5, so check before you promise it to a friend.
First, we are going to install the server tool from Steam.
What running it at home means
The server is a program. It only works while the computer it runs on is on and online.
- The computer has to stay on. If it goes to sleep, your friends are kicked out. Open Windows Settings and search for sleep to find the setting that decides when your computer sleeps, and set it so it does not sleep while plugged in.
- Restarts stop it. Windows updates can restart the computer. After a restart, you start the server again by hand.
- It uses power and your internet. The cost is power for that computer, plus your home internet connection. Your internet provider's speed and rules apply.
- It needs some memory and processor. Example only: on the owner's small mini PC (16 GB of RAM, memory) with four players and small builds, the server used about 4% of the processor and about 11% of the memory. A bigger world and more players use more. The Basics shows how to check yours in Task Manager.
- Only share your address with people you trust. With crossplay off, friends connect to your home internet address.
If that is more than you want to take on, a paid host does all of this for you. The hosting comparison is on the Basics tab.
Install and set up the server
These steps all happen on the server computer. First, we are going to find and install the server tool in Steam.
- On the server computer: install the tool from Steam.
1. Open Steam and go to your Library.
2. At the top left of the Library there is a dropdown. Open it and make sure the Tools checkbox is ticked. Without this, the server tool is hidden.
3. Scroll the list or search for Valheim Dedicated Server. Its Steam App ID (a number Steam uses to identify it) is 896660, so if the name finds nothing, search the number. A Steam database site (SteamDB) lists it by that name as a free tool.
4. Click Install and wait for it to finish.
Next step: we open the tool's folder. - On the server computer: open the folder.
1. In your Steam Library, right-click Valheim Dedicated Server.
2. Choose Manage, then Browse local files. File Explorer opens on the tool's folder.
3. Find the file named start_headless_server.bat. A .bat file (batch file) is a small text file Windows can run as a list of commands. This one starts the server.
Next step: we make your own copy of that file. - Make a copy of the start file. Valheim's guide says to edit a copy, not the original, so you always have the original to go back to.
1. Right-click start_headless_server.bat and choose Copy. Right-click an empty space in the folder and choose Paste.
2. Right-click the new copy and rename it, for example start_my_server.bat.
Do not start the server from inside Steam. That may use the default settings instead of yours. You will start it by double-clicking your copy.
Next step: we put your server's name, world and password into the copy. - Edit your copy.
1. Right-click your copy (start_my_server.bat), choose Show more options if you see it, then Edit. Notepad opens. Do not double-click it, because that starts the server.
2. Find the long line that starts with valheim_server. It looks like the line below. Your file may have a few other switches in it (such as -nographics and -batchmode). Leave those alone.valheim_server -nographics -batchmode -name "[YourServerName]" -port 2456 -world "[YourWorldName]" -password "[YourPassword]" -crossplay
3. Change only the words inside the quotation marks. In the line above, [YourServerName], [YourWorldName] and [YourPassword] are stand-ins. Delete each stand-in, square brackets included, and type your own text between the quotes.
Here is what a finished line looks like, using made-up words. Do not copy these. Type your own name, world and password:valheim_server -nographics -batchmode -name "Bears Den" -port 2456 -world "BearsWorld" -password "grizzly42x" -crossplay
The quotation marks stay. The name is what friends see in the server list. The world name is a name you pick for the world (any short name you like). The password is what friends type to join.
4. Keep the switches exactly as they are: -name, -port, -world, -password and -crossplay. Do not delete or rename them.
What each one means: -name is what shows in the server list. -port is the door the server uses (2456 is the default). -world is the world's name (Valheim makes a new world with that name, or uses an existing one). -password is what players type to get in. -crossplay turns crossplay on.
5. The password must be at least 5 characters. Use one you do not use anywhere else.
6. To turn crossplay off, delete the word -crossplay from the line (and remember you then need port forwarding). Leave it in to keep crossplay on.
7. Save the file (Ctrl+S) and close Notepad.
8. Copy your saved file into a second folder outside Steam, such as Documents\valheim-backup. A game update can put the original start file back to its defaults, and this spare copy means you never have to retype your settings.
Next step: we let Windows Firewall know the server is allowed. - Allow the server through Windows Firewall. Windows Firewall is the part of Windows that blocks programs from reaching the internet unless you allow them.
1. The first time you start the server (next section), Windows may show a box asking if it can communicate on the network.
2. Valheim's guide says to tick all the checkboxes in that box and allow it.
3. If you closed the box without allowing it, the server will start but friends cannot get in. See the "More" box under Let friends join.
Next step: we start the server.
Install and settings are done.
Start the server
First, we are going to start the server from your copy and check that it is running.
- On the server computer: start it.
1. Open the tool's folder (see the earlier step) and double-click start_my_server.bat.
2. A black window (the server's console, which shows what the server is doing) opens. Leave it open. Closing it stops the server.
3. If Windows shows the firewall box, tick all the checkboxes and allow it.
Next step: we read the console to see that it is working. - Check that it is running.
1. Wait. The first start can take a minute while the world is created.
2. Valheim's guide says that when the console shows Game server connected, the server is up and ready for players.
3. With crossplay on, the owner of a working server reports the join code appears near that line. A join code is a short code your friends type in to find your server. Copy it. You will use it in the next section.
4. If you see an error instead, copy the exact words and search them with "Valheim server" in front.
Next step: we let your friends in.
Let friends join
What your friends do depends on whether crossplay is on. First, we are going to give them what they need to find your server.
- If crossplay is on: send them the join code.
1. Send your friends the join code from the console (see the earlier step), and the server password.
2. They start Valheim and go to Join Game, press Add server, and paste the code. This is the step Valheim's crossplay FAQ describes.
3. Valheim's guide also says players can find a public server in the server list. Servers are public by default. You can hide yours by adding -public 0 to the line in your copy.
Xbox players can only join if both the Xbox and the server have crossplay on.
Next step: if you turned crossplay off, the next step is for you. If crossplay is on, you are done with this section. - If crossplay is off: open the ports on your router.
1. This is the port forwarding steps in The Basics, under Ports and port forwarding. Do those steps there, then come back.
2. When it asks for ports, use 2456 to 2458 and the type UDP (User Datagram Protocol, one of the two ways data travels on the internet, the other being TCP). This is the setup the owner of a working server uses. Valheim's guide says the default range is 2456 to 2457, so 2458 is an extra.
3. Your friends need your public address (the Basics steps show how to find it) and the port. In Valheim they go to Join Game, press Add server, and type the address, a colon and the port, like 203.0.113.5:2456. That address is made up. Use yours.
Next step: stopping the server safely.
More: if friends cannot connect or the password is refused
An Xbox player cannot see or join the server
Valheim's crossplay FAQ says an Xbox can join a dedicated server only if both the Xbox and the server have crossplay on. Check that -crossplay is in your copy of the start file, then restart the server.
Crossplay is off and nobody outside your home can connect
Port forwarding is needed. Redo the port forwarding steps in The Basics, including the Windows Firewall rule, then test again. Also check that your computer's address did not change.
The firewall box was closed without allowing
Make a Windows Firewall rule that allows the server program, valheim_server.exe, through. The firewall step under Ports and port forwarding in The Basics shows each screen. Choose the program option and browse to the file in the tool's folder.
The password is not accepted
Make sure the password in your copy has at least 5 characters and that your friends type it exactly as written, including capital letters.
Careful: stop the server before you change anything.
Changing settings later
You do not change Valheim's server settings from inside the game. They live in the long line of your copy of the start file (start_my_server.bat) on the server computer. First, we are going to stop the server, so the change is safe.
- On the server computer: stop the server. Follow Stop it safely below (click the black window and press Ctrl+C). Valheim's guide does not say whether the server reads the file again without a restart, so always stop, change, then start.
Next step: we keep a copy of what works now. - Back up the file you have.
1. Open the tool's folder (Steam, right-click the tool, Manage, Browse local files).
2. Copy start_my_server.bat and paste it in the same folder. Rename the copy with today's date, such as start_my_server_2026-10-01.bat. Do not run this one. It is your way back if the change goes wrong.
Next step: we make the change. - Change or add a switch. Each setting is a word that starts with a dash, such as -name or -password. To change one that is already there, change the quoted words after it. To add a new one, click at the very end of the long line, type a space, then type the new switch. Example: this adds a harder difficulty to the line you made earlier:
valheim_server -nographics -batchmode -name "Bears Den" -port 2456 -world "BearsWorld" -password "grizzly42x" -crossplay -preset hard
In -preset hard, hard is the part you choose. Valheim's guide lists these choices for -preset: Normal, Casual, Easy, Hard, Hardcore, Immersive and Hammer. Type your choice in place of hard. The other words in the line above are made up. Keep your own.
Save the file (Ctrl+S) and close Notepad.
Next step: we start the server and look. - Start the server and check.
1. Double-click start_my_server.bat. Wait for Game server connected.
2. Join from Valheim and look at the result. Valheim's guide does not say whether a new difficulty changes a world that already exists, so check it in the world.
3. If it works, copy the updated start_my_server.bat into your backup folder (such as Documents\valheim-backup), replacing the old copy. If it does not, delete your edited file and rename your dated copy back to start_my_server.bat.
What else you can change (from Valheim's own guide)
- The basics. Name, world, password, port and crossplay are all in the same long line. Changing -world to a name that does not exist makes a new world.
- Hide the server from the list. Add -public 0. Valheim's guide says the server is then invisible in the list and joinable only through the Join IP button. -public 1 is the default and shows it.
- Difficulty rules. -preset (the choices are in the step above). For one rule at a time, Valheim's guide gives -modifier [Modifier] [Value], with the example -modifier raids none. Replace [Modifier] and [Value] with a pair from this list: combat (veryeasy, easy, hard, veryhard); deathpenalty (casual, veryeasy, easy, hard, hardcore); resources (muchless, less, more, muchmore, most); raids (none, muchless, less, more, muchmore); portals (casual, hard, veryhard). You can add several.
- On/off rules. -setkey [Key]. Replace [Key] with one of nobuildcost, playerevents, passivemobs or nomap. The guide's example is -setkey nomap.
- Saves. -savedir changes where the world is stored, -saveinterval changes how often it saves automatically (30 minutes is the default), and -backups controls the automatic backups. Valheim's guide has the exact values for each. It is on Valheim's support site under "A Guide to Dedicated Servers".
- Admins, bans and an allow list. Valheim's guide names three plain text files in "the default save path": adminlist.txt, bannedlist.txt and permittedlist.txt. Put one player ID per line. The format is the platform, an underscore, then the ID, and it is case sensitive, so copy it exactly as it appears. The guide says you can get the ID from the server's black window or, in the game, from the F2 panel. It does not say where that folder is exactly, so look in the save folder from the Stop section, or use File Explorer's search box. It does not say whether the server needs a restart for these, so stop and start it. Careful: the guide says that putting even one person on permittedlist.txt bans everyone else.
- Anything else. Valheim's guide is the full list. The Assistant can walk you through a setting.
Stop it safely, and where your world is saved
First, we are going to close the server the way Valheim's guide says to.
- On the server computer: stop the server.
1. Click the black console window so it is the active window.
2. Press Ctrl+C.
3. Wait for it to close by itself. Valheim's guide says it is important to close it this way, and not by clicking the X.
4. If the window will not close, or Ctrl+C does nothing, you can close it with the X in the window's top right corner. Use the X only when nothing else works. Valheim's guide recommends Ctrl+C, and the world may not get a final save, so changes since the last automatic save could be lost.
Next step: we show where your world is kept. - Know where the world is saved.
1. By default Valheim keeps its saves in AppData\LocalLow\IronGate\Valheim, inside your Windows user folder. That is the default from Valheim's guide.
2. The server saves automatically. Valheim's guide lists the default as every 30 minutes, and keeps some automatic backups.
3. To make your own backup, stop the server first, then copy the saves folder somewhere else.
Switching hosts?
Moving your world between a paid host and your own computer
Every host has its own control panel, so this section covers only the Valheim side. Whatever your host calls it, you are looking for a file manager, backups or FTP (File Transfer Protocol, a way to copy files to and from a server) page. If you cannot find it, ask the host's support how to download and upload your world. We have not tested a move. First, we are going to look at which files hold your world.
- What to move. A world is a folder named after the world, inside worlds_local in the save folder (on your computer, by default %USERPROFILE%\AppData\LocalLow\IronGate\Valheim\worlds_local). An older world is a pair of files ending in .db and .fwl. This is what we saw on a working install.
- Stop first. Stop the server on the host and on your computer (on your computer: click the console and press Ctrl+C) so no file is half-written. Copy, do not move, and keep your own backup.
- From a host to your computer. Download the world's folder from the host. Put it inside your worlds_local folder. Open your copy of the start file and make -world "..." the exact name of that folder, capital letters included. Valheim's guide says -world uses an existing world with that name. A different name makes a new, empty world. Start the server and join to check.
- From your computer to a host. Stop your server and copy the world's folder. Upload it to the host's matching save location (look for a folder called worlds_local in their file manager), then set the host's world name setting to the same name.
- If you see a new, empty world, the name did not match. The "More: if your world looks new" box in the update section covers it.
Every time Valheim updates, come back here.
After a Valheim update
Valheim updates now and then. When it does, your friends' game updates, and the server has to match. Updates can also reset files in the server tool's folder. A server owner reported that after the first update, the name, world name and password in the original start file had gone back to the defaults (the world's progress was fine). First, we are going to back up your world and settings.
- On the server computer: back up first.
1. Stop the server: click the black console window and press Ctrl+C.
2. Open File Explorer. In the address bar at the top, type %USERPROFILE%\AppData\LocalLow\IronGate\Valheim and press Enter. This is Valheim's default save folder.
3. Copy that whole folder into a backup folder somewhere else, such as Documents\valheim-backup\2026-09-30 (use today's date). Copy, do not move. Inside it, the worlds are in a folder named worlds_local. Each world is a folder named after the world. (Worlds made before Valheim 1.0 were a pair of files ending in .db and .fwl. You may still see those pairs, usually with the word backup in their names.)
4. Also copy your start file (start_my_server.bat) into the same backup folder.
Next step: we let Steam update the server tool. - Let Steam update the tool.
1. Open Steam and go to your Library. Click Valheim Dedicated Server. If it shows an update, let it finish.
2. Steam has a setting that controls when a game or tool updates. Right-click Valheim Dedicated Server, choose Properties, and look in the Updates section. The wording changes between Steam versions, so read the options and pick the one that keeps it up to date.
Next step: we check that your settings survived. - Check your settings, then start.
1. Open your copy (start_my_server.bat) with Edit, as before, and look at the line that starts with valheim_server. Your server name, world name and password should be yours.
2. If they went back to defaults, copy your saved file from the backup folder over it.
3. Double-click your copy to start the server. Wait for Game server connected.
4. Join from Valheim. If the game says the server is running an older version, the server tool did not update yet. Go back to step 2.
Next step: if your world looks new, the box below explains.
More: if your world looks new or empty after an update
The server started, but it is a brand-new world
Valheim's guide says the -world setting creates a world with that name, or uses an existing world with that name. If an update put the start file back to the defaults, the server used the default world name and made a new world. Your real world was not deleted. It is still in the save folder, in worlds_local, as a folder named after the world (an older world is a pair of files ending in .db and .fwl).
To go back: stop the server, set -world in your copy to the old world's name (the file name without the ending), save, and start again. Do not delete any world files until you have checked.
I do not remember my world's name
Look in the worlds_local folder inside the save folder you backed up. Each world is a folder, and the folder's name is the world's name. (An older world is a pair of files with the name before the .db and .fwl endings.)
Before you start
The RuneScape: Dragonwilds Dedicated Server is its own free tool in Steam. It is separate from the Dragonwilds game you play. It runs the world and shows a text window, not the game.
This guide is for Windows. If you are new to servers, the pieces it leans on (router, ports, firewall) are explained in The Basics.
What you will need.
- A Windows computer that can stay on. The official page says 64-bit Windows or Linux.
- Steam installed on that computer.
- Your Dragonwilds Player ID. It is a code that identifies you in the game. You will copy it from the game in a later step.
- Access to your router, because this server needs port forwarding (opening a door on your router for the game). Dragonwilds has no relay option like Valheim's crossplay mode, so everyone needs this step.
Friends join by searching for your world's name in the game. That is covered in Let friends join.
First, we are going to check that this computer is big enough, then install the server tool from Steam.
What running it at home means
The server is a program. It only works while the computer it runs on is on and online.
- The computer has to stay on. If it goes to sleep, your friends are kicked out. Open Windows Settings and search for sleep to find the setting that decides when your computer sleeps, and set it so it does not sleep while plugged in.
- Restarts stop it. Windows updates can restart the computer. After a restart, you start the server again by hand.
- It needs memory. The official page says 2 GB of RAM (memory) plus 1 GB for each player, and supports up to 6 players. For 6 players it lists 8 GB. The Basics shows how to check your computer's memory and see what the server is using in Task Manager.
- It uses power and your internet. The cost is power for that computer, plus your home internet connection.
- Your internet provider matters. The official page warns that every router between you and your internet provider must pass the door through, and that some providers do not allow port forwarding at all. If that is your case, the server cannot be reached from outside your home.
- Backups are on you. The official page says at-home hosting needs manual backups. The Stop section shows how.
- Only share your world with people you trust.
The other two hosting choices the official page lists
- Shockbyte. The official page names Shockbyte as its hosting partner. You rent a server and set it up in their control panel. The hosting comparison on this site is on the Hosting page.
- Cloud. You rent a computer in a data center and install the server tool yourself. The official page rates it the hardest of the three, with costs that change with the capacity you use.
If that is more than you want to take on, a paid host does all of this for you.
Install and set up the server
These steps happen on the server computer, except where one says otherwise. First, we are going to find the server tool in Steam and install it.
- On the server computer: install the tool from Steam.
1. Open Steam and go to your Library.
2. At the top left of the Library there is a dropdown. Open it and make sure the Tools checkbox is ticked. Steam hides tools unless it is ticked, and Steam files this one as a tool.
3. Search for RuneScape: Dragonwilds Dedicated Server. (The official page writes the name with a dash and an s, but Steam lists it without them.) The official page says it is a free product with the Steam App ID (a number Steam uses to identify it) 4019830.
4. If it is not in your Library, search the Steam Store for the same name, open its page, and add or install it there. It is free.
5. Click Install and wait for it to finish.
Next step: we open the tool's folder. - Open the folder.
1. In your Steam Library, right-click RuneScape: Dragonwilds Dedicated Server.
2. Choose Manage, then Browse local files. File Explorer opens on the tool's folder.
3. Look for a file named RSDragonwildsServer.exe. This is the program that starts the server. (The official page calls it RSDragonwilds.exe, but on a working install the file is named RSDragonwildsServer.exe. Do not double-click it yet.) The folder itself is named RuneScape Dragonwilds Dedicated Server, and sits in Steam's steamapps, then common folder.
4. Leave this window open. Later steps come back to it.
Next step: we tell Steam how to start the server so it shows its activity window. - Set the launch options. Launch options are extra words Steam adds when it starts a program. The official page recommends -log -NewConsole. They make the server open a text window (a console) that shows what it is doing. Without them the server may run with no window at all.
1. In your Steam Library, right-click RuneScape: Dragonwilds Dedicated Server and choose Properties.
2. On the General tab, find the box named Launch Options.
3. Click in the box and type exactly this, with the dashes and the space between:-log -NewConsole
4. Close the Properties window. Steam saves it.
Next step: we get your Player ID from the game. - Get your Player ID from the game. The server needs to know who owns it. The official page says your Player ID is at the bottom of the game's Settings Menu.
1. On the device you play Dragonwilds on, start the game and open the Settings Menu.
2. Scroll to the bottom. You will see your Player ID, with a copy button next to it.
3. Press the copy button. Paste it into a Notepad file on the server computer for now (a way to move it across, such as emailing it to yourself, works too).
4. Keep the ID. You will paste it into the server's settings file in a moment. Use your own ID.
Next step: we start the server once so it can make its settings folders. - Start the server once, to create its folders. The server keeps its settings in a folder it creates itself. We start it once so that folder exists.
1. In your Steam Library, click RuneScape: Dragonwilds Dedicated Server, then Play (the button may say Launch).
2. A text window opens. If Windows shows a box about the firewall, allow it (tick the boxes it offers). The firewall is the part of Windows that blocks programs from reaching the internet unless you allow them.
3. Wait about a minute. Two third-party guides (not Dragonwilds' own) say the server shuts itself down if your Owner ID is missing. That is normal for this first start. If the window stays open, that is fine too.
4. If the window is still open, click it and press Ctrl+C to close it. Closing it now costs you nothing, because no one has played in it yet.
5. If you see an error, copy the exact words and search them with "Dragonwilds server" in front.
Next step: we find the settings file. - Find the settings file. The official page says the file is named DedicatedServer.ini. An .ini file is a plain text file that holds settings. It sits inside the tool's folder, in RSDragonwilds, then Saved, then Config.
1. Go back to the tool's folder window (from the earlier step). If you closed it, redo it: right-click the tool in Steam, then Manage, then Browse local files.
2. Open RSDragonwilds, then Saved, then Config.
3. Look at what is inside and follow whichever fits. (On a working install, the first start made the WindowsServer folder and the file for us, so case A is the most likely.)
A. There is a folder named WindowsServer with DedicatedServer.ini inside. This is the file you edit. Go to the next step.
B. There is no WindowsServer folder, but there is a folder named Linux with DedicatedServer.ini inside. The official page says Windows needs the values copied from the Linux file into a WindowsServer folder. Right-click the Config folder, choose New, then Folder, and name it exactly WindowsServer. Copy DedicatedServer.ini from the Linux folder and paste it into WindowsServer.
C. Neither file exists. A third-party guide says this file does not exist on a fresh install. Make the WindowsServer folder as in B. Inside it, right-click empty space, choose New, then Text Document, and name it exactly DedicatedServer.ini. Windows often hides file endings, so the file can end up named DedicatedServer.ini.txt without you noticing. To see endings, click View at the top of File Explorer, then Show, then File name extensions. (If your menu looks different, search Windows Settings for "file extensions".) If Windows asks whether you are sure about changing the ending, say yes.
4. If there is no Saved folder at all, the server did not get far enough to make it. Start it once more as in the last step, close it, and look again. Also try the search box at the top right of File Explorer: search for DedicatedServer.ini while you are in the tool's folder.
Next step: we put your settings into the file. - Edit the settings file.
1. In the WindowsServer folder, right-click DedicatedServer.ini, choose Open with, then Notepad.
2. The official page lists the settings the file needs, but not the file's exact text. Two third-party guides (not Dragonwilds' own, and not tested by us) show it like this. If your file is empty, type or paste this in. If your file already has text, keep the layout it has and only fill in the values after the equals signs:[/Script/Dominion.DedicatedServerSettings]
OwnerId=[YourPlayerID]
ServerName=[YourServerName]
DefaultWorldName=[YourWorldName]
AdminPassword=[YourAdminPassword]
WorldPassword=[YourWorldPassword]
3. In that text, [YourPlayerID], [YourServerName], [YourWorldName], [YourAdminPassword] and [YourWorldPassword] are stand-ins. Delete each stand-in, square brackets included, and type your own value in its place. Do not add quotation marks.
Here is what a finished file looks like, using made-up words and a made-up ID. Do not copy these. Use your own Player ID, name, world and passwords:[/Script/Dominion.DedicatedServerSettings]
OwnerId=A1B2C3D4E5F60718293A4B5C6D7E8F90
ServerName=Bears Den
DefaultWorldName=BearsWorld
AdminPassword=ironladder77
WorldPassword=grizzly42x
Your file may also hold lines you did not type, such as PlatformPolicy=Crossplay, ServerGuid and bAllowSendingCrashDumps. The server writes those. Leave them alone. On a working install the file the server made had no AdminPassword line. The official page lists it as mandatory, so add that line yourself, on its own line under the [/Script/Dominion.DedicatedServerSettings] line, as in the example.
4. What each setting means:
OwnerId is the Player ID you copied from the game. It is mandatory. Paste it exactly.
ServerName is a label for your server. It is mandatory.
DefaultWorldName is the name of the world the server makes the first time. It is mandatory. Your friends will search for this name to find your world, and the official page says the search is case-sensitive, so capital letters matter.
AdminPassword is mandatory. The official page says people who enter it become Admins. Keep it to yourself.
WorldPassword is optional. It is what players type to join. Leave the value empty (nothing after the equals sign) for no password. A third-party settings guide says an empty value means anyone can join. We have not tested it.
5. The official page does not give password length or character rules. As our own cautious tip, use letters and numbers only. Make the two passwords different, and different from your other passwords.
6. Save the file (Ctrl+S) and close Notepad.
7. Copy your saved file into a second folder outside Steam, such as Documents\dragonwilds-backup. An update could change files in the tool's folder, and this spare copy means you never have to retype your settings.
The official page also warns: if you change this file while the server is running, the changes are lost. Always stop the server first.
Next step: we start the server for real.
Installed with SteamCMD instead, or starting from the .exe
- SteamCMD. SteamCMD is Valve's text-only tool for installing servers; The Basics explains it. The official page gives this line, where C:\MyInstallFolder is the folder you want the server in:
steamcmd +force_install_dir C:\MyInstallFolder +login anonymous +app_update 4019830 +quit
Replace C:\MyInstallFolder with a real folder, such as C:\servers\dragonwilds. Then RSDragonwildsServer.exe is in that folder instead of Steam's. - Starting from the .exe. The official page says you can run the server program from the tool's folder. On a working install it is RSDragonwildsServer.exe. To add the launch options without Steam, right-click the file, choose Show more options if you see it, then Create shortcut (or Send to, then Desktop (create shortcut)). Right-click the shortcut, choose Properties, and in the Target box add a space and -log -NewConsole after the last quotation mark. Click OK, then double-click the shortcut to start.
Install and settings are done.
Start the server
First, we are going to start the server with your settings and check that it shows up in the game.
- On the server computer: start it.
1. In your Steam Library, click RuneScape: Dragonwilds Dedicated Server, then Play (or Launch).
2. The text window opens. Leave it open. Closing it stops the server.
3. Wait a minute or two. The first start with your settings makes your world.
Next step: we check that it is really up. - Check that it is running. No Dragonwilds page says what the window prints when the server is ready, so we use a real test instead of a message.
1. Check the window is still open and has not closed itself. If it closed, the likely cause is a missing or misspelled setting. Go back to the settings file and check every value after the equals signs, especially OwnerId.
2. On a computer or console with Dragonwilds, open the game and go to Worlds. Open the Public tab and search for your world name, typed exactly as in the file, capitals included. This is the way the official page says players find a server.
3. If your world appears, the server is up. If it does not, wait another minute and search again, then open the "More" box in the next section.
4. Seeing your world in the list only proves the server is running. Friends outside your home still need the router step in the next section before they can get in.
Next step: we let your friends in.
Let friends join
The official page says the server's door has to be reachable from outside your home. First, we are going to open that door on your router.
- Open the port on your router, and allow it in Windows Firewall.
1. This is the port forwarding steps in The Basics, under Ports and port forwarding. Do those steps there, then come back.
2. When it asks for the port, use 7777 and the type UDP (User Datagram Protocol, one of the two ways data travels on the internet, the other being TCP). The official page says Dragonwilds uses UDP ports starting at 7777.
3. Make the matching Windows Firewall rule too. The same section shows each screen. Name the rule something you will recognize, such as "Dragonwilds UDP". The official page names the firewall, the router and the internet provider as the three places the port must be open.
4. You do not need to send friends your public address or a port number. Skip that part of the Basics steps. Dragonwilds players find servers by name in the game, as the next step shows.
Next step: we tell your friends how to find the world. - Tell your friends how to join.
1. Send them two things: your world name (the value you set for DefaultWorldName, with the exact capital letters) and the world password if you set one. Send the password privately, not in a public chat.
2. They start Dragonwilds and open Worlds, then the Public tab.
3. They search the exact world name. The official page says the search is case-sensitive.
4. They pick the world, type the password if asked, and choose a character. The Public-tab steps are from the official page. The character step is from a third-party guide.
5. The search is for the world name, not the server name. If friends search the server name, they will not find it.
6. Do not use Steam Invites. The official page lists this as a known issue: inviting a player to your dedicated server through Steam "doesn't currently connect as intended".
Which devices? The official page does not mention consoles. Third-party guides say PC, Xbox, PlayStation 5 and Nintendo Switch 2 all join with the same steps, and that consoles cannot host. A server owner reports their group played from Xbox on a rented server. We have not tested a home server with a console.
Next step: stopping the server safely.
Owner, Admin and regular players (what each can do)
- Owner. This is the player whose Player ID is in the settings file. The official page says the Owner can ban and unban anyone.
- Admin. Anyone who enters the admin password. The official page says Admins can ban regular players who are online, and cannot unban.
- Regular players. Everyone else.
- The official page does not say where in the game someone types the admin password. A third-party settings guide says the admin password gives access to a Server Management tab in the game. Do not give the admin password to anyone you do not trust to ban players.
More: if friends cannot find the world or cannot join
The world does not show up when you search
Check these in order. First, that the text window is still open on the server computer. Second, that the name you search is exactly the DefaultWorldName in your settings file, capitals included. Third, that the server was stopped before you last saved the settings file (changes made while it runs are lost, says the official page). Fourth, that the game and the server are on the same version (see the update section).
Friends can see the world but cannot join
A third-party guide says this points to port forwarding. Redo the port forwarding steps in The Basics for UDP 7777, including the Windows Firewall rule. Check that your server computer's address did not change. The official page also says every router between you and your internet provider needs the rule, and that some providers block port forwarding. The Basics section has a box on double NAT and CGNAT.
The window closes by itself right after starting
Third-party guides say the server stops if the OwnerId is missing. Open the settings file and check that OwnerId has your Player ID after the equals sign and nothing else. If you edited a copy in the wrong folder, redo the "Find the settings file" step.
The world disappeared after a game update
The official page says this is likely after an update or hotfix, because the server and the game no longer match. See the update section.
A friend used Steam Invites and it did not work
This is a known issue on the official page. Have them use the Worlds, Public tab and world name instead.
I want to look at the server's log
The window shows it live. Log files are kept in the Logs folder inside RSDragonwilds, then Saved, in the tool's folder, in a file named RSDragonwilds.log. If you ask for help, copy the last lines from there.
Careful: stop the server before you change anything.
Changing settings later
You change Dragonwilds' server settings in a file on the server computer, DedicatedServer.ini, not from inside the game. The official page warns that if you change that file while the server is running, the changes are lost. First, we are going to stop the server.
- On the server computer: stop the server. Follow Stop it safely below. Ask everyone to leave first.
Next step: we keep a copy of what works now. - Back up the file you have.
1. Open the tool's folder (Steam, right-click the tool, Manage, Browse local files), then RSDragonwilds, Saved, Config, WindowsServer.
2. Copy DedicatedServer.ini into your backup folder (such as Documents\dragonwilds-backup) and rename the copy with today's date, such as DedicatedServer_2026-10-01.ini.
Next step: we make the change. - Change the value.
1. Right-click DedicatedServer.ini, choose Open with, then Notepad.
2. Find the line for the setting. Each line is the setting's name, an equals sign, and its value. Change only what is after the equals sign. For example, to change the password friends type, change the value on the WorldPassword line:WorldPassword=[NewPassword]
Replace [NewPassword] with the new password you want, for example pinecone55 (made up, so choose your own). No quotation marks and no spaces.
3. Save (Ctrl+S) and close Notepad.
Next step: we start the server and check. - Start the server and check.
1. Start it from Steam as before.
2. Search for your world in Worlds, then the Public tab, and join. Use the new password if you changed it.
3. If it works, copy the new DedicatedServer.ini into your backup folder. If it does not, copy your dated backup over it.
What you can change (and what we do not know)
- ServerName. The label of your server. Safe to change.
- DefaultWorldName. Careful. The official page calls this the name for the world made automatically. A third-party guide says it is the world created on first startup if no save exists. So changing it to a name that has no save file likely makes a new, empty world. To get your old world back, change it back to the old name exactly, capital letters included.
- WorldPassword. What players type to join. A third-party guide says empty means anyone can join.
- AdminPassword. Gives admin powers to anyone who enters it. A third-party guide says it opens a Server Management tab in the game. Keep it private.
- OwnerId. The Player ID of the owner. Change it only if the owner changes. Paste the new one exactly.
- Number of players. A third-party guide says the limit is 6 by default and cannot go higher. It does not give the exact line to use. On a working install the file the server made had no such line, so we cannot tell you the exact spelling. The Assistant can help here.
- The port. The official page says ports start at 7777 (UDP). A third-party guide says you can change it by adding -port=[YourPort] to the launch options in Steam (the same box where you typed -log -NewConsole), with a space before it. Replace [YourPort] with a number such as 7778. If you change it, change the router and Windows Firewall rules to match (see the ports step). We have not tested this.
- Difficulty and gameplay rules. We did not find any dedicated-server setting for these in the official page or the guides we read. If you need one, ask the Assistant, and tell it what you want to change.
Stop it safely, and where your world is saved
No Dragonwilds page says how to shut the server down. First, we are going to close it in the way that works for most programs in a text window, and we say plainly that this part is our own suggestion.
- On the server computer: stop the server.
1. Ask everyone to leave the world first.
2. Click the text window so it is the active window.
3. Press Ctrl+C. This is a common way to close a program in a text window. It is not from Dragonwilds' page.
4. Wait for the window to close by itself.
5. If it does not close after a minute, or Ctrl+C does nothing, close the window with the X in its top right corner. A server owner reports the X works when it is the only option. It may skip a final save, so back up first when you can.
Next step: we show where your world is kept and how to back it up. - Know where the world is saved, and back it up.
1. The official page says saves are in RSDragonwilds, then Saved, then SaveGames, inside the tool's folder. Open the tool's folder as before (Steam, right-click the tool, Manage, Browse local files).
2. The saves are files ending in .sav. On a working install the save was named after the world (a world called BearsWorld would be BearsWorld.sav), and the server kept a second copy ending in .sav.backup beside it. That copy is not a replacement for your own backup.
3. To back up: stop the server first, then copy the files in SaveGames into a folder elsewhere, such as Documents\dragonwilds-backup\2026-10-01 (use today's date). Copy, do not move. The official page says you can rename the copies so you remember which is which.
4. Also copy your DedicatedServer.ini into the same backup folder.
5. Back up regularly. The official page says at-home servers need manual backups.
Next step: if you ever need to put a backup back, the box below explains.
How to put a backup back
- The official page says the server loads the latest .sav file when it starts. It does not say how it decides which is latest, so do not leave several saves in the folder if you can avoid it.
- Stop the server. In SaveGames, move every .sav file into a spare folder (move, not delete). Copy the one you want from your backup into SaveGames. Start the server.
- This is our reasoning from the official wording, not a tested method.
Switching hosts?
Moving your world between a paid host and your own computer
Every host has its own control panel, so this section covers only the Dragonwilds side. Whatever your host calls it, you are looking for a file manager, backups or FTP (File Transfer Protocol, a way to copy files to and from a server) page. If you cannot find it, ask the host's support how to download and upload your world. We have not tested a move. First, we are going to look at which files hold your world.
- What to move. A world is one file ending in .sav, in RSDragonwilds\Saved\SaveGames. On a working install the file name, the save's slot name and the DefaultWorldName setting were all the same word (a world called BearsWorld would be BearsWorld.sav). The server also keeps a .sav.backup beside it; you do not need to move that.
- Stop first. Stop the server on the host and on your computer so no file is half-written. Copy, do not move, and keep your own backup.
- From a host to your computer. Download the .sav file from the host (the official page puts saves in RSDragonwilds/Saved/SaveGames, so look for that folder in the host's file manager). Stop your server. Move any other .sav files out of your SaveGames folder into a spare folder, because the official page says the server loads the latest .sav. Put the downloaded file in SaveGames. Open DedicatedServer.ini and set DefaultWorldName to the file's name without .sav, capital letters included. Make sure OwnerId is your own Player ID. Start the server and search for the world in the game, as in Let friends join. Copying a host's file this way is our reasoning from the working install, not a tested move.
- From your computer to a host. Copy the .sav file from SaveGames, upload it to the host's save folder, and set the host's world name setting to the file's name without .sav.
- If you see a new, empty world, the name did not match. See the "More: if your world looks new" box in the update section.
Every time Dragonwilds updates, come back here.
After a game update
Dragonwilds updates and gets hotfixes (quick fixes). When it does, your friends' game updates, and the server has to match. The official page says that if you stop seeing your server, check in the logs that the server's version matches the game's, and that this is likely after any update or hotfix. A third-party guide says the versions must match exactly. First, we are going to back up your world and settings.
- On the server computer: back up first.
1. Stop the server (see the Stop section).
2. Copy the files in RSDragonwilds\Saved\SaveGames into a backup folder, such as Documents\dragonwilds-backup\2026-10-01 (use today's date).
3. Copy DedicatedServer.ini into the same backup folder.
Next step: we let Steam update the server tool. - Let Steam update the tool.
1. Open Steam and go to your Library. Click RuneScape: Dragonwilds Dedicated Server. If it shows an update, let it finish.
2. Steam has a setting that controls when a game or tool updates. Right-click the tool, choose Properties, and look in the Updates section. The wording changes between Steam versions, so read the options and pick the one that keeps it up to date.
Next step: we check that your settings survived. - Check your settings, then start.
1. Open the tool's folder and go to RSDragonwilds, then Saved, then Config, then WindowsServer. Open DedicatedServer.ini with Notepad. Your Player ID, names and passwords should be yours.
2. If they are gone or look like defaults, stop the server if it is running, and copy your saved file from the backup folder over it.
3. Also check that the Launch Options are still there (right-click the tool, Properties, General). They should read -log -NewConsole.
4. Start the server and look for your world in Worlds, then the Public tab, as before.
5. If you cannot find it, the usual cause is a version mismatch. Check that the tool finished updating, then check again. The log window shows the version the server runs.
Next step: if you installed with SteamCMD, the box below shows that route. If your world looks new, the "More" box at the end explains.
Installed with SteamCMD? How to update that way
- A third-party guide says to re-run the install line after every game update. Use the same folder you installed into, and no validate word (validate can overwrite files you changed; The Basics has the details):
steamcmd +force_install_dir C:\MyInstallFolder +login anonymous +app_update 4019830 +quit - Replace C:\MyInstallFolder with the folder you used the first time, for example C:\servers\dragonwilds.
- Then check your settings file and start the server as in the steps above.
More: if your world looks new or empty after an update
The server started, but it is a brand-new world
Your real world was not deleted by joining a new one. Your old save is still in RSDragonwilds\Saved\SaveGames as a .sav file, and your backup folder has a copy. The official page says the server loads the latest .sav file. If an update put your settings back to defaults, the server may have made a new save, and that new save could be the one it loads. We have not seen this happen. It is our reasoning from the official wording.
To go back: stop the server. Fix DedicatedServer.ini from your backup. Then use the "How to put a backup back" box in the Stop section to leave only your old save in the folder. Do not delete any save files until you have checked.
I do not remember my world's name
Look at your backed-up DedicatedServer.ini for DefaultWorldName. Your friends can also tell you what they searched for.
Before you start
The 7 Days to Die Dedicated Server is its own free tool in Steam. It is separate from the 7 Days to Die game you play. It has no game screen. It runs the world.
This guide is for Windows. If you are new to servers, the pieces it leans on (router, ports, firewall) are explained in The Basics.
What you will need.
- A Windows computer that can stay on.
- Steam installed on that computer.
- Access to your router, because this server needs port forwarding (opening doors on your router for the game).
Decide who will play. It changes a few settings.
- PC players only. This is the easy way. Players on a PC can join with the default settings.
- Console players too (Xbox Series X|S or PlayStation 5). 7 Days to Die has crossplay, but consoles are picky. The official crossplay page lists extra rules: the server must have crossplay on, anti-cheat on, no more than 8 players, and some game settings kept inside set limits. Those rules are in the "Let friends join" section.
If you have only hosted this game from your own console, a dedicated server is different. The game runs on a separate computer, and you and your friends all join it from the game.
First, we are going to install the server tool from Steam.
What running it at home means
The server is a program. It only works while the computer it runs on is on and online.
- The computer has to stay on. If it goes to sleep, your friends are kicked out. Open Windows Settings and search for sleep to find the setting that decides when your computer sleeps, and set it so it does not sleep while plugged in.
- Restarts stop it. Windows updates can restart the computer. After a restart, you start the server again by hand.
- It needs memory and processor power. The guides we found disagree. One third-party guide lists a bare minimum of 2 GB of RAM (memory) and another says 4 fast processor cores and 6 GB of RAM, with more for modded games and more players. Bigger worlds and more players need more. The Basics shows how to check your computer and see what the server is using in Task Manager.
- It uses power and your internet. The cost is power for that computer, plus your home internet connection.
- Your internet provider matters. Some providers do not allow port forwarding. The Basics tab explains how to check.
- Only share your server with people you trust.
If that is more than you want to take on, a paid host does all of this for you. The hosting comparison is on the Hosting page.
Install and set up the server
These steps happen on the server computer. First, we are going to find the server tool in Steam and install it.
- On the server computer: install the tool from Steam.
1. Open Steam and go to your Library.
2. At the top left of the Library there is a dropdown. Open it and make sure the Tools checkbox is ticked. Steam hides tools unless it is ticked.
3. Search for 7 Days to Die Dedicated Server. Its Steam App ID (a number Steam uses to identify it) is 294420, so if the name finds nothing, search the number. A Steam database site (SteamDB) lists it by that name as a free tool. The game you play is a different one, 251570.
4. If it is not in your Library, search the Steam Store for the same name, open its page, and add or install it there. It is free.
5. Click Install and wait. The download is large, so give it time.
Next step: we open the tool's folder. - Open the folder.
1. In your Steam Library, right-click 7 Days to Die Dedicated Server.
2. Choose Manage, then Browse local files. File Explorer opens on the tool's folder.
3. Find two files: startdedicated.bat and serverconfig.xml. A .bat file (batch file) is a small text file Windows can run as a list of commands. This one starts the server. An .xml file is a plain text file that holds settings, and serverconfig.xml holds your server's settings.
4. Leave this window open. Later steps come back to it.
Next step: we make your own copy of the settings file. - Make your own copy of the settings file. Two third-party guides say an update overwrites the shipped serverconfig.xml, so they tell you to keep your settings in a copy with a different name.
1. Right-click serverconfig.xml and choose Copy. Right-click an empty space in the folder and choose Paste.
2. Right-click the new copy and rename it myserver.xml.
3. Leave the original alone, so you can always go back to it.
Next step: we put your server's name and password into the copy. - Edit your copy.
1. Right-click myserver.xml, choose Show more options if you see it, then Edit. Notepad opens. (If your menu has no Edit, choose Open with, then Notepad.)
2. The file is long. It is a list of lines that each start with <property. Press Ctrl+F in Notepad to open a search box, type a setting's name such as ServerName, and press Enter to jump to its line.
3. Each line looks like the one below. The word after name= is the setting. The word between the quotation marks after value= is what you change:<property name="ServerName" value="[YourServerName]"/>
In that line, [YourServerName] is a stand-in. Delete the stand-in, square brackets included, and type your own text between the quotation marks. Keep the quotation marks, the /> at the end, and everything else on the line.
4. Change these six settings. Each is found the same way (search for its name):
ServerName is what friends see in the server list.
ServerPassword is what friends type to join. Third-party guides say it is empty by default, which means no password. We have not confirmed any length or character rules. As our own cautious tip, use letters and numbers only, and one you do not use anywhere else.
GameName is the name of your save. A third-party forum post says a new GameName makes a new save folder, so pick a name now and keep it. Use letters and numbers only.
GameWorld is the map. Third-party guides give the choices as Navezgane (the game's hand-made map) or RWG (random world generation, where the game builds a new random map for you).
WorldGenSeed is a word the game uses to build the random map. It only matters if GameWorld is RWG. The same seed gives the same map.
ServerMaxPlayerCount is how many players can be on at once. A third-party guide says it ships set to 8.
Here is what the finished lines look like, using made-up words. Do not copy these. Type your own:<property name="ServerName" value="Bears Den"/>
<property name="ServerPassword" value="grizzly42x"/>
<property name="GameName" value="BearsWorld"/>
<property name="GameWorld" value="RWG"/>
<property name="WorldGenSeed" value="bearseed"/>
<property name="ServerMaxPlayerCount" value="8"/>
5. Leave ServerPort as it is (26900 is the usual). If you change it later, the ports in the router step change too.
6. Some lines in this file may be wrapped in <!-- and -->. Those marks mean the game ignores the line. A third-party forum post says to delete the marks to turn a line on. Leave them alone unless you are turning a line on on purpose.
7. Save the file (Ctrl+S) and close Notepad.
Next step: we make your own copy of the start file, so it uses your settings. - Make your own copy of the start file, and point it at your settings.
1. Right-click startdedicated.bat, choose Copy, then paste in an empty space. Rename the copy start_my_server.bat.
2. Right-click the copy, choose Show more options if you see it, then Edit. Do not double-click it, because that starts the server.
3. Look for the text -configfile= in the file. A third-party guide shows a start line like this one:start 7DaysToDieServer -logfile "output_log.txt" -quit -batchmode -nographics -configfile=myserver.xml -dedicated
Your file may not look exactly the same, and that is fine. The only change you make is to the file name after -configfile=. If it says serverconfig.xml, change that name to myserver.xml. If your line has no -configfile= part at all, add -configfile=myserver.xml just before the word -dedicated. The same guide says -dedicated must stay last on the line.
4. Save the file (Ctrl+S) and close Notepad.
5. Copy myserver.xml and start_my_server.bat into a second folder outside Steam, such as Documents\7dtd-backup. An update can change files in the tool's folder, and these spare copies mean you never have to retype your settings.
Next step: we let Windows Firewall know the server is allowed. - Allow the server through Windows Firewall. Windows Firewall is the part of Windows that blocks programs from reaching the internet unless you allow them.
1. The first time you start the server (next section), Windows may show a box asking if it can communicate on the network.
2. Tick the checkboxes it offers and allow it.
3. If you closed the box without allowing it, the server will start but friends cannot get in. See the "More" box under Let friends join.
Next step: we start the server.
Make the game your own: zombies, loot, damage, difficulty and more
- 7 Days to Die lets you tune your server a lot: how many zombies there are and what kind, how much you get from things you gather, how much damage you take and give, day length, and many more. The official version 3.0 release notes say the game now has 150 sandbox options. It is up to you how far to go. This guide does not cover individual settings.
- Where they live now. The official release notes say many of the older settings that used to be separate lines in serverconfig.xml were moved into a single line named SandboxCode. A code is a short string of letters. Its default is AAAJABJACJADJARFBNC. If the line is missing or left at the default, the official notes say it uses the default ruleset, so a harder game you were used to may start easier.
- How to set it. The official release notes say to open the game's Sandbox Options menu, set each option the way you want, and copy the code the game gives you. Then, in myserver.xml, find the SandboxCode line and paste the code between the quotation marks after value=:
<property name="SandboxCode" value="[YourSandboxCode]"/>
Replace [YourSandboxCode] with the code you copied. A code looks like AAAJABJACJADJARFBNC. That one is the default, shown only so you know what a code looks like. Use your own. We do not know the exact menu path to the Sandbox Options screen. One third-party guide says it is on the new-game screen. - Achievements. A server owner reports that most of these settings do not stop the normal achievements. We have not checked which settings might, so look at the game's own screens for any warning before you change a lot.
- Console players. If you want console players, the official crossplay page limits some settings. See the "Console players" box in the next sections.
- Old settings. If you are using a world and settings from before version 3.0 (version 2.6 or older), the official release notes say to recreate the old settings in the Sandbox Options menu and paste the code in, as above.
Installed with SteamCMD instead
- SteamCMD is Valve's text-only tool for installing servers; The Basics explains it. Third-party guides give this line, where C:\servers\7dtd is the folder you want the server in:
steamcmd +force_install_dir "C:\servers\7dtd" +login anonymous +app_update 294420 +quit
Replace C:\servers\7dtd with a real folder if you want a different one. The third-party guides add the word validate before +quit. It is not needed to install, and for updates the Basics tab warns that it can overwrite files you changed. - Then the files from the steps above are in that folder instead of Steam's.
Install and settings are done.
Start the server
First, we are going to start the server from your copy and check that it shows up in the game.
- On the server computer: start it.
1. Open the tool's folder (see the earlier step) and double-click start_my_server.bat.
2. A black window (the server's console, which shows what the server is doing) opens. Leave it open. Closing it stops the server.
3. If Windows shows the firewall box, tick the checkboxes and allow it.
4. Wait. A third-party guide says the first start can take a few minutes, and a random map takes longer to build.
Next step: we check that it is really up. - Check that it is running. No 7 Days to Die page we found says what the window prints when the server is ready, so we use a real test.
1. Check the window is still open and has not closed itself. If it closed, the likely cause is a typo in myserver.xml or in start_my_server.bat. Go back and check each line you changed, especially the quotation marks.
2. On a PC with the game, start 7 Days to Die and choose Join a Game. Search for your server's name, typed the way you set it.
3. If your server appears, it is running. If it does not, wait a few more minutes, then search again, and open the "More" box in the next section.
4. Seeing your server in the list only proves it is running. Friends outside your home still need the router step in the next section before they can get in.
Next step: we let your friends in.
Let friends join
Your server needs a way in from outside your home. First, we are going to open the ports on your router.
- Open the ports on your router, and allow them in Windows Firewall.
1. This is the port forwarding steps in The Basics, under Ports and port forwarding. Do those steps there, then come back.
2. When it asks for ports, make these rules. Third-party guides give them, and they differ a little, so we list the larger set:
Port 26900, type TCP and also UDP (TCP is Transmission Control Protocol and UDP is User Datagram Protocol, the two ways data travels on the internet).
Ports 26901 to 26903, type UDP. (Most guides list 26901 and 26902. 26903 is an extra.)
3. Make the matching Windows Firewall rules too. The same Basics section shows each screen. Name them something you will recognize, such as "7 Days TCP" and "7 Days UDP".
4. Do not forward ports 8080 and 8081. Third-party guides say those are for remote admin tools (a web dashboard and a text console) that you only need if you turn them on. A forwarded admin port is a way into your server for anyone who finds it.
5. If you changed ServerPort, a third-party guide says the other ports move with it. For example, 26920 would use 26921 to 26923.
Next step: we tell your friends how to find the server. - Tell your friends how to join.
1. Send them your server name (exactly as you typed it in ServerName) and the password if you set one. Send the password privately, not in a public chat.
2. On PC: they start 7 Days to Die, choose Join a Game, and search for the server name. Third-party guides also say PC players can use a Connect to IP option to type your public address, a colon and the port, like 203.0.113.5:26900. That address is made up. Use yours. The Basics steps show how to find it.
3. On Xbox or PlayStation 5: there is no typing in an address. A third-party guide says console players must use Join a Game and the server list, filter for crossplay servers, and search for the server name. On Xbox, a player on a Fun Pimps forum thread says the results do not show right away. You click the small world icon at the top left of the search window to see the list.
4. If you want console players, read the "Console players" box below before you start the server. They cannot join without it.
Next step: stopping the server safely.
Console players: the settings your server needs
- The official crossplay page (posted in June 2025, before version 3.0) says a server that console players join needs these four settings in myserver.xml. Find each line the same way as before (Ctrl+F for the setting's name) and change the value between the quotation marks after value=:
<property name="ServerAllowCrossplay" value="true"/>
<property name="EACEnabled" value="true"/>
<property name="IgnoreEOSSanctions" value="false"/>
<property name="ServerMaxPlayerCount" value="8"/>- ServerAllowCrossplay turns crossplay on. EACEnabled turns on EAC (Easy Anti-Cheat, the game's cheat blocker). IgnoreEOSSanctions stays off. ServerMaxPlayerCount can be 8 at most. The official page writes the values as True and False. Third-party examples write them in lowercase as above.
- Server visibility. A third-party guide says ServerVisibility should be 2 (public, so players can find it in the list). Third-party guides say 1 is friends only and 0 is not listed.
- Mods. One third-party guide says any mod turns crossplay off. The official page does not say.
- Setting limits. The official page lists limits for other settings, and says consoles will not be able to join if you step outside them: experience gained between 25 and 300 percent, day length 10 minutes or more, blood moon enemy count 4 to 64, airdrops no more often than every 24 hours, damage to blocks by players 25 to 300 percent, block damage by enemies 25 percent or more, loot abundance 200 percent or less, and loot respawn 5 days or more. It says PC players can play on the server regardless of settings, and consoles cannot. The page predates version 3.0, which moved many of these settings into the SandboxCode. We do not know how the limits apply to it now.
- The official page says nothing about ports or how consoles find a server.
Making yourself an admin (so you can use commands)
- An admin can type commands in the game. The file that lists admins is named serveradmin.xml. A third-party guide shows an admin line like this:
<user platform="Steam" userid="[YourSteamID64]" permission_level="0" /> - Replace [YourSteamID64] with your Steam ID, the long number that identifies your Steam account. A made-up example looks like 76561198021925107. Do not use that one. Level 0 is the highest admin level. Keep the quotation marks.
- Where the file is. A Steam forum answer, confirmed by the person who asked, puts it in C:\Users\[YourWindowsName]\AppData\Roaming\7DaysToDie\Saves. Replace [YourWindowsName] with your Windows user name, or simply press the Windows key and R together, type %APPDATA%\7DaysToDie\Saves, and press Enter. If it is not there, look one folder up, in %APPDATA%\7DaysToDie (a Linux discussion shows it there), or use File Explorer's search box. The file may not exist until the server has started once, so start it, stop it, and look again. Edit it with Notepad while the server is stopped. We have not seen this file on a real install.
- Console players have different ID types. A third-party wiki lists the platform names Steam, EOS, XBL and PSN. We have not tested those.
More: if friends cannot find the server or cannot join
The server does not show up when you search
Check these in order. First, that the black window is still open on the server computer. Second, that the name you search is exactly the ServerName in myserver.xml. Third, that ServerVisibility is not set to 0, which means not listed. Fourth, that the game and the server are on the same version (see the update section). Fifth, that start_my_server.bat points at myserver.xml (a third-party guide says the start line's -configfile= part decides which file is used).
Friends can see the server but cannot join
Port forwarding is the usual cause. Redo the port forwarding steps in The Basics for port 26900 (TCP and UDP) and 26901 to 26903 (UDP), including the Windows Firewall rules. Check that your server computer's address did not change. The Basics section has a box on double NAT and CGNAT.
A console player cannot find the server
Check the "Console players" box above: crossplay on, EAC on, 8 players or fewer, no mods, and the setting limits. On Xbox, remember to click the small world icon to show the search results.
The black window closes by itself right after starting
Open myserver.xml and look at each line you changed. A missing quotation mark, a missing /> at the end of a line, or a missing > can break the file. Compare the line with an untouched line next to it. If you cannot find it, start over from a fresh copy of serverconfig.xml.
The password is not accepted
Make sure friends type it exactly as written in ServerPassword, including capital letters.
I want to look at the server's log
The black window shows it live. A Steam guide says log files named output_log_dedi followed by a date are kept in a folder named 7DaysToDieServer_Data inside the tool's folder. If you ask for help, copy the last lines from there.
Careful: stop the server before you change anything.
Changing settings later
You change 7 Days to Die's server settings in a file on the server computer, your copy myserver.xml, not from inside the game. First, we are going to stop the server, so the change is safe.
- On the server computer: stop the server. Follow Stop it safely below. Ask everyone to leave first. No page we found says whether the server reads the file again without a restart, so always stop, change, then start.
Next step: we keep a copy of what works now. - Back up the file you have.
1. Open the tool's folder (Steam, right-click the tool, Manage, Browse local files).
2. Copy myserver.xml into your backup folder (such as Documents\7dtd-backup) and rename the copy with today's date, such as myserver_2026-10-01.xml.
Next step: we make the change. - Change the value.
1. Right-click myserver.xml, choose Show more options if you see it, then Edit (or Open with, then Notepad).
2. Press Ctrl+F, type the setting's name, and press Enter. Change only the word between the quotation marks after value=. For example, to change how many players can be on at once:<property name="ServerMaxPlayerCount" value="[NumberOfPlayers]"/>
Replace [NumberOfPlayers] with a whole number, such as 6 (made up, so choose your own). Keep the quotation marks and the />. If you want console players, 8 is the highest (see the console box in Let friends join).
3. Some lines have a short note after them between <!-- and -->. Read it before you change that line.
4. Save (Ctrl+S) and close Notepad.
Next step: we start the server and check. - Start the server and check.
1. Double-click start_my_server.bat.
2. Search for your server in Join a Game and join.
3. If it works, copy the new myserver.xml into your backup folder. If it does not, copy your dated backup over it.
What you can change
- ServerName, ServerPassword, ServerMaxPlayerCount. The name in the list, the password friends type (empty means no password, per third-party guides), and how many players (ships as 8).
- ServerVisibility. Third-party guides say 2 is public, 1 is friends only, and 0 is not listed.
- GameName, GameWorld, WorldGenSeed. Careful. A third-party forum post says a new GameName makes a new save folder, which means a new world. Change them only if you want a new world. To go back, put the old values back exactly.
- ServerPort. Third-party guides say the other ports move with it. If you change it, change the router and Windows Firewall rules to match (see the ports step).
- EACEnabled. It ships on (EAC is Easy Anti-Cheat, the cheat blocker). Console players need it on. A third-party guide says most mods need it off.
- Zombies, loot, XP, difficulty, damage and the rest of the gameplay. The official version 3.0 notes say these now live in the SandboxCode line. Open the game's Sandbox Options menu, set what you want, copy the code, and paste it between the quotation marks of the SandboxCode line. The "Make the game your own" box in the install section has the details. The official notes do not say whether a new code changes a world that already exists, so check in the world.
- Admins. The admin file, serveradmin.xml, is separate from this file. See the admin box in Let friends join.
- Anything else. The file has many more lines. The Assistant can explain one.
Stop it safely, and where your world is saved
No page we found says for certain how to shut this server down. First, we are going to save the world and close the server in the way the console commands suggest, and we say plainly where this part is our own suggestion.
- Stop the server.
1. Ask everyone to leave the world first.
2. If you made yourself an admin (see the admin box above), join the server from the game, press F1 to open the console, type saveworld and press Enter, then type shutdown and press Enter. Both commands are listed on a third-party commands page. It does not say whether shutdown saves by itself, so we run saveworld first.
3. If you did not set up an admin, click the black window on the server computer so it is the active window, then press Ctrl+C. This is a common way to close a program in a text window. It is our suggestion, not from a 7 Days to Die page.
4. Wait for the window to close by itself.
5. If it does not close after a minute, or Ctrl+C does nothing, close the window with the X in its top right corner. A server owner reports the X works when it is the only option. It may skip a final save, so back up first when you can.
Next step: we show where your world is kept. - Know where the world is saved, and back it up.
1. A third-party forum post says the server keeps its user data, including your saves, in %APPDATA%\7DaysToDie by default. Older forum posts show a Saves folder in there, with a folder for the world type inside it and your save's folder inside that. The setting that decides this place is UserDataFolder in your settings file, and SaveGameFolder sets the saves folder.
2. To open it, press the Windows key and R together, type %APPDATA%\7DaysToDie, and press Enter. (If it says the folder does not exist, start and stop the server once so it is created, or look at your UserDataFolder setting.)
3. To back up: stop the server first, then copy the Saves folder into a folder elsewhere, such as Documents\7dtd-backup\2026-10-01 (use today's date). Copy, do not move.
4. Also copy myserver.xml and start_my_server.bat into the same backup folder.
5. Back up regularly.
Switching hosts?
Moving your world between a paid host and your own computer
Every host has its own control panel, so this section covers only the 7 Days to Die side. Whatever your host calls it, you are looking for a file manager, backups or FTP (File Transfer Protocol, a way to copy files to and from a server) page. If you cannot find it, ask the host's support how to download and upload your world. We have not tested a move. First, we are going to look at which files hold your world.
- What to move. Your world is the folder named after your GameName, inside the Saves folder in the server's user data (by default %APPDATA%\7DaysToDie\Saves on your own computer). A third-party forum post says a new GameName makes a new save folder, so the name matters.
- Stop first. Stop the server on the host and on your computer so no file is half-written. Copy, do not move, and keep your own backup.
- From a host to your computer. Download the save folder from the host. Put it inside your own Saves folder, in the same kind of place. Open myserver.xml and set GameName to the folder's exact name, and GameWorld to the map the world used (the host's settings or the world's folder name tell you). Start the server and join to check.
- Your sandbox settings do not travel with the world. The official release notes say the SandboxCode is a setting in the server's config file. Copy the SandboxCode line from the host's settings into your myserver.xml, or the game uses the default rules.
- From your computer to a host. Stop your server and copy your world's folder. Upload it to the host's matching save location, then set the host's GameName, GameWorld and SandboxCode to match.
- Old worlds. The official release notes say a version 2.6 save can be continued on version 3.0 or newer, but you have to recreate the old settings with the Sandbox Options menu.
- If you see a new, empty world, the name did not match. The "More: if your world looks new" box in the update section covers it.
Every time 7 Days to Die updates, come back here.
After a 7 Days to Die update
7 Days to Die updates often. When it does, your friends' game updates, and the server has to match. A third-party wiki says the client and the server must be on the same build, and gives the example that players on one version cannot join a server on a newer one. It also says an update overwrites the shipped serverconfig.xml, which is why your settings live in myserver.xml. First, we are going to back up your world and settings.
- On the server computer: back up first.
1. Stop the server (see the Stop section).
2. Open the user data folder: press the Windows key and R together, type %APPDATA%\7DaysToDie, and press Enter.
3. Copy the Saves folder into a backup folder, such as Documents\7dtd-backup\2026-10-01 (use today's date).
4. Copy myserver.xml and start_my_server.bat into the same backup folder.
Next step: we let Steam update the server tool. - Let Steam update the tool.
1. Open Steam and go to your Library. Click 7 Days to Die Dedicated Server. If it shows an update, let it finish.
2. Steam has a setting that controls when a game or tool updates. Right-click the tool, choose Properties, and look in the Updates section. The wording changes between Steam versions, so read the options and pick the one that keeps it up to date.
3. Stay on the normal (stable) version. Players on the game's test versions need a server on the same test version, and we have not covered that.
Next step: we check that your settings survived. - Check your settings, then start.
1. Open the tool's folder and check that myserver.xml and start_my_server.bat are still there and still yours. Open myserver.xml with Notepad and look at ServerName, GameName and SandboxCode.
2. If anything went back to defaults, stop the server if it is running, and copy your saved files from the backup folder over them.
3. Double-click start_my_server.bat to start the server.
4. Join from the game. If it says your game and the server are on different versions, wait for the server tool to finish updating and try again.
Next step: if you installed with SteamCMD, the box below shows that route. If your world looks new, the "More" box at the end explains.
Installed with SteamCMD? How to update that way
- Stop the server, then run the same install line again. Use the same folder you installed into, and no validate word (validate can overwrite files you changed; The Basics has the details):
steamcmd +force_install_dir "C:\servers\7dtd" +login anonymous +app_update 294420 +quit - Replace C:\servers\7dtd with the folder you used the first time. A third-party wiki says it fetches only what changed.
- Then check your settings files and start the server as in the steps above.
More: if your world looks new or empty after an update
The server started, but it is a brand-new world
Your real world was not deleted. A third-party forum post says the server makes a new save folder when GameName changes. If the server used a different GameName than before (for example because the settings file went back to defaults, or the start file points at the wrong settings file), it made a new world. Your old save folder is still in %APPDATA%\7DaysToDie\Saves, and your backup has a copy.
To go back: stop the server, set GameName in myserver.xml to the old save folder's exact name (and GameWorld to the map it used), check that start_my_server.bat still has -configfile=myserver.xml, and start again. Do not delete any save folders until you have checked.
The game feels easier or different after the update
The official version 3.0 release notes say many settings moved into the SandboxCode line. If it is missing or at its default, the server uses the default ruleset. Check the SandboxCode line in myserver.xml against your backup.
I do not remember my GameName
Look in the Saves folder in your backup. The names of the folders inside are your save names. Your backed-up myserver.xml also has the GameName line.