Hosting Project Zomboid Build 42: Ports, Capacity, and Small-Group Setup

For Project Zomboid Build 42.19 Host and dedicated-server multiplayer.

Quick-start setup

These steps cover a dedicated server on Windows or Linux. For connection failures after the server is running, use the server connection guide and the normal termination / crash guide. Deeper option names live in the server administrator tips and the admin survival guide.

1. Install the dedicated server. In Steam: Library → Tools → Project Zomboid Dedicated Server. Download size varies by platform and updates; plan for multiple gigabytes, not a tiny download.
2. First launch. Browse local files and run StartServer64.bat (Windows) or the matching start-server.sh script (Linux). Set an admin password when prompted.
3. Open two UDP ports for internet play. Forward or allow UDP 16261 (DefaultPort) and UDP 16262 (UDPPort). Do not open a long per-player range such as 16262–16266 unless you have a documented reason on an older stack—current UI describes two UDP ports.
4. Configure before inviting players. Stop the server after the first run. Use in-game Host → Manage Settings, or edit Zomboid/Server/<servername>.ini. Set name, password, memory, MaxPlayers, and mods while the process is stopped.
5. Start and confirm. Launch again from the Host UI or the start script. Wait until the console reports the server is ready, then join from LAN (same network) or the public IP with port 16261.
6. Stop cleanly. Prefer save then quit in the console, or the Host Stop control. Kill signals without a save risk lost progress.

Ports and firewall (Build 42.19)

Networking uses two UDP ports: a primary player-data port and a second UDP port. Defaults in current options are:

If you change either port in the INI, forward the values you actually set—not the defaults from a blog post. Clients typically connect with the primary port (16261 by default). Leaving only one of the two UDP ports open is a common cause of “works on LAN, fails on internet.”

# Linux firewall examples (adjust if you changed the INI)
sudo ufw allow 16261/udp
sudo ufw allow 16262/udp
# Prefer the two explicit rules above over wide ranges like 16261:16270/udp

Player capacity and the 32+ warning

Capacity is defined by server options, not by marketing “slots” on a host’s product page.

Hardware planning

Project Zomboid multiplayer is sensitive to single-thread CPU work, open map chunks, zombie AI, and mods. RAM prevents out-of-memory crashes more than it “buys FPS.” Use these ranges as starting points for capacity planning, then measure under real load.

• CPU: Prefer higher single-thread speed over many idle cores. Busy zombie simulation and multiplayer sync are not pure multi-core free lunch.
• Upload: Remote players depend on your upstream. Home asymmetric plans fail more often on upload than download; measure with friends online, not idle speed tests alone.
• Storage: SSD reduces hitching when chunks load and the world saves. Install plus saves grow over time—leave free space for logs and backups.
• OS headroom: Cap Java with -Xmx below total RAM so the OS, antivirus, and Steam still have room.

Build 41 vs Build 42 hosting notes

Build 42 multiplayer is available. Hosts should plan around version matching and content changes, not around “B42 is free performance.”

Windows, Linux, and hosted options

Windows (home PC or spare box)

• Easiest path for beginners: Steam tool + Host UI + Windows Firewall prompts.
• For always-on play, the machine must stay awake; use a high-performance power plan if the host idles poorly.
• Allow the Java runtime / server process and the two UDP ports through the firewall.
• Hosting and playing on the same PC is common for tiny groups; watch combined RAM and disk I/O.

Linux headless

# Install with SteamCMD (dedicated server app id 380870)
./steamcmd.sh +login anonymous +app_update 380870 validate +quit

chmod +x start-server.sh
./start-server.sh -Xms2g -Xmx4g -adminpassword "YourAdminPass"

# Open only the ports you configured in the INI
sudo ufw allow 16261/udp
sudo ufw allow 16262/udp

• Run under tmux or screen, or a systemd unit, so logout does not kill the process.
• Edit Zomboid/Server/<name>.ini and the matching sandbox file while the server is stopped.
• Low-power boards can work for tiny groups; they fail first under large hordes and heavy mods, not during empty-world idling.

Game panels vs DIY VPS

• Pick a region near your players.
• Prefer documented CPU / RAM over vague “player slot” tiers.
• Confirm monthly bandwidth caps if everyone explores distant cities every session.

Key INI options and admin basics

Settings live under the user Zomboid folder, typically Zomboid/Server/<servername>.ini for network and admin options, plus <servername>_SandboxVars.lua for loot and zombie rules.

# Identity and network (examples — keep key names exact)
Public=true
PublicName=My PZ Server
DefaultPort=16261
UDPPort=16262
ServerPassword=
UPnP=true

# Access and capacity
Open=true
MaxPlayers=8
PVP=false
PauseEmpty=true

# Mods (IDs must match installed workshop content)
Mods=
WorkshopItems=

# Optional remote console — secure or leave disabled
RCONPort=27015
RCONPassword=

# Discord group still exists in Build 42 options
DiscordEnable=false
# DiscordToken=
# DiscordChatChannel=
# DiscordLogChannel=
# DiscordCommandChannel=

Useful admin commands

Backups

• Stop the server (or ensure a consistent save), then copy the multiplayer save folder under Zomboid/Saves/Multiplayer/ plus the matching Zomboid/Server/ configs.
• Never delete a live world “to fix lag” without a verified backup.
• Soft-reset is a separate, destructive maintenance action described in the game UI—use only when you intend that outcome.

Mods and load management

Mods change RAM, download size, and failure modes. Prefer a small shared Workshop collection over dozens of overlapping packs.

• Put dependency mods before dependents in the load list.
• After workshop updates, restart so every client and the server share the same versions.
• Large map packs, dense item overhauls, and mass-spawn tools are the usual first suspects when “hardware that used to be fine” starts hitching.
• Named community mods change over time; confirm Build 42 compatibility and Workshop IDs before treating any list as permanent.

FAQ

How much RAM do I need?

There is no fixed per-player RAM formula from the game. For a 2–4 friend vanilla server, many hosts start around a 4 GB Java budget; for 5–8 players or heavy mods, plan higher and leave OS headroom. Size from your actual sandbox and mod list—not a fixed “2 GB + 0.5 GB per player” rule.

Which ports must I open?

By default, UDP 16261 (DefaultPort) and UDP 16262 (UDPPort). Open both for internet play. Do not rely on older guides that prescribe a multi-port per-player range unless you know you are on a different networking model.

What is the safe MaxPlayers value?

Default is 32. Counts above 32 may cause poor map streaming and desync. The option allows values up to 100—that is a configuration ceiling, not a performance rating. For friends-only servers, set MaxPlayers to your real group size.

Does Build 42 require better hardware than Build 41?

Treat B42 as its own workload: new content and different mods can raise or lower load. If a B41 host was already near the edge at high player counts, re-test on B42 instead of assuming free headroom.

Can I host Build 42 on a headless Linux box?

Yes. Install app ID 380870 via SteamCMD, set memory flags, open the two UDP ports you configured, and keep the process under a session manager or service. All primary configuration remains text files under the Zomboid user directory.

Is Discord integration gone in Build 42?

No. Discord-related server options still exist (enable flag, bot token, and channel fields). They are optional; leave them disabled if you do not run a bot.

How do I cut lag?

• Confirm both UDP ports and that clients use the correct primary port.
• Lower zombie population or other sandbox extremes if CPU is pegged.
• Use PauseEmpty=true when the world should idle offline.
• Restart after heavy workshop updates; inspect logs for missing assets.
• Stay at or below 32 concurrent players unless you accept the streaming/desync risk.