Project Zomboid Port Forwarding Guide
If players can't connect to your Project Zomboid server, port forwarding is almost always the cause. This guide covers the exact ports needed, how to forward them on common routers, and how to verify the forward worked.
Hosted on DoomHosting? You don't need to port-forward anything. Our servers expose ports automatically. This guide is for self-hosted setups (your own PC or a home server).
The exact ports you need
Project Zomboid (Build 41 and 42) requires only one port for client connections:
| Port | Protocol | Purpose |
|---|---|---|
| 16261 | UDP | Game traffic (required) |
Older guides mention port 16262 and a port range up to 16272. Since Build 41.65, only 16261/UDP is needed for player connections — additional ports were retired with the new networking layer.
If you also want Steam server browser visibility, also forward:
| Port | Protocol | Purpose |
|---|---|---|
| 16261 | TCP | Steam server browser |
| 8766 | UDP | Steam query (optional) |
Step 1 — Find your local IP
On the machine running the server:
Windows: Open Command Prompt → ipconfig → look for IPv4 Address (e.g. 192.168.1.50)
Linux: ip addr | grep inet → use the 192.168.x.x address
Write this down. The forward needs to point here.
Step 2 — Open your router admin panel
In a browser, navigate to your router's admin interface. Common addresses:
192.168.1.1192.168.0.110.0.0.1
Log in (default credentials are usually printed on the router itself).
Step 3 — Add the port forward rule
The exact menu varies by router brand:
| Brand | Menu path |
|---|---|
| TP-Link | Advanced → NAT Forwarding → Virtual Servers |
| Netgear | Dynamic DNS / Port Forwarding |
| ASUS | WAN → Virtual Server / Port Forwarding |
| Linksys | Security → Apps and Gaming → Single Port Forwarding |
| Fritz!Box | Internet → Permit Access → Port Sharing |
Add a new rule with:
Service Name: Project Zomboid
External Port: 16261
Internal Port: 16261
Internal IP: <your local IP from Step 1>
Protocol: UDP
Save and apply. Some routers require a reboot.
Step 4 — Allow through Windows Firewall
If the server runs on Windows:
- Search "Windows Defender Firewall with Advanced Security"
- Click Inbound Rules → New Rule → Port
- Select UDP, specific port
16261 - Allow the connection, all profiles
- Name it
Project Zomboid Server
Repeat with TCP if you forwarded that too.
Step 5 — Verify the forward worked
Use an online port checker:
- Go to
canyouseeme.orgorportchecker.co - Enter port
16261and protocolUDP(note: most checkers only test TCP — for UDP tryportcheckers.com) - Start your PZ server first
- Click check
If it shows "open" — done. If it shows "closed" but the server is running, the forward didn't apply or your ISP blocks it (some CGNAT setups do).
CGNAT — when port forwarding can't work
Some ISPs (especially mobile/4G/5G internet) put you behind CGNAT (Carrier-Grade NAT). You don't get a real public IP, so port forwarding is impossible. Symptoms:
- Your "public IP" from
whatismyip.comdoesn't match the WAN IP shown in your router - Port checker says closed even with everything configured correctly
Fix: Either ask your ISP for a public IP (usually a paid extra), use a VPN with port-forwarding support (Mullvad, AirVPN), or rent a dedicated hosting tier instead. Self-hosting is genuinely impossible on CGNAT without one of these workarounds.
Tell players how to connect
Once forwarded, players connect using:
- IP: Your public IP (from
whatismyip.com) - Port:
16261 - Server name: Whatever they want — local label only
In the Join Server screen, the IP and port go in the obvious fields.
Common errors
"Connection failed" / timeout — port not actually forwarded, or wrong protocol (must be UDP, not TCP).
Players in your house can't join via public IP — NAT loopback isn't enabled on your router. They should use the local IP 192.168.x.x:16261 instead.
Server visible to you but not others — Windows Firewall is blocking UDP 16261. Re-check the inbound rule.
Public IP keeps changing — your ISP gives you a dynamic IP. Use a Dynamic DNS service (DuckDNS, No-IP) so players use a hostname instead.
FAQ
Do I need to forward port 16262 like older guides say?
No. Build 41.65+ retired the per-player port range. Only 16261/UDP matters now.
Can I change the default port?
Yes — edit DefaultPort in servertest.ini. Then forward whatever port you set.
Why is my server slow with players from far away? Self-hosting from home means upload bandwidth and routing matter. Most home connections have 10–40 Mbps upload — fine for 4–8 players, painful for 16+. A dedicated hosting tier sits on a 1 Gbps line in a datacenter near your players.
Do I need a static IP? No, but a Dynamic DNS hostname is much friendlier than telling players a new IP every week.