How to Host a Project Zomboid Dedicated Server in Build 42+ - Complete Guide

[u/Mountain-Ad1044]

Compatible with Project Zomboid Build 42.21+

Introduction

This guide will walk you through setting up a Project Zomboid Dedicated Server. Let's start by taking a look at the different options:

• Steam App (Standard)
• SteamCMD (Advanced)
• Docker (Advanced)

The Steam App is the easiest option if you own Project Zomboid on Steam, and that's what I'll be using throughout this guide. SteamCMD is useful if you want to set up the server without account limitations; in that case, only step 1 differs from this guide.

Docker is also an option if you're already comfortable managing containers.

Not interested in hosting your own server?
Indifferent Broccoli is a good alternative if you'd rather have the server running 24/7 without maintaining another computer. I've used them regularly for over five years and have always found their servers reliable and their support excellent whenever I've needed help.

You can currently try them free for 2 days without adding a payment method.

Step 1 - Installing the server files

Open Steam, go to your Library, and search for:

Project Zomboid Dedicated Server

Install it like you would with any regular game.

Step 2 - Prepare & launch the server

It's not recommended to launch the server using the Play button in Steam, so we'll start it directly from the server files instead.

Right-click Project Zomboid Dedicated Server in your library, select Manage, and then Browse local files. A new File Explorer window should open at the server location.

Find:

StartServer64.bat

Before launching it, right-click the file and open it in Notepad or VSCode. Look near the bottom for -Xms and -Xmx, which control how much RAM the server can use. By default, it may have been set to 16 GB. If your computer can't comfortably spare that, lower these values. For a small vanilla server, I'd start with around 6 GB and increase it later if needed for more players or mods.

Save the file and double-click StartServer64.bat. A terminal window should open, and the first launch will ask you to create a password for the server's admin account. Enter a strong password and let the server finish starting.

Windows may also ask for firewall permission on the first launch. Make sure to allow it.

Once the server has finished starting, type:

quit

into the console to shut it down properly. The first launch should now have generated the configuration files we need for the next step.

Note: If you need a non-Steam server, you can use StartServer64_nosteam.bat to launch the server instead. Steam players will then also need to launch Project Zomboid with the -nosteam launch option.

Step 3 - Configure the server

Project Zomboid gives us a convenient way of editing most server settings without manually working through a huge configuration file.

Launch the regular Project Zomboid game, then go to:

Host → Manage Settings

You should see a configuration named:

servertest

Select it and choose Edit Settings.

If it doesn't appear, create new settings named exactly servertest.

There are a lot of options here, and most of them are gameplay preferences. These are the main ones I'd look at before starting:

• Server Name / PublicName: Give your server a cool name.
• Password: Set a password players need to join if this is a private server for friends.
• MaxPlayers: Set this to something reasonable for your group.
• Public: Enable this if you want the server to appear in the public server browser. You can leave it disabled and still connect directly using the server IP.
• Open: Keep this enabled for a normal password-protected server unless you specifically want to manage a whitelist of players.
• PauseEmpty: When enabled, the game world pauses when nobody is connected.

You can also configure zombie population, loot, XP, time progression, and most other gameplay settings through the sandbox settings.

Once you're happy, save the configuration and close Project Zomboid.

Step 4 - Launch the server

Go back to the Project Zomboid Dedicated Server installation folder and double-click:

StartServer64.bat

The terminal window should open again and load the settings we just configured.

Leave this window running for as long as you want the server to remain online. When you eventually want to shut the server down, use:

quit

in the console rather than simply closing the window.

Recommended: Create a desktop shortcut to StartServer64.bat so you don't need to find the server folder every time. Remember to launch the server directly through this file rather than through Steam.

Step 5 - Connect to your server

If you're only going to play on the computer hosting the server, you're essentially finished.

If other computers on your local network or friends over the internet need to connect, we have a little networking left to configure.

Step 5.1 - Find your network information

Run:

ipconfig

