Menu
 

How to Make a Project Zomboid Server (2026): Step-by-Step Guide

How to Make a Project Zomboid Server (2026)

Three ways to run a Project Zomboid multiplayer server in 2026: in-game Host Server (free, dies when you log off), self-hosted dedicated (full control, requires Linux/Windows skills), or managed hosting (pay $5.99-$12.99/mo, skip the setup). This guide walks through all three so you can pick the right one for your group, then gives you the exact commands and config edits to ship it.

TL;DR by group size: 2-3 friends, casual play → in-game Host Server is fine. 4+ players, want persistent saves → dedicated server (DIY or managed). 8+ players, mods, RP community → managed hosting saves you days of mod-version-pinning headaches.

The Three Options at a Glance

MethodCostSetup timeAlways-on?Best for
In-game Host ServerFree2 minutesNo (only when you're online)2-4 friends, casual sessions
Self-hosted dedicated (Linux)$0 hardware (or $10-30/mo VPS)1-3 hoursYes (if you keep your hardware on)Tech-savvy admins who want full file access
Self-hosted dedicated (Windows)$0 (your PC) or VPS30-60 minutesYes (PC must stay on)Windows users avoiding the Linux learning curve
Managed hosting$5.99-$12.99/mo2 minutesYes, 24/7 datacenterCommunities of 4+ players who want zero ops

Option 1: In-Game Host Server (Easiest)

  1. In Project Zomboid main menu, click Host.
  2. Pick Sandbox for custom rules or Apocalypse for vanilla.
  3. Set a server name and password.
  4. Configure your sandbox sliders (zombie population, day length, looting rate, etc.).
  5. Click Start. Your friends connect via Steam Friends or by joining the server name through PZ's multiplayer browser.

Honest caveat: Host Server runs in the same Java process as your game. RAM is shared. Performance degrades fast with mods or 4+ players. The server exists only while you're playing — log off and your friends get disconnected. Saves are per-host: only YOU can resume the world.

Option 2: Self-Host a Dedicated Server (Linux)

Linux is the recommended platform for serious PZ servers. Cheaper VPS, lower overhead, better scripting story. Tested on Ubuntu 22.04 LTS.

Step 1: Install SteamCMD

sudo apt update sudo apt install -y software-properties-common sudo add-apt-repository multiverse sudo dpkg --add-architecture i386 sudo apt update sudo apt install -y steamcmd

Step 2: Create a Service User and Install PZ Server

sudo adduser --system --group --home /home/pzserver pzserver sudo -u pzserver -H bash -c " steamcmd +login anonymous \ +force_install_dir /home/pzserver/zomboid-server \ +app_update 380870 validate \ +quit "

App ID 380870 is the Project Zomboid Dedicated Server. (The game itself is 108600 — don't confuse them.)

Step 3: First Boot to Generate Configs

sudo -u pzserver -H bash -c " cd /home/pzserver/zomboid-server ./start-server.sh -servername myserver -adminpassword changeme123 "

Press Ctrl+C after the first boot finishes. Configs now live in /home/pzserver/Zomboid/Server/myserver.ini and myserver_SandboxVars.lua.

Step 4: Edit myserver.ini for Your Group

PublicName=My PZ Server PublicDescription=Friends only — please be cool MaxPlayers=8 DefaultPort=16261 UDPPort=16262 PingFrequency=10 Open=true Password= PauseEmpty=true GlobalChat=true AnnounceDeath=true DiscordEnable=false

For per-player slot tuning and 100+ sandbox options, see our Complete Server Settings Reference.

Step 5: Configure Sandbox Settings

Edit myserver_SandboxVars.lua for zombie counts, day length, looting rates. See All Sandbox Settings for every option.

Step 6: Open Ports

Default ports are UDP 16261 (game) and UDP 16262 (Steam). On Linux:

sudo ufw allow 16261/udp sudo ufw allow 16262/udp

If you're behind a router, also forward UDP 16261-16262 in your router admin panel. See our PZ Server Ports Guide for ISP/CGNAT issues.

Step 7: Run as a systemd Service

Don't run from a shell session — make it a proper service that restarts on crash:

sudo tee /etc/systemd/system/pzserver.service <<'EOF' [Unit] Description=Project Zomboid Dedicated Server After=network.target [Service] Type=simple User=pzserver WorkingDirectory=/home/pzserver/zomboid-server ExecStart=/home/pzserver/zomboid-server/start-server.sh Restart=on-failure RestartSec=15 [Install] WantedBy=multi-user.target EOF sudo systemctl daemon-reload sudo systemctl enable --now pzserver

Step 8: Allocate Enough RAM

Default start-server.sh reserves only 4 GB. For modded or larger groups, edit -Xmx. See our Project Zomboid Server Memory Guide for per-scenario numbers.

Option 3: Self-Host on Windows

  1. Subscribe to "Project Zomboid Dedicated Server" tool in your Steam Library (free).
  2. Install via Steam.
  3. Right-click Steam → Browse Local Files → find StartServer64.bat.
  4. Run it once to generate configs in C:\Users\YourName\Zomboid\Server\.
  5. Edit servertest.ini (or rename to your server name).
  6. Forward UDP 16261-16262 in your router.
  7. Run StartServer64.bat — it stays running until you close the console window or your PC powers off.

Windows gotcha: Windows Defender often blocks the dedicated server. Whitelist StartServer64.exe and the Java executable in jre64\bin\java.exe before complaining about lag.

Option 4: Managed Hosting (Skip the Whole Thing)

The DIY paths above work if you want full control. The honest reality: most groups end up paying for managed hosting after the first time a Build 42 patch breaks Saturday's session at 11 PM.

  • Plan S ($5.99/mo) — 1-8 vanilla players
  • Plan M ($7.99/mo) — 8-16 players, modded servers
  • Plan L ($12.99/mo) — 16-32 players, heavy mod packs

All plans include: automatic snapshots, Steam Workshop one-click mods, mod-version pinning, RCON, FTP/SFTP, web file manager, scheduled restarts, free region change, 17 Tbit/s DDoS protection, 2-day money-back. See all PZ hosting plans →

Hosting for Friends (Specifically)

If you just want a small server for 2-6 friends, here's the realistic short path:

  1. Try Host Server first (free, 2 min setup) — works fine for casual non-modded play.
  2. If anyone complains about lag, move to a managed Plan S — $5.99/mo, no setup, 24/7 even when you sleep.
  3. Skip self-hosting unless you specifically want to learn server admin or have spare always-on hardware.

Common Mistakes

  • Confusing the game and server App IDs. Game = 108600, dedicated server = 380870.
  • Editing the wrong .ini file. The active server is the one you passed via -servername on first boot. Default is servertest.
  • Not allocating enough RAM for mods. See Server Memory Guide.
  • Ignoring Steam Workshop pinning. A modded server breaks the next time a mod updates if you didn't pin the Workshop versions.
  • Running on a residential connection with CGNAT. Most cellular and some cable ISPs block incoming connections. Friends won't be able to join. See Port Forwarding & CGNAT Issues.

Related Project Zomboid Guides

Want zero setup? Supercraft Project Zomboid hosting from $5.99/mo — Plan S/M/L for any group size, instant deploy, mods preinstalled, automatic backups, DDoS protection, 5 datacenter regions, 2-day refund. Cancel anytime.

Tired of fighting this issue every patch?

Run a managed Project Zomboid server with us — we handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in 3 minutes, 5 datacenter regions, no contract.

See Project Zomboid hosting plans →
Top