Project Zomboid Multiplayer: How to Play With Friends (Host, Dedicated Server, and Build Compatibility)

For a small group, the quickest way to play Project Zomboid together is the in-game Host option: create server settings, start the world, then invite friends through Steam or the in-game Esc → Invite menu. You do not need a dedicated server. Choose a dedicated server only when the world must remain available while the usual host is offline. Before anyone joins, make sure every player is on a compatible game branch, because Build 41 saves cannot be used with Build 42.

Prefer not to run the server on your own PC? Godlike.Host offers hosted Project Zomboid servers with free DDoS protection and up to three free backups a day.

Choose the right multiplayer setup

Project Zomboid offers two practical ways to play with friends. An in-game Host session uses one player’s normal game client as the server. A dedicated server runs separately, either on another desktop or on a headless machine, so the world can continue without the host’s game client.

#	Preview	Product	Price
1		Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board...		Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

If you just want to play tonight with a few friends, use Host. If the group needs to enter the same world at different times without waiting for one person to launch the game, use a dedicated server.

Check branches and saves before setting anything up

Version compatibility is the first requirement. Every player and, for a dedicated setup, the server itself must be on a compatible branch and build string. A connection problem caused by different builds cannot be fixed by changing a password or forwarding a port.

#1 Best Overall

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

• 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?

Buy on Amazon

Build 41 and Build 42 are separate save environments

The official Build 42 checklist dated July 28, 2026 states: “Build 41 savegames clearly will not be compatible with Build 42.” If your group needs to continue an existing Build 41 online world, select the legacy41 beta in Steam’s Game Versions & Betas menu for every player. Do not open that save in Build 42 expecting it to convert safely.

Selecting Build 42 on Steam

1. Open the Steam library and right-click Project Zomboid.
2. Choose Properties.
3. Open the Betas tab.
4. Select Unstable to use Build 42.

Everyone joining the same session must make the same branch choice. A dedicated server must also be updated or rolled back to the matching build string.

What the current Build 42 multiplayer warning means

In an official Steam announcement dated December 11, 2025, The Indie Stone wrote that “Multiplayer is WIP and has been released for stress testing.” That announcement strongly advises Steam co-op or whitelisted servers, recommends disabling debug and mods, and says more than 20 players is currently inadvisable. It also warns that future Unstable updates can disrupt ongoing multiplayer games.

Those warnings apply specifically to the Build 42 stress-test situation described in that announcement. If your group values a stable long-running save, avoid changing an Unstable installation mid-campaign, keep a backup before updates, and check current official notices before moving the server to a newer Unstable build.

How to host a game for friends

The in-game Host flow is the least complicated option for a small group. The host’s computer runs the world while that player is in the session.

Create and start the hosted world

1. Start Project Zomboid and select Host.
2. Choose Manage settings.
3. Select Create new settings.
4. Configure the world and server options your group wants.
5. Save the settings, then start the server from the Host screen.
6. Wait until the world has finished loading before sending invitations.

The exact settings you choose determine the rules of that world. Save the configuration with a recognizable name so you can select it again instead of creating a new world accidentally.

Invite friends

Once the hosted world is running, press Esc and choose Invite, or use Steam’s normal invite function. Send the invitation only after the host is in the world; an invitation to a game that has not finished starting can appear unavailable to the recipient.

What the host must keep in mind

• The host’s game client is also the server process, so closing the client ends the hosted session.
• A crash or forced exit can make the world unavailable until the host starts it again.
• The host should use a stable internet connection and avoid changing the game branch while the group is using the save.
• If the group wants to play at different times, move to a dedicated server rather than leaving one player responsible for launching the Host session.

How friends join a hosted game

For a Host session, the normal route is accepting the Steam invitation. A friend can also use the in-game invitation workflow when the host sends it from Esc → Invite.

If an invite does not appear, confirm that the host has actually started the world, that both accounts are online in Steam, and that both installations are on the same Project Zomboid branch and build. Do not start changing router settings until those basic checks pass; branch mismatches and mod mismatches are more common first causes.

