Setup Guide
How to Set Up a Project Zomboid Dedicated Server (2026)
This guide walks through both ways to run a persistent Project Zomboid dedicated server: self-hosting the Linux/Docker server yourself, and deploying a fully managed server on the Flux decentralized cloud in about 30 seconds. Project Zomboid is an open-ended zombie-survival sandbox set in Knox County, Kentucky (Build 41) that supports up to 32 players, and a dedicated server keeps your world, safehouses and survivor progression online 24/7 with no resets.
Why run a dedicated server instead of hosting from the game?
When you host Project Zomboid directly from your game client, the world only exists while you are online. The moment you close the game, every friend is disconnected and the apocalypse pauses. A dedicated server removes that limitation: Knox County runs continuously, friends in any time zone can log in whenever they like, and you gain admin tooling - Source RCON for kick/ban and broadcasts, sandbox settings, scheduled restarts, saves and backups - that player-hosting does not offer.
Method 1: Self-host the Project Zomboid dedicated server (Linux + Docker)
- Provision a machine that meets the requirements: about 4 GB RAM for a small vanilla group (6-8 GB for heavily modded or larger servers), 2 CPU cores, and roughly 15 GB of SSD. See our Project Zomboid dedicated server requirements for details.
- Install Docker on your Linux host and pull the Project Zomboid dedicated server image (
danixu86/project-zomboid-dedicated-server), or run the server natively on Linux. - Configure the server - set the server name, sandbox settings (zombie population, loot rarity, the horde) and any Steam Workshop mods via the config file or environment variables.
- Open the ports your server uses - by default 36261 plus 36262 UDP - on both your firewall and router (port forwarding), and make sure they are reachable from the internet.
- Start the container, wait for the first boot to finish, then share your address (IP or domain), port and optional password so friends can join.
- Maintain it - keep the image updated to match the client version, schedule backups of the save data, and monitor RAM/CPU as your world and mod list grow.
Self-hosting is free apart from your hardware or VPS bill, but you own every part of the stack: the OS, networking, updates, uptime and backups.
Method 2: Deploy a managed Project Zomboid server on Flux (recommended)
- Create a free account at projectzomboid.runonflux.com with Google, email or a Flux wallet.
- Choose a plan sized for your group and a region close to your players for the lowest ping.
- Click deploy - automated provisioning brings your dedicated server online in under 30 seconds, with DDoS protection and the Steam Workshop Mod Manager and RCON dashboard already enabled.
- Share your connection details - the server address, port and optional password - from your dashboard; see how to play with friends.
- Manage everything from the web dashboard: file manager, sandbox config editor, Steam Workshop Mod Manager that auto-resolves Mod IDs, RCON, backups and restore.
The managed route handles the operating system, networking, ports and updates for you, so you can focus on surviving instead of sysadmin work.
The first things to do after your server is up
A fresh Build 41 server works out of the box, but three settings are worth deciding before anyone starts a character, because changing them later is disruptive:
- Pick the sandbox preset. Apocalypse, Survivor and Builder change loot rarity, zombie strength and XP rates dramatically. Agree on one with the group at deploy — swapping preset mid-run rewrites the rules under players who have already built around them.
- Settle the mod list. Adding or removing map and overhaul mods after a world has generated can corrupt already-explored chunks. Install what you want up front; the Steam Workshop mods guide covers load order and the two IDs every mod has.
- Set a join password if the server is not meant to be public. It takes effect after the first restart, so restart once before sharing the address.
After that, the day-to-day is simple: the RCON console handles kicks, bans, broadcasts and manual saves, and backups run on demand from the dashboard. Take one before any mod change — that is when a world is most likely to break, and one-click restore is what turns a bad evening into a five-minute fix.
Setup FAQ
How long does it take to set up a Project Zomboid server?
Self-hosting takes anywhere from 20 minutes to an hour depending on your experience. A managed Flux deployment is live in about 30 seconds.
Do I need port forwarding?
Only when self-hosting. Managed Flux servers open the required ports automatically.
Can I move my world later?
Yes - the save data is portable, so you can migrate between hosts or between self-hosted and managed.