Project Zomboid is one of those games that looks kind of simple… until it isn’t.
You start with a backpack, a half broken frying pan, and this optimistic idea that you will be the one person in Knox Country who has it all figured out. Then you open the wrong bathroom door and suddenly you are sprinting, bleeding, and questioning your life choices.
Now add friends.
A dedicated server turns Project Zomboid into a long running apocalypse. A shared base. Shared vehicles. Shared mistakes. People logging in at different times and still living in the same world. No more “host has to be online” problems.
This guide walks you through setting up a Project Zomboid dedicated server, explains the settings that actually matter, and helps you avoid the common facepalm stuff that wastes an evening.
If you want the simplest route, I will also mention a hosted option like Gaming4Free (https://gaming4free.net) where you can deploy a server from a web panel, no credit card, and manage mods, backups, and files without living in a terminal. But I’ll cover the full DIY route too.
Dedicated server vs hosting a co op game
Quick clarity, because a lot of people mix these up.
Co op hosting (Invite friends) is when you click “Host” in game and your PC is the server. If you log off, the world pauses. If your internet hiccups, everyone feels it. It’s fine for a quick night.
Dedicated server is a separate server process that runs the world continuously. You can leave it up all week. Friends can join anytime (assuming you allow it). It’s the “real” way to run a long term multiplayer world.
What you need before you start
You don't need a monster machine, but you do need a few basics:
- A Windows or Linux machine to run the server (local PC, spare PC, VPS, or hosted panel)
- A stable connection if you are hosting at home
- Ability to forward ports on your router (if hosting at home)
How much RAM do you need?
- Vanilla small group: 2 to 4 GB can work
- 6 to 10 players with mods: 6 to 12 GB is more realistic
And patience. Not a ton, but some.
Option A: The easy way (hosted server)
If you don't want to mess with port forwarding, firewall rules, SteamCMD updates, or figuring out why your friend can't connect, hosted servers are the "just play" option.
On Gaming4Free you can spin up a multiplayer game server from a control panel, manage config files, upload mods, and use features like:
- 1 click deployment
- Live console access
- File manager and SFTP
- Automatic backups
- Multi region hosting with DDoS protection
- Free tier with a renewable 24 hour lease model (and paid plans if you want always on)
If your goal is simply "we want a stable Zomboid world tonight", hosted is often the shortest path. You still want to understand the settings though, because Project Zomboid server config is where the real magic lives.
Alright. DIY time.
Option B: DIY dedicated server (Windows)
Step 1: Install the Project Zomboid Dedicated Server tool
On Steam, go to Library, change the filter to show Tools, then search for:
Project Zomboid Dedicated Server
Install it like a normal Steam thing.
Once installed, you’ll have a server folder inside your Steam library, usually something like:
...\Steam\steamapps\common\Project Zomboid Dedicated Server\
Step 2: First launch to generate config files
In the dedicated server folder there are start scripts (batch files). On Windows you’ll typically run:
StartServer64.bat(common)- or a similar start file depending on build
Run it once. The first run creates your server settings in your user folder, not inside the install directory. That trips people up.
Config path is typically:
C:\Users\<YourName>\Zomboid\Server\
Inside that folder you’ll see files like:
servertest.iniservertest_SandboxVars.luaservertest_spawnregions.luaservertest_spawnpoints.lua
The “servertest” part is the default server name. You can rename later, but keep it simple at first.
Step 3: Edit server settings (the important ones)
Open servertest.ini with a text editor. Notepad works. Notepad++ feels nicer.
Here are the settings you should actually look at, especially for a first server.
Server name and description
You’ll see things like:
PublicName=PublicDescription=
If you are not listing publicly, this is mostly for you. But it’s still nice to label it so your friends pick the right server.
Password (do this)
Set a password. Seriously. Randoms will join even if you think they won’t.
Password=YourPasswordHere
Max players
MaxPlayers=8
Be honest with this. A home hosted server with 20 max players is a great way to make your own internet cry.
PVP and friendly fire
If you’re playing with friends who have… energy… decide now.
PVP=true/falseSafetySystem=true/false
The safety system gives a small buffer to prevent accidental (or “accidental”) murder.
Minutes per in game day
MinutesPerDay=60 is common.
Shorter days are more hectic. Longer days feel more like a survival sim. I like 60 or 90 for groups, because it gives time for scavenging runs without everything turning into night instantly.
Loot respawn
A big one for long running servers.
If you want a world where looting matters and towns don’t magically refill, keep respawn off or slow. If you want ongoing gameplay for months with players coming and going, consider a gentle respawn.
Settings vary by version, but look for options like loot respawn hours and whether it’s enabled.
Safehouse options
If you want safehouses, set rules:
- Require claim
- Allow trespass
- Allow fire spread (careful)
Project Zomboid plus fire is basically “we accidentally deleted our base”.
Step 4: Sandbox settings
The servertest_SandboxVars.lua file controls the “world rules”. Zombie population, infection, electricity shutoff, vehicle condition, all that.
If you do not want to read a wall of settings, here are the usual decisions people argue about:
- Infection: Bite only vs saliva only vs off
If you want cinematic deaths, keep it on. If your group hates losing characters, consider bite only or even off. No shame. It’s your apocalypse. - Zombie count: Normal is fine. High can be miserable with new players.
- Respawn/unseen hours: Controls whether areas refill with zombies.
- Water and power shutoff: Default is great for the slow collapse feeling.
Change a few things, not everything. If you tweak every variable at once, you won’t know what caused the weirdness later.
Step 5: Open the right ports (router + firewall)
This is the part that breaks most home servers.
Project Zomboid uses UDP ports. Common defaults:
- UDP 16261 (main server port)
- UDP 16262 (first player slot)
- More player slots increment upwards (16263, 16264, etc)
Rule of thumb: forward 16261 to 16261 UDP and then forward a range for players, like:
16262 to 16272 UDP for up to about 10 players.
Exact needs depend on your MaxPlayers. If you set 32 players, you may need a wider range.
Windows Firewall
Make sure the server executable is allowed through firewall for private networks, or manually open the same UDP ports.
If your friends can see the server but time out, it’s almost always ports or firewall.
Step 6: Start the server for real
Run the start script again. You should see the console window and logs. The first boot can take a bit.
Look for lines indicating:
- Server started
- Listening on port 16261
- Steam connection initialized
If it errors immediately, read the log. Zomboid logs are verbose, but the clue is usually there.
Step 7: Connect from your game client
On the PC running the server, you can connect via:
127.0.0.1(localhost)
For friends outside your network:
- Use your public IP (from a “what is my IP” site)
- Or use a domain if you have one
- Give them the port if needed (usually just the default)
Inside your LAN, friends can use your local IP like 192.168.x.x, but that only works on the same home network.
DIY dedicated server (Linux) with SteamCMD (short version)
If you’re using Ubuntu or Debian, SteamCMD is usually the path.
High level steps:
- Install SteamCMD
- Download the Project Zomboid dedicated server app via SteamCMD
- Run the server start script
- Edit config files in
~/Zomboid/Server/ - Open UDP ports in your firewall (ufw/iptables)
- Run it in a screen or tmux session so it stays alive after logout
Linux is stable and nice for 24/7 hosting, but if you’re not comfortable, a managed panel (again, Gaming4Free style) removes most of the pain.
Mods on a dedicated server (without losing your mind)
Mods are where servers go from “cool” to “this is our world”.
But mods are also where servers break.
The two IDs you need
Most Workshop mods have:
- A Workshop ID (a number)
- A Mod ID (a text string)
The server needs both. Usually in the .ini you’ll see:
WorkshopItems=Mods=
Example format is typically comma separated lists. The order can matter sometimes, and duplicates can cause issues.
If players are getting “Workshop item version mismatch” errors, do this checklist:
- Make sure server downloaded the mods
- Make sure clients are subscribed to the same mods
- Restart server after changing mod lists
- Remove old mod configs if you changed a lot at once
Where to find the mod info
On the Steam Workshop page, the Workshop ID is in the URL. The Mod ID is often in the description or inside the mod files.
Yes, it is annoying the first time. After that, it’s routine.
Mod load order and compatibility
If you’re running a lot of mods, test in batches.
Add 5 mods. Boot. Join. Drive around. Fight something. Quit. Add more.
If you install 40 mods at once and it breaks, you now have a fun job. You become the QA department.
Admin, whitelist, and basic server safety
Even if you only invite friends, do some basic safety.
Admin account
You can set admins in the server settings or via console commands once in game.
Admins can:
- Teleport to stuck players
- Fix broken safehouse claims
- Spawn items (try not to abuse it or the game gets stale)
- Kick or ban if needed
Whitelist
If you want to lock the server down, use a whitelist. That way only approved usernames can join.
It’s worth it if you ever plan to make the server public.
Backups (do not skip this)
Project Zomboid worlds can corrupt. Mods can break saves. Power can go out. Someone can accidentally burn the base down and you might want to roll back even if nobody admits it.
Back up your Zomboid server folder, especially:
Zomboid/Saves/Multiplayer/Zomboid/Server/
If you use a host like Gaming4Free, automatic backups are usually built in. On DIY, schedule it yourself. Even a simple daily zip is better than nothing.
Common problems and fixes (the stuff you will probably hit)
“My friend can’t connect”
- Check UDP port forwarding
- Check firewall rules
- Confirm you gave the correct public IP
- Confirm server is actually running and listening on 16261
“Server not showing in browser”
Don’t rely on the server browser. Direct connect is often more reliable.
Also, if Steam services are having a day, browser listings can be flaky.
“Version mismatch”
Update server and client to the same build. If you’re on unstable or beta branches, make sure everyone is on the same branch.
“Mods not downloading”
Usually a wrong WorkshopItems list, or SteamCMD permissions, or the server didn’t restart after changes.
“Lag spikes when driving”
This can be CPU, RAM, disk I/O, or just too many zombies plus too many vehicles plus too many mods. Reduce view distance, reduce zombie counts, or upgrade the host.
Dedicated servers benefit from good single thread performance more than people expect.
A sane starter configuration (for most friend groups)
If you just want a fun, not too brutal, not too easy co op world, this is a solid vibe:
- 6 to 10 max players
- Password protected
- PVP off (or on with safety system)
- 60 or 90 minute days
- Infection on, bite only (optional)
- Zombie population normal, respawn slow or off
- Loot respawn off (or very slow)
- Backups daily
- Add mods slowly, not all at once
It keeps the tension, but doesn’t turn every session into a corpse run marathon.
Should you self host or use a hosting panel?
If you like tinkering, self hosting is satisfying. You control everything and it’s basically free if you already have the hardware.
But if you want reliability, easy mod management, quick restarts, built in backups, and not having to teach your router what 16261 UDP means, using a hosting platform is honestly just… calmer.
That’s why platforms like Gaming4Free (https://gaming4free.net) are appealing for Project Zomboid groups. You can get a server up fast, manage it from a browser, and spend your time planning your next supply run instead of troubleshooting NAT.
Final notes before you hit “Start”
Dedicated servers change how Project Zomboid feels. The world keeps living even when you are not there. Your friend logs in and expands the base. Someone else clears a road. You come back and the fridge is full, or the garage is on fire, either way it’s a story.
Set a password. Make backups. Don’t add 50 mods in one night. And maybe, just maybe, don’t open the bathroom door without pushing first.
If you want the quickest setup with a control panel and no credit card to test the idea, start with Gaming4Free. If you want full DIY control, follow the steps above and you’ll have a stable dedicated server running.
Then it’s you, your friends, and an unreasonable number of zombies.
Good luck. You’ll need it.
FAQs (Frequently Asked Questions)
What is the difference between hosting a co-op game and running a dedicated server in Project Zomboid?
Hosting a co-op game means your PC acts as the server, so if you log off or experience internet issues, the game pauses or affects all players. A dedicated server runs continuously on a separate machine, allowing friends to join anytime without depending on the host being online, ideal for long-term multiplayer worlds.
What are the basic requirements to set up a Project Zomboid dedicated server?
You need a Windows or Linux machine (local PC, spare PC, VPS, or hosted panel), a stable internet connection if hosting at home, and the ability to forward ports on your router. RAM requirements vary: 2-4 GB for small vanilla groups and 6-12 GB for 6-10 players with mods.
How can I easily set up a Project Zomboid dedicated server without dealing with technical hassles like port forwarding?
Using a hosted server service like Gaming4Free allows you to deploy and manage your Project Zomboid server via a web panel without needing credit cards. Features include one-click deployment, live console access, file management, automatic backups, multi-region hosting with DDoS protection, and a free tier with renewable leases.
What are the essential server settings I should configure when setting up my Project Zomboid dedicated server?
Key settings include setting a clear Server Name and Description for easy identification; setting a Password to prevent unwanted access; configuring MaxPlayers realistically based on your hardware; deciding on PVP and SafetySystem settings to manage player combat; adjusting MinutesPerDay for gameplay pacing; managing loot respawn rates for long-term play; and configuring safehouse rules such as claim requirements and fire spread options.
Where are the configuration files located after launching the Project Zomboid Dedicated Server for the first time?
After running the dedicated server start script once, configuration files like servertest.ini and related sandbox variables are generated in your user folder, typically at C:\Users<YourName>\Zomboid\Server. This location is outside of the installation directory.
How much RAM do I need for running a Project Zomboid dedicated server with mods and multiple players?
For 6 to 10 players with mods enabled, it's realistic to allocate between 6 to 12 GB of RAM. For smaller vanilla groups of 2 to 4 players, 2 to 4 GB may suffice. Always consider additional overhead depending on your specific mod setup and player count.
Frequently Asked Questions
What is the difference between hosting a co-op game and running a dedicated server in Project Zomboid?
Hosting a co-op game means your PC acts as the server, so if you log off or experience internet issues, the game pauses or affects all players. A dedicated server runs continuously on a separate machine, allowing friends to join anytime without depending on the host being online, ideal for long-term multiplayer worlds.
What are the basic requirements to set up a Project Zomboid dedicated server?
You need a Windows or Linux machine (local PC, spare PC, VPS, or hosted panel), a stable internet connection if hosting at home, and the ability to forward ports on your router. RAM requirements vary: 2-4 GB for small vanilla groups and 6-12 GB for 6-10 players with mods.
How can I easily set up a Project Zomboid dedicated server without dealing with technical hassles like port forwarding?
Using a hosted server service like Gaming4Free allows you to deploy and manage your Project Zomboid server via a web panel without needing credit cards. Features include one-click deployment, live console access, file management, automatic backups, multi-region hosting with DDoS protection, and a free tier with renewable leases.
What are the essential server settings I should configure when setting up my Project Zomboid dedicated server?
Key settings include setting a clear Server Name and Description for easy identification; setting a Password to prevent unwanted access; configuring MaxPlayers realistically based on your hardware; deciding on PVP and SafetySystem settings to manage player combat; adjusting MinutesPerDay for gameplay pacing; managing loot respawn rates for long-term play; and configuring safehouse rules such as claim requirements and fire spread options.
Where are the configuration files located after launching the Project Zomboid Dedicated Server for the first time?
After running the dedicated server start script once, configuration files like servertest.ini and related sandbox variables are generated in your user folder, typically at C:\Users\
How much RAM do I need for running a Project Zomboid dedicated server with mods and multiple players?
For 6 to 10 players with mods enabled, it's realistic to allocate between 6 to 12 GB of RAM. For smaller vanilla groups of 2 to 4 players, 2 to 4 GB may suffice. Always consider additional overhead depending on your specific mod setup and player count.