Project Zomboid supports online co-op, and Steam lists a “Cross-Platform Multiplayer” feature. However, the official Build 42 multiplayer information does not publish a complete Steam-to-GOG, store-to-store, or PC-to-console compatibility matrix. Treat crossplay beyond an explicitly supported client/server route as unconfirmed. Before you buy or configure a server, make sure every player uses the same game branch and build, then verify that the server accepts that client version.
Godlike.Host offers hosted Project Zomboid servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
For a small group, the in-game Host option is the simplest route. A dedicated server keeps the world available when the host is offline, while managed hosting removes much of the machine and network administration. Build 42 multiplayer is still a work in progress, so stability, mods and updates need more care than in a finished release.
As an Amazon Associate I earn from qualifying purchases.
What “crossplay” means in Project Zomboid
Crossplay can mean several different things: players on different operating systems, players who bought the game from different stores, or PC players joining console players. Those are separate compatibility questions.
Steam’s feature metadata lists both Online Co-op and Cross-Platform Multiplayer. That label confirms that cross-platform play is a supported feature category, but it does not identify the participating stores, operating systems, console editions, server software or build combinations. It should not be read as a promise that every PC storefront and console can connect.
#1 Best Overall
- UPDATED CLASSIC: Dive into Zombicide: 2nd Edition, the thrilling update to the classic zombie-slaying game. Experience enhanced gameplay and new challenges in the zombie apocalypse.
- COOPERATIVE SURVIVAL: Join forces as Survivors in a world overrun by zombies. Work together to navigate through missions, complete objectives, and fight for survival.
- ADRENALINE-POWERED ACTION: With each zombie kill, increase your Adrenaline Points. Gain strength and skills but attract more zombies with your actions – a double-edged sword.
- INTENSE MISSIONS: Face a series of challenging missions, each requiring strategic planning, teamwork, and bravery. Can you accomplish your objectives while fending off the undead?
- SURVIVE OR BECOME ZOMBIE PREY: The stakes are high - will you emerge as a triumphant survivor or fall victim to the relentless zombie hordes?
Steam and GOG
The Build 42 multiplayer rollout was Steam-first. Build 42 was published on Steam’s Unstable branch, and The Indie Stone said the latest 42.13 build would be uploaded to GOG only when it was stable enough and had likely hotfixes. The announcement does not state that Steam and GOG clients can already share a server.
That makes Steam-to-GOG play unconfirmed rather than guaranteed or disproven. If your group owns different editions, check the exact build number and the server’s supported client route after both editions have received the same release. Do not rent or configure around cross-store play based only on the Steam metadata label.
PC and console
The official Build 42 multiplayer announcement does not establish a PC-to-console compatibility path. No console client, console server route or complete platform matrix is specified in the supplied official information. Until The Indie Stone publishes an explicit statement for a particular console edition, assume that PC and console players cannot be promised access to the same server.
Build 42 multiplayer status and important limits
On December 11, 2025, The Indie Stone released Build 42 multiplayer as a work in progress for stress testing. Its announcement says, “Multiplayer is WIP and has been released for stress testing.” That status affects how you should plan a persistent world: updates can change compatibility, saves can be disrupted, and a configuration that works one week may need repair after an Unstable update.
The same announcement says, “For the best experience you are STRONGLY advised to play on whitelisted servers or in Steam co-op.” It also says, “It is currently inadvisable to have more than 20 players on a server. This will be further improved.” These are stress-test recommendations, not a permanent player limit. They are the safest guidance for groups using the early Build 42 multiplayer releases.
Future Unstable updates are another operational risk. The announcement warns, “Please be aware that future updates to the Unstable branch WILL disrupt ongoing MP games.” Back up server saves before changing branches or applying an update, and schedule updates when nobody is playing.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Compatibility checklist before anyone joins
Use this checklist when a friend cannot connect or when you are deciding whether a mixed-store group is viable:
- Match the branch: Everyone should be on the same branch, such as the same Build 42 testing branch, rather than mixing stable and Unstable clients.
- Match the complete build: Compare the displayed build number, not merely “Build 42.” A 42.13 client and a later 42.20.x server are not automatically interchangeable.
- Confirm the client path: The server administrator should identify whether the server is intended for Steam clients or another explicitly supported route. Cross-store support is not established merely because Steam displays a cross-platform label.
- Coordinate mods: Build 42 stress-test guidance says to disable all mods, including client mods. If a server eventually uses mods, every client must have the same Workshop items and mod identifiers in the same configuration.
- Back up the world: Copy the server save before updates, branch changes or large mod changes.
- Check networking: Confirm the server address, UDP ports, firewall rules and any router forwarding required for an internet connection.
Project Zomboid multiplayer server options
| Option | Best for | Persistence | Administration | Main trade-off |
|---|---|---|---|---|
| In-game Host / Steam co-op | A small group that plays together | World ends when the host closes or crashes | Lowest setup effort; host carries game and server workload | Players depend on the host being online, and the host PC’s CPU, memory and connection handle the combined load |
| Dedicated server | A persistent world, a rented machine or a separate home server | Runs independently of an individual player’s game client | Install software, edit configuration, manage ports, builds, mods, backups and updates | More setup and security responsibility |
| Managed server hosting | Groups that want persistence without maintaining a home machine | Normally designed for an always-on world; verify the provider’s terms | Provider supplies a control panel and machine; you still manage game settings and mods | Recurring price and provider-specific limits; current pricing is not established here |
Option 1: host a small game with Steam co-op
In-game Host is the quickest choice when the same person usually organizes sessions and the group is small. It also follows The Indie Stone’s stress-test advice to use Steam co-op for the best experience.
- Launch Project Zomboid on the agreed branch and build.
- Choose the in-game Host option and create or select the world settings.
- Keep mods disabled during the Build 42 stress-test period unless the server administrator has verified a compatible configuration.
- Invite the group through the game’s Steam co-op flow and have every player join the same hosted session.
- Keep the host client running while others play. Closing the game or suffering a crash ends the hosted world session.
This approach avoids installing a separate server process and usually avoids manual port work for a Steam-only group. The cost is availability: the world is tied to the host’s play schedule. The host computer also renders the game while handling the hosted session, so crowded areas, animals, basements, large maps or heavy mod workloads can affect everyone.
Option 2: run a dedicated server
A dedicated server is a separate process or machine. It is the appropriate choice when the world should remain available after players log off, when a group rents a server, or when you want to separate server workload from the player’s game client.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Install the server software
The dedicated-server guide documents two installation routes:
- Desktop installation: In the Steam library, open the Tools list and install Project Zomboid Dedicated Server.
- Headless installation: Use SteamCMD on a machine that does not need the normal game interface.
- Launch the server once. Its first start generates the configuration files.
- Stop it cleanly, then edit the generated
servertest.inifile for the server name, password, gameplay settings and other options.
Keep the server files on the same branch and build as the clients. After a Steam update, update the dedicated-server files too; a client can be current while the server remains on an older build.
Open the network ports
For internet play, the guide lists these default UDP ports:
- 16261: the main Project Zomboid server port.
- 16262: the Steam networking port.
- 8766: used depending on the Steam networking path.
The exact port use can depend on the networking route and your configuration. Allow the required ports through the host machine’s firewall and forward them on the router when the server is inside a private home network. Expose only the ports you need, use a strong password, and avoid publishing administrative credentials.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesJoin a dedicated server
- Open Project Zomboid and select Multiplayer.
- Choose Add server.
- Enter a recognizable server name, the server IP address, the configured port and the password.
- Join only after confirming that the client branch, build and mod list match the server.
A dedicated server remains available when the administrator closes the game, but it does not administer itself. Assign someone to monitor updates, backups, logs, restarts, passwords and mod changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Option 3: use managed Project Zomboid server hosting
Managed hosting rents the machine and provides tools for a persistent multiplayer world. It is useful when nobody wants to leave a home PC running, configure router forwarding, or perform every operating-system and server maintenance task.
Because Build 42 compatibility is still evolving, ask a provider these questions before paying:
- Can the service run the exact Build 42 branch and build your group needs?
- Can you pin a build, roll back after an update and schedule restarts?
- What player limit is configured, and is it a marketing ceiling or a tested recommendation?
- Can you control Workshop items and the
Modssetting? - How often are saves backed up, how long are backups retained, and can you download them?
- Where is the server region, and what latency should players in different locations expect?
- What are the current recurring price, cancellation terms and support response times?
No universal managed-hosting price or provider capability is established here. Compare those details directly, and do not assume that a host advertising a high slot count supports the same Build 42 features or mod workflow your group requires.
Player capacity, hardware and performance
The dedicated-server documentation says Build 42.20.3 improved handling for up to 254 players. That number is a capacity ceiling, not a promise of a smooth 254-player experience. Actual performance depends on the machine, map size, animals, basements, mods, player behavior and other workload.
The initial Build 42.13 multiplayer stress-test guidance advised against more than 20 players. For a new world, start well below any advertised ceiling, measure stability and increase the population only if the server remains responsive. A smaller, stable server is preferable to a nominally large server that regularly loses connections or corrupts a save.
Steam’s current desktop listing, accessed October 14, 2026, lists 8 GB of RAM and 10 GB of storage among the game requirements. The Windows listing specifies 64-bit Windows 10 or 11 and a 2.77 GHz quad-core processor; macOS and Linux have separate requirements. These are requirements for running the game client, not a universal sizing rule for a dedicated server. A server process may need different resources depending on player count and world activity.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshooting common connection failures
“Incompatible version” or immediate disconnect
Compare the full build number on every client and the server. Update the dedicated-server files after a Steam update, and make sure nobody is mixing stable and Unstable branches. If an Unstable update disrupted the world, restore the pre-update backup only after confirming that the group will remain on the matching build.
The server appears offline
Check that the server process is running, then verify the IP address and port in Multiplayer → Add server. On a home connection, confirm router forwarding and the host firewall rules for the required UDP ports. A local address may work inside the home network but not for friends connecting from the internet.
Players load different content or are rejected for mods
Disable all mods while stress-testing Build 42. If you intentionally enable mods later, compare the server’s WorkshopItems and Mods settings with every client. Remove outdated entries, update the server files and restart before asking players to reconnect.
Lag, rubber-banding or world stalls
Reduce the number of simultaneous players and heavy world activity, then observe CPU, memory and network use on the host. Animals, basements, large maps and mods can increase workload. Do not treat the 254-player figure as a performance target.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe world is unavailable whenever one person leaves
That behavior is normal for in-game Host. Move the save to a dedicated server or managed host if the group needs an always-on world.
Which option should you choose?
- Choose Steam co-op when a small group plays at the same time, one person can remain host, and the priority is minimal setup.
- Choose a dedicated server when the world must persist between sessions, someone can handle installation and backups, or you want server workload separated from a player’s PC.
- Choose managed hosting when persistence matters but nobody wants to maintain a home machine, router rules and operating-system updates. Confirm Build 42 support, backups, mod controls, region and current price first.
Whichever route you select, settle the client path before inviting people: same branch, same build, coordinated mods and a server route that explicitly accepts those clients. That is the reliable way to avoid treating a broad storefront feature label as a crossplay guarantee.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
