How to Host a Project Zomboid Server in 2026 (Dedicated, LAN, and Internet Setup)

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

For a persistent Project Zomboid world, run the free Project Zomboid Dedicated Server as a separate process, configure the generated files in your Zomboid user folder, forward the required UDP ports, and keep every player on a compatible game build. In-game hosting is fine for a one-off session, but the world stops when the host closes the game. A dedicated server can stay online while the operator is away, provided the machine, network, and backups are maintained.

This guide covers the three practical choices— in-game Host, a self-managed dedicated server, and a managed game-server service—then gives exact Windows and Linux installation paths, memory guidance, router settings, configuration locations, mod setup, backup procedures, and fixes for the failures players encounter most often.

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

Choose a hosting method before installing anything

Your choice determines who maintains the machine, whether the world remains available, and how much control you have over settings and mods.

For a long-running cooperative save, a dedicated server is normally the most flexible option. A managed service is operationally simpler; a home server is more controllable but makes you responsible for every failure and update.

#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

Check the build and save compatibility

Project Zomboid’s multiplayer server and every joining client must use compatible builds. Current 2026 setup guides report Build 42.21 Stable as of 28 September 2026. Build 41 remains available on Steam’s legacy41 branch. A Build 41 save does not load in Build 42, so select the branch deliberately before creating or migrating a world.

• Confirm the server branch in Steam or SteamCMD before the first boot.
• Have every player select the same branch and update at the same time.
• Do not assume a version number will remain current; check the live branch selector and the server files after an update.
• Back up the complete Zomboid user folder before changing branches or applying a game update.

If one player has a different build, typical symptoms include a failed connection, a server-list entry that cannot be joined, or a world that appears to be missing. Fix the version mismatch before changing ports or reinstalling files.

Dedicated-server requirements and sensible sizing

The dedicated server is a separate Java process. It needs enough memory for the world, connected players, loaded cells, Java overhead, and the operating system. Do not treat the game client’s published system requirements as a dedicated-server sizing recommendation.

Memory settings

On Windows, the supplied StartServer64.bat can request -Xms16g -Xmx16g in current distributions. That is an observation of a shipped script, not a universal minimum or a recommendation for every mod set. A machine with less available memory must use lower values, and even a machine with 16 GB installed cannot safely assign all 16 GB to the Java heap because Windows, Java’s non-heap areas, and other services still need room.

Set the initial and maximum heap to values the machine can sustain. Keep -Xms and -Xmx equal for a predictable allocation when practical, but leave overhead for the operating system and monitoring tools. If the server crashes or the operating system starts swapping, inspect the logs and actual memory use before simply increasing -Xmx.

Player limits

Current configuration guides commonly show a default limit of 32 players. Project Zomboid Wiki coverage for Builds 42.20.3/42.20.4 describes 254 players as a technical handling ceiling, not a performance guarantee. At high counts, map streaming and synchronization can degrade badly. Treat the configured limit as an administrative cap, then test the real workload with your mods, map size, and internet connection.

Practical host checklist

• A 64-bit Windows or Linux machine that can remain powered on for the intended schedule.
• Sufficient free disk space for the installation, logs, workshop content, and growing save files.
• A stable wired connection when possible, particularly for a public server.
• Administrative access to install Steam or SteamCMD, edit server files, and create firewall rules.
• A backup destination separate from the live disk. An external SSD can hold a copy of the Zomboid folder, but it is optional and is not required to run the server.

Install the Project Zomboid Dedicated Server

Windows desktop installation through Steam

1. Open Steam and select Library.
2. Change the library filter to show Tools.
3. Install Project Zomboid Dedicated Server. The server is a separate tool from the normal game client.
4. Open the installation directory and locate StartServer64.bat.
5. Start the server with that supplied script, not with Steam’s ordinary Play or Launch button.
6. On the first successful boot, wait while the server generates its configuration files. The console prompts for an initial administrator password; record it securely.

Stop the process cleanly from its console before editing configuration, copying a save, or applying an update. Killing the process while it is writing a world can leave an incomplete or inconsistent save.

Headless Windows or Linux installation with SteamCMD

SteamCMD is appropriate for a machine without the Steam desktop client. Install SteamCMD using the package or archive method supported by your operating system, then run the following command sequence from its prompt:

login anonymous
app_update 380870 validate