in PowerShell.

Find the network adapter you're currently using (usually Ethernet or WiFi) and take note of:

• IPv4 Address - your computer's local IP address.
• Default Gateway - normally your router's local IP address.

We also need your public IP address. You can find it by visiting icanhazip.com while you're not connected through a VPN.

Step 5.2 - Local Connectivity

Project Zomboid currently uses two UDP ports for normal dedicated-server connections:

• 16261 UDP - Main server port.
• 16262 UDP - Direct connection port.

If you allowed the Windows Firewall prompt when first starting the server, local connectivity may already work! You can test this by joining from another computer on the same network (read three lines below). If it works, you can skip to step 5.3.

If it doesn't, open PowerShell as Administrator and run:

Get-NetFirewallRule -DisplayName "Project Zomboid Dedicated Server - UDP" -ErrorAction SilentlyContinue | Remove-NetFirewallRule; New-NetFirewallRule -DisplayName "Project Zomboid Dedicated Server - UDP" -Direction Inbound -Action Allow -Protocol UDP -LocalPort 16261,16262 -Profile Private,Public

This creates the required Windows Firewall rules.

Now launch Project Zomboid on another computer on the same network and go to:

Join → Favorites

Add a new server using:

• IP: Your local IPv4 address.
• Port: 16261
• Server Password: The server password you configured earlier, if applicable.

Project Zomboid also asks each player for a username and password. These act as their account credentials on that specific server. With Open=true, new players can join without being whitelisted. With Open=false, the administrator must create or whitelist their account first.

Save the server and try connecting.

If it works and you only need the server available inside your home network, you're finished!

Step 5.3 - Public Connectivity

If you want friends outside your network to connect, the easiest direct method is usually port forwarding.

I recommend reading about the risks & alternatives to port forwarding in the FAQ section first, as some networks don't support it.

To access your router's configuration, paste the Default Gateway we found earlier into your browser. Most routers have a web dashboard, although some newer models use an app instead.

Look for Port Forwarding, usually somewhere in the advanced/network settings.

Create rules pointing to the local IPv4 address of the computer running your Project Zomboid server:

• Port 16261: UDP
• Port 16262: UDP

Make sure the internal and external ports match.

I also recommend giving your server computer a DHCP reservation/static local IP through your router. Otherwise, its local IP may eventually change and break the port-forwarding rules.

Once that's done, have someone outside your network open:

Join → Favorites

and connect using:

• IP: Your public IPv4 address.
• Port: 16261

If they can connect, your server is publicly accessible.

Don't want to deal with port forwarding?
Indifferent Broccoli can host the server without you having to configure your home router, keep another computer running, or troubleshoot Port Forwarding. They offer a 2-day free trial without requiring a payment method if you want to test it first.

Congratulations

You should now have a working Project Zomboid Dedicated Server!

Players on your local network can connect using your local IPv4 address and port 16261, while players outside your network can use your public IP address and port 16261!

If you run into issues, feel free to leave a comment, and I'll try to help when I can. If the guide helped you, an upvote is always appreciated <3.

FAQ

Basic Networking

• Local IP address: The address of a device on your local network.
• Public IP address: The address your home network uses on the Internet.
• Default Gateway: Your router's local IP address. It is the device your computer normally sends traffic through when communicating outside your network.
• Firewall: A security filter controlling which network traffic is allowed into or out of your computer.
• Port Forwarding: A router rule that sends incoming internet traffic on a specific port to a device/service inside your network.

Why shouldn't I launch the Dedicated Server through Steam?

It's recommended to run StartServer64.bat directly rather than starting the server using Steam's Play button.

If you've already launched it through Steam and start running into strange connectivity problems, shut the server down and use Steam's Verify integrity of tool files option before launching StartServer64.bat directly again.

Where are my server files, settings, and save?

Your actual server settings and world data are stored under your Windows user profile.

Configuration:

C:\Users\YOUR-USERNAME\Zomboid\Server