When a dedicated server is worth the extra work

A dedicated server is optional, not a prerequisite for multiplayer. Its defining advantage is persistence: the server can remain running when the person who originally configured it is not playing. This is useful for a group that plays on different schedules or wants a shared world available throughout the day.

The trade-off is administration. Someone must install the server software, keep its build aligned with clients, maintain configuration files, monitor logs, arrange network access, and make backups. A dedicated server is therefore a better fit for a persistent world, not automatically a better fit for a three-person session that happens once a week.

Self-hosting versus renting infrastructure

• Self-hosting: install the server on a desktop or headless machine you control. You retain direct access to files and settings, but you are responsible for uptime, updates, network configuration, and backups.
• Rented hosting: a provider supplies an always-on machine. The operational details vary by provider, so confirm the supported Project Zomboid build, mod controls, backup tools, and port access before committing.

No single recurring price applies to all dedicated arrangements. The meaningful comparison is whether the convenience of an always-on machine justifies the provider charge or the maintenance time of running your own hardware.

Set up a Project Zomboid dedicated server

The official dedicated-server path supports both a normal desktop installation and a headless machine. The following sequence reflects the documented workflow.

Install the server application

1. On a desktop, open Steam’s Tools list and install Project Zomboid Dedicated Server.
2. For a headless machine, install the server application with SteamCMD.
3. Place the server on reliable storage; the community guide recommends an SSD for hosting.
4. Make sure the machine has a stable internet connection and enough memory for the planned player count.

Generate and edit the configuration

1. Run StartServer64.bat on the Windows installation.
2. Allow the first launch to finish. It generates the initial configuration files.
3. Back up the generated configuration before making edits.
4. Edit servertest.ini to set the server’s options.
5. Confirm that the server and every client use the same build string.
6. Start the server again and watch its console output for errors before asking friends to connect.

The first launch is important because editing a file before the server has generated its defaults can lead to missing or incorrectly named settings. Keep a known-good copy of servertest.ini so you can restore it after an unsuccessful change.

Match the server’s mod entries

For a dedicated server, the WorkshopItems and Mods entries must match the mod set the server is meant to load. Client-side selections do not automatically synchronize a dedicated-server INI. If those lists disagree, players can be rejected, fail to load the world, or see different content.

Network and port requirements

The community multiplayer guide lists 16261 as the default Project Zomboid port. The dedicated-server guide notes that forwarding may involve UDP 16261 and 16262, with 8766 depending on the Steam networking path. Treat these values as version- and network-path-sensitive rather than universal router instructions.

• First verify the server’s current configuration and documentation for the exact build you are running.
• Forward only the ports that your current server setup requires, using UDP where the documentation specifies it.
• Check the machine’s local firewall as well as the router; opening a router port alone does not guarantee that the server process can receive traffic.
• Have a friend test from outside your home network. A local connection test can succeed even when outside connections are blocked.

Do not use port forwarding as the first response to every join failure. Confirm the branch, build, server status, password, IP address, and mod state first. Router changes are unnecessary for many Steam co-op problems and can create a new security or maintenance burden.

Server memory, storage, and practical capacity

A current Steam community guide by Aiteron, Beard, and Spiffo gives a rule of thumb of 2 GB starting memory plus approximately 500 MB for each planned player. This is operational community advice, not an official minimum specification.

These figures are planning estimates, not guarantees. Mods, world activity, map size, other programs on the machine, and the current game build can change actual use. Leave headroom rather than allocating every megabyte the computer has available.

The same guide recommends an SSD and stable internet connection for hosting. An SSD can reduce storage-related delays, while a stable connection helps prevent disconnects; neither resolves a branch mismatch or an incorrectly configured server.

For Build 42 multiplayer, the official announcement’s current guidance says more than 20 players is inadvisable. Treat that as a warning about the stress-test state, not as a target capacity.

Mods and clean Build 42 testing