380870 is the dedicated-server application ID used by current setup guides. Run app_update 380870 validate again when you deliberately want to verify or repair the installed files. To operate Build 41, select the legacy41 branch instead of installing the current Build 42 branch; do not mix files from the two branches in one active world.

After installation, change to the server directory and use the supplied platform script:

• Windows: StartServer64.bat
• Linux: start-server.sh

On Linux, make the script executable if the file permissions require it, then launch it from a terminal or a service manager you control. Keep the terminal or service logs available during the first boot so you can see password prompts, bind errors, and memory failures.

Set Java heap values for your machine

Windows

1. Stop the server.
2. Open StartServer64.bat in a text editor.
3. Find the -Xms and -Xmx arguments.
4. Replace the shipped values with heap sizes that leave room for Windows, Java overhead, and any other applications on the host.
5. Save the file and start the script again.

Linux

Current Linux instructions point to Java options in ProjectZomboid64.json. Stop the server, edit the relevant -Xms and -Xmx values, save the file, and restart. The exact safe value depends on available RAM, concurrent players, loaded maps, and mods; there is no well-supported single number that fits every installation.

Diagnose memory failures instead of guessing

• If the process exits immediately, read the console and server log for an invalid heap value or an out-of-memory message.
• If the host becomes unresponsive, reduce the maximum heap and stop unrelated applications before testing again.
• If a heavily modded world needs more memory, increase it only after confirming the operating system has sufficient free RAM.
• Keep a record of the old values so you can roll back a change that makes startup worse.

Open the network path players actually need

For the default server configuration, current guides identify UDP 16261 and UDP 16262. Forward those ports from the router to the server’s local IP address when players connect from outside your LAN, and permit the same UDP traffic through the host firewall.

Router port forwarding

1. Give the server a stable local address with a DHCP reservation or a static address.
2. In the router’s port-forwarding page, create a UDP rule for external port 16261 to the server’s local address and port 16261.
3. Create the corresponding UDP rule for 16262.
4. Apply the router changes and confirm that the server is running before testing from outside the home network.

Some Steam networking paths may also use UDP 8766. Do not open every historical port list automatically: verify the active server configuration and connection path first, then add only the port that your setup actually requires. For multiple instances, assign each instance its own clearly documented port pair rather than overlapping the defaults.

Host firewall

Forwarding on the router is not enough if Windows Defender Firewall or a Linux firewall blocks the process. Allow the server executable or create inbound UDP rules for the ports in use. Test from a friend’s connection or a phone hotspot; testing only from inside the same LAN can hide a missing forward or a carrier-grade NAT limitation.

When forwarding cannot work

If your internet provider places the router behind carrier-grade NAT, inbound forwarding may never reach your machine. Ask the provider for a public address or use a managed server instead. Do not expose unrelated administrative ports to the internet just to make the game connection work.

Find and edit the generated server configuration

The first start creates server settings under the Zomboid/Server directory of the user account that runs the process:

• Windows example: C:Users<name>ZomboidServer
• Linux example: ~/Zomboid/Server

The multiplayer world saves live in the corresponding Zomboid saves area, not simply beside the installed server binaries. This distinction matters when migrating to another machine: copying only the installation directory can leave the world behind.

Common configuration responsibilities

• The server INI controls visibility, access, password settings, player limits, and other multiplayer options.
• Sandbox settings control world rules such as progression, loot, and survival difficulty.
• Public-listing fields determine whether the server advertises itself and what information players see.
• Remote-console settings are separate from the normal join password. Never publish administrator credentials in a server description or chat.

Stop the server before editing these files. Copy the generated files first, make one logical change at a time, restart, and read the console for syntax or loading errors. If you want a private server, leave public-listing fields disabled and give players the address and access details directly.

Add mods without creating a mismatch

Modded servers require two different kinds of identifiers. The WorkshopItems setting contains Steam Workshop item IDs, while Mods contains the mods’ internal loading IDs. A Workshop page name is not a substitute for either value.

1. Stop the server and back up the Zomboid folder.
2. Collect the Workshop item ID for every required mod.
3. Collect each mod’s internal ID from its metadata or the mod documentation.
4. Enter the Workshop IDs in WorkshopItems and the internal IDs in Mods, using the delimiter format shown in the generated configuration.
5. Restart the server and watch the log for download, dependency, or load errors.
6. Have every player enable the same mod set and use the same compatible game build.