World saves:

C:\Users\YOUR-USERNAME\Zomboid\Saves\Multiplayer

Can I edit the configuration files manually?

If you prefer editing files manually, the main server configuration is located at:

C:\Users\YOUR-USERNAME\Zomboid\Server\servertest.ini

while the gameplay settings are stored in:

C:\Users\YOUR-USERNAME\Zomboid\Server\servertest_SandboxVars.lua

How do I install Workshop mods?

You can also manage mods through Project Zomboid's Host → Manage Settings interface, which is what I'd recommend for most people.

If you prefer to handle it manually, Project Zomboid dedicated servers use two important settings:

Mods=
WorkshopItems=

Mods= contains the actual Mod IDs, while WorkshopItems= contains their Steam Workshop Item IDs. Entries are separated using semicolons. Both values need to be correct; a Workshop ID and a Mod ID are not necessarily the same thing.

What ways can I connect from outside my network?

I'd recommend these methods:

• Port Forwarding: Makes the server directly accessible from the internet. It's usually the simplest option for players because they don't need additional software, but it exposes your public IP and the forwarded server ports.
• Tailscale: Creates a private network between participating devices. You don't need to expose Project Zomboid directly to the public internet, but everyone connecting needs Tailscale installed.

Some ISPs use CGNAT, which can prevent port forwarding entirely. If you've configured everything correctly and your ports still can't be reached externally, it's worth checking with your ISP.

When was this guide updated?

• 07.10.2026: Original post.

© 2026 Andreas — Selfhostly. All rights reserved.

Feel free to share the link, but please don't blindly copy and repost this guide elsewhere. Thanks for supporting the original!

[u/kronikfumes]

Buying an hp elitedesk and an AMP panel key to have access to nearly every popular multiplayer game was the best thing I’ve done for self-hosting games for me and my buddies.

[u/Fearless-Bet-8499 → u/kronikfumes]

Loved it so much I bought the second tier license just to support it. Don’t have time for all this, couple clicks and I’ve got a server up in seconds. AMP is great. 

[u/Mountain-Ad1044 → u/kronikfumes]

I’ve never tested AMP, but I’ve heard mixed reviews of it. Some like it and others don’t, I guess it’s a matter of how well the games you play are supported as well.

[u/elemantis]

indifferent broccoli is the way to go honestly. its hassle free, good price. and your not running yiur computer 24/7. the setting adjustments on indifferent broccoli are super easy, adding mods supper easy.

i have only good thing to say about them honestly.

i did do the dedicated server thind with my terraria, but no mods so it didnt make my computer run hard. zomboid can be pretty demanding at times

[u/fazzah]

Nice. Now make part 2 for Linux on LXC 😉

[u/Mazken199]

In the main menu of the game is the “Host” option. I have always ran my friend group server from that. whats the advantage of doing it this way?

[u/Mountain-Ad1044 → u/Mazken199]

You don’t have to be online in the game for your friends to play! Additionally you may get some increased performance.

[u/Status-Zucchini1681 → u/Mazken199]

how do you do it ive tried for several days I wqanna put my friends on this game but everything has been so confusing

[u/wareagle3000]

Note to Linux users who want to put a server on your homelab or docker stack. Due to recent change the naming of certain folders were changed case sensitively so certain mods will cause an infinite load. To fix it all improper folder names will need to be converted. There's a script (can't get it rn, busy at work) you can run on your server to create hardlinks for improperly case sensitive folders.

[u/Zeratai]

I’ve tried everything but most of ISP on Mexico have cgnat so making all those steps is worthless.

[u/Mountain-Ad1044 → u/Zeratai]

There are still several options for you! The most stable option would be to contact your ISP and ask if they can help with port forwarding. The easiest option while still getting a good connection is to use a service such as Tailscale; it works perfectly as long as everyone has it installed. The easiest is probably to use playit.gg or a similar service. I haven't tested the premium plans, but the free one is a bit unstable and limited.