For the Build 42 multiplayer stress-test period described by the official announcement, disable all mods, including client-only mods. This removes a major source of incompatibility while you establish that the base game can connect.

1. Exit the game on every client and stop the dedicated server if one is running.
2. Disable all subscribed and locally enabled mods, including mods that do not add server content.
3. Start an unmodded Host session or dedicated server.
4. Test that every player can join on the same branch and build.
5. Only after the clean test succeeds, add mods deliberately and keep the server’s WorkshopItems and Mods entries aligned with the clients.

Adding several mods at once makes a failure difficult to isolate. Change one logical set at a time and keep a backup of the working configuration before each change.

Troubleshoot “my friend can’t join” in the right order

Use this sequence instead of changing several variables simultaneously.

1. Confirm the exact branch and build

Ask every player to check Steam’s selected beta and compare the server’s build string with the clients. Build 41 and Build 42 are not interchangeable, and a Build 41 save cannot be loaded in Build 42. If the group is continuing a Build 41 world, select legacy41 for all participants.

2. Remove mods temporarily

Disable every mod, including client-only mods, and retry with a clean world. On a dedicated server, compare the WorkshopItems and Mods entries rather than assuming the clients synchronized them automatically.

3. Check that the server is actually running

For Host, the host must be inside the world; closing or crashing the host client ends that session. For a dedicated server, inspect the server console and logs after startup and after the failed connection attempt. A server that stopped during launch cannot accept a friend regardless of the invite method.

4. Recheck join details

For a dedicated server, use Join/Multiplayer and enter the server name or IP, the configured port, any required password, and the player’s account credentials. A single wrong digit in an IP address or port produces the same broad symptom as a deeper network problem.

5. Investigate ports and firewalls

Only after the build, mods, server state, and join details are correct should you check router forwarding and local firewall rules. Verify whether the current setup needs UDP 16261, 16262, and, on some Steam networking paths, 8766. Follow the documentation for the exact version instead of forwarding every number found in an old guide.

6. Check memory and machine stability

If the server starts but becomes unstable under load, compare available memory with the community rule of 2 GB plus about 500 MB per planned player. Also check that the server is using an SSD as recommended and that other applications are not consuming the machine’s resources.

7. Account for Build 42 stress-test limitations

If you are on Build 42 Unstable, remember that multiplayer is described as work in progress and stress testing in the cited official announcement. Keep the group small, prefer Steam co-op or a whitelisted server as advised there, disable debug and mods, and expect future Unstable updates to disrupt ongoing multiplayer games.

Protect a shared world from avoidable losses

A persistent world is valuable only if you can recover it. For a Host session, the host should preserve the world and its settings before changing branches or experimenting with mods. For a dedicated server, the operator should back up both the save data and configuration, especially servertest.ini, before edits or updates.

• Keep a dated copy of the last known-good configuration.
• Back up before switching between Build 41 and Build 42; the saves are incompatible.
• Back up before adding, removing, or updating mods.
• Do not update an Unstable server while friends are actively using the world.
• Record the branch, build string, server port, password policy, and mod lists so a replacement machine can be configured consistently.

Which setup should your group choose?

Choose Host when

• Two or more friends are playing at the same time.
• The group wants the shortest setup process.
• Everyone can use the same branch and a clean mod state.
• It is acceptable for the world to stop when the host leaves.

Choose a dedicated server when

• The world must remain available while the original host is offline.
• Players have different schedules.
• One person is willing to maintain builds, ports, logs, mods, memory, and backups.
• The group accepts the additional setup and possible hosting cost.

For most small friend groups, start with Host and Steam invitations. Move to a dedicated server only when persistence is the requirement that the Host flow cannot provide. Whichever route you choose, branch compatibility, a matching build string, and a mod-free first test will prevent more failures than changing network settings at random.

Quick Recap

Bestseller No. 1

Zombicide 2nd Edition Strategy Board Game | Cooperative Game for Teens and Adults | Zombie Board Game | Ages 14+ | 1-6 Players | Avg. Playtime 1 Hour | Made by CMON

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.