Add mods in small batches. If the server stops loading, remove the last batch, confirm the base world starts, and then reintroduce items one at a time. A mod that changes maps, spawn tables, or world rules can affect an existing save even when the server itself starts normally.

Back up the world before updates or migration

The complete Zomboid user folder contains server settings and world saves. Copy that folder before changing branches, installing a large mod set, moving to another machine, or applying a game update.

A reliable backup routine

1. Announce a maintenance window and stop the server cleanly.
2. Copy the entire Zomboid user folder, including Server, saves, and relevant configuration files.
3. Store the copy on a separate disk or host. An external SSD is a practical optional destination for this copy.
4. Label the backup with the date, game build, and mod state.
5. Start the server and verify that the world and player data load.
6. Periodically restore a copy to a separate test location so you know the backup is usable.

Before an update, preserve the backup first, update the server files, then verify that all clients use the same compatible build. If the update causes a regression, stop the server and restore the previous files and Zomboid folder rather than repeatedly launching the damaged world.

Connect and verify the finished server

1. Start the server script and wait until the console reports that startup has completed.
2. From the host machine, check that the expected UDP ports are listening and that no Java or firewall error appears.
3. Join from the same LAN using the server’s local address.
4. Join from outside the LAN using the public address and forwarded port.
5. Confirm that a player can disconnect and reconnect without losing the character or world changes.
6. Stop and restart the server once, then verify that the save, settings, and mods persist.

For a public listing, fill in the listing fields in the server configuration and avoid exposing administrative passwords. For a private group, distribute only the address, port, and join password that players need.

Troubleshoot the failures that block most first launches

The server window closes immediately

• Run the supplied script from a terminal so the error remains visible.
• Check that the installed branch and server files match the clients.
• Inspect -Xms and -Xmx for values larger than available memory or malformed arguments.
• Run SteamCMD validation with app_update 380870 validate if files may be incomplete.

Players on the internet cannot connect, but LAN players can

• Confirm the server’s local IP has not changed.
• Recheck UDP forwarding for 16261 and 16262.
• Check the host firewall as well as the router.
• Test from a truly external network.
• Determine whether the internet connection uses carrier-grade NAT, which can prevent inbound connections.

The server appears, but joining fails with a version error

Compare the exact Build number and branch on the server and each client. Build 41 and Build 42 saves are not interchangeable. Update or switch the outlier, then restart the client before testing again.

Players are kicked after adding mods

• Compare the WorkshopItems list and the Mods list character by character.
• Confirm that every Workshop item has finished downloading on the server.
• Check internal mod IDs and dependencies in the startup log.
• Have players remove stale local copies and let the client redownload the required content.
• Restore the pre-mod backup if the world rules or map data became inconsistent.

The server runs but becomes unstable as players join

Watch memory use, CPU load, Java logs, and network latency while adding players gradually. Reduce the heap only if the host is starved, but do not assume a larger heap fixes every problem. High player counts, extensive map mods, and poor upstream bandwidth can cause map-streaming delays or desynchronization even when the process remains online.

Operate the server safely over time

Use a maintenance schedule

• Stop cleanly before every update, configuration edit, or backup.
• Keep the server and clients on the same supported branch.
• Review logs after restarts and mod changes.
• Keep at least one known-good backup from before the latest update.
• Remove unused mods and old log files when disk space becomes constrained.

Separate administrative access from player access

Give players only the join information they need. Store the initial administrator password securely, restrict remote-console access, and never paste credentials into a public listing, screenshot, or community chat.

Plan for migration

To move the server, stop it, copy the complete Zomboid user folder, install the same compatible server build on the destination, restore the folder under the account that will run the process, and start the supplied script. Recheck absolute paths, firewall rules, ports, and mod downloads on the new machine before inviting players back.

Decide between self-hosting and a managed service

Self-hosting avoids a provider bill and gives you direct access to scripts, configuration, logs, and backups. It also means you handle router access, operating-system updates, failures, security, and power outages. A managed service removes most machine and networking work, but its resources, backup retention, mod workflow, geographic location, and support quality vary by provider and plan.

Choose the option that matches your tolerance for maintenance. The important outcome is not the label of the host but a compatible build, a reachable server, enough resources for the actual player and mod load, and a backup you can restore.

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.