Project Zomboid Servers and Online Co-op
Join communities or host Build 42 worlds for your group in Early Access.
Finding the right Project Zomboid server matters as much as picking a good safe house. Public worlds offer populated Knox County with established bases and economy mods; private hosts give friends full control over sandbox presets, wipe schedules, and mod lists. Build 42 Early Access added quality-of-life networking fixes, but the fundamentals stay constant: matching game versions, stable saves, and agreed rules before anyone spends real-world weekends looting Louisville.
This guide explains how to join online co-op, host for friends, handle ports and admin tools, and keep long campaigns alive across patches.
Joining a public server
From the main menu, choose Join to open the server browser. Filter by ping, player count, and password requirement. Read the server name and description-many list loot multipliers, PVP status, and wipe dates.
Create your character on first connect. Some servers enforce anti-cheat or whitelist Discord roles; follow their onboarding before hauling rare loot. Expect permadeath unless the description advertises respawn kits.
New players should prefer lower zombie population servers until Combat Basics mechanics feel automatic. Hardcore 10x loot worlds tempt veterans but starve beginners of learning pressure.
Hosting friends-only co-op
Select Host from the main menu to spin a local listen server or dedicated instance. Friends connect via Steam invite or direct IP if you port-forward.
Recommended sandbox starting points for learning groups:
- Loot: normal or abundant for first campaign
- Zombies: speed shamblers, population low or normal
- Water shutoff: 0-4 days to teach urgency without instant crisis
- XP multiplier: normal-fast XP hides skill gaps that kill later
Align settings in voice chat before anyone rolls characters. Document choices in a pinned Discord message.
Port forwarding and connectivity
Dedicated hosts need 16261 UDP (default query) and game port forwarding per The Indie Stone documentation-verify current ports in official FAQ if patches change defaults. Windows firewall prompts must allow Project Zomboid when hosting.
If NAT blocks connections, use Steam relay or VPN solutions your group already trusts. Avoid mystery tunnel tools that violate server rules on public listings.
Mods in multiplayer
Workshop mods require identical load order on server and every client. Build 42 mod API shifts broke some Build 41 favorites; curate a minimal list:
- Map mods everyone agrees on
- Quality-of-life UI only if performance stays stable
- No secret client-side cheat mods on honor-system servers
After updates, wipe mods cache only when hosts instruct-blind deletes desync clients.
Saves, backups, and wipes
Server saves live in user Zomboid directories-hosts should copy Server save folders before major Early Access patches. Weekly zip backups to cloud storage prevent one corrupted file from erasing a month of co-op progress.
Schedule season wipes when loot inflation or ghost towns ruin tension. Vote transparently; surprise wipes erode trust faster than zombie bites.
Track patch impact via Build 42 Overview and Updates Hub release summaries.
In-session coordination
Use map pings and shared waypoints for loot routes planned on the Map hub. Voice beats text for helicopter passes-see Helicopter Event.
Establish loot rules: kitchen food communal, personal weapon bind unless dropped. Vehicle keys become political-assign ownership or leave spare keys in a labeled crate.
Run First Week Checklist as a group objective board during early sessions.
Admin and griefing tools
Hosts access admin menus for kick, ban, and teleport in emergencies. Private groups rarely need heavy moderation; public hosts should log repeat offenders and post rules linking to ban appeals.
There is no official report system-community reputation is the enforcement layer.
Performance and player caps
Large player counts stress simulation in dense towns. Six to eight active survivors in one cell lag more than sixteen spread across Knox County. Split loot territories instead of crowding one mall.
Lower zombie counts help CPU-heavy bases with farms and generators online simultaneously.
Early Access expectations
Multiplayer receives the same in-progress patches as solo. Expect downtime on patch days, broken mods for 48 hours, and occasional rollback saves. The game is not fully released-treat long campaigns as seasons, not permanent MMO homes.
Transition from solo to co-op
Solo veterans joining groups should suppress loot hoarding instincts-shared barricades beat personal gun collections early. Read First Week Survival with group timing in mind and defer solo night loot habits that isolate teammates.
Use Character Build Planner during session zero so occupations complement rather than duplicate.
Recommended server checklist
- Match Build 42 version numbers across clients
- Confirm mod list hash or collection link
- Agree sandbox JSON or preset name
- Pick spawn region via Map discussion
- Test voice and push-to-talk binds from Keyboard and Mouse
- Backup save before first long expedition
Frequently Asked Questions
Quick answers to the most common questions.
How do I invite friends to my Project Zomboid server?
Host from the main menu and send Steam invites, or share your public IP and port if forwarded. Everyone must match game version and mods.
What ports does Project Zomboid use for hosting?
Default UDP ports include 16261 for queries; verify the latest list in official FAQ because Early Access patches occasionally adjust networking.
Can I play co-op without mods?
Yes. Vanilla co-op is the most stable Build 42 experience. Add mods only when the whole group commits to the same workshop list.
What happens to my character if the server wipes?
Characters delete with the world unless admins migrate saves. Treat public wipes as normal Early Access seasons.
Is PVP enabled by default?
Sandbox setting-many PVE servers disable friendly damage. Read server descriptions before joining.