Project Zomboid Server Stuck Initializing: How to Fix It

A Project Zomboid server stuck initializing has nearly always hit one of six problems: a Workshop mod that will not download, a broken or conflicting mod, a Map= line in the wrong order, a memory setting (-Xmx) the machine cannot give, a port that another process already holds, or a server and mods on different builds (Build 41 vs Build 42). You do not have to guess. The server log names the cause: open server-console.txt, read the last lines before it stopped, and search for STACK TRACE.

What "stuck initializing" really means

A dedicated server that finishes starting prints a clear line. The PZwiki Multiplayer FAQ shows it as *** SERVER STARTED ***. If you never see that line, the console stops moving, or the process closes and starts over, the server failed somewhere along the way. Before it can print that line, the server has to:

• start Java with the memory set in -Xms and -Xmx;
• read servertest.ini and servertest_SandboxVars.lua (the file names follow -servername);
• download and check every Workshop item in WorkshopItems=;
• load the mods in Mods= and the maps in Map=;
• load or create the world and open its UDP ports, 16261 and 16262 by default.

Find the cause in the server log first

The PZwiki Tech Support page points to two log files: server-console.txt for a dedicated server and coop-console.txt for a game hosted from the in-game Host menu. Both sit in the Zomboid folder: %USERPROFILE%\Zomboid on Windows and ~/Zomboid on Linux. The game client writes its own console.txt in the same folder.

Stop the server and open server-console.txt at the end: the last lines show what it was doing when it stopped. Then search for STACK TRACE. The PZwiki says many errors can be found this way, and the lines below it often name the mod or file that failed.

Fix 1: Workshop mods that never finish downloading

A dedicated server downloads the items in WorkshopItems= by itself on every start. If one item cannot be downloaded, startup stalls right there. Two lines in servertest.ini work together, as the Server settings page explains: WorkshopItems= takes the numeric Workshop IDs, and Mods= takes the mod IDs from each mod's mod.info. Both lists are separated by semicolons. The values below are placeholders:

WorkshopItems=1111111111;2222222222
Mods=ExampleModA;ExampleModB

Check these points:

• Every Workshop ID still opens in Steam and is public. An item its author removed or hid cannot be downloaded by your server.
• Each Workshop item has its mod ID in Mods=. One Workshop item can hold several mods, each with its own ID.
• Install with SteamCMD. The PZwiki Tech Support page says that servers which stall while fetching mods were often installed with the "Dedicated Server" tool from the Steam client library, and recommends a SteamCMD install instead.
• Test without mods. Empty both lines, start the server, and add the mods back in small groups.

Our guide on how to add mods to a Project Zomboid server shows where to find each ID.

Fix 2: a broken mod, a conflict or a missing dependency

When the downloads finish but the server dies while it loads Lua files, the STACK TRACE usually names the mod. The PZwiki's Resolving problems with mods page and the Mods page list the usual reasons:

• A missing dependency. Many mods need another mod to run. The mod's mod.info lists it on a require= line, and the Workshop page usually names it too. The required mod also has to be in WorkshopItems= and Mods=. In the in-game mod list, a mod shown in red is missing a dependency.
• An outdated mod. The PZwiki warns that mods made for older versions of the game are likely not to work with new ones.
• Two mods that change the same thing. Each works alone, and together they crash.

To find the culprit quickly, split the list in half:

1. Back up servertest.ini.
2. Remove half of the mods from Mods= and their items from WorkshopItems=.
3. Start the server. If it now reaches SERVER STARTED, the problem is in the half you removed. If not, it is in the half that stayed.
4. Repeat with the guilty half. With 40 mods you find the culprit in about six restarts.

Fix 3: Map= is in the wrong order

A map mod needs its map folder name in Map=, besides its entries in Mods= and WorkshopItems=. The default map is Muldraugh, KY. The PZwiki Tech Support page says the Muldraugh map overwrites other modded maps, so it has to go last; when it comes first, your modded maps lose priority. Put your modded maps first and Muldraugh, KY at the end:

Map=ExampleMapMod;Muldraugh, KY

• The value is the map's folder name. It is not the Workshop ID, and it can differ from the mod ID.
• Write Muldraugh, KY exactly, with the comma and the space.

Fix 4: the memory setting (-Xmx) does not fit the machine

The server is a Java program. -Xms sets the memory it reserves at start and -Xmx the most it may use. The PZwiki Dedicated server page warns that StartServer64.bat ships with 16 GB, and that if you do not edit -Xms and -Xmx to fit your machine the server fails to start with memory errors. On Linux and macOS, the Tech Support page says to change -Xmx in ProjectZomboid64.json.

The PZwiki rule of thumb is at least 3 GB for the server plus about 500 MB per player, and more with mods. The Multiplayer FAQ also says not to use more than 80% of the machine's RAM, and the Startup parameters page warns that a value above the physical RAM pushes the server into slow virtual memory.

One more trap from the Tech Support page: a global Java option left in the Windows environment variables, such as -Xmx512m, can cap the memory of every Java program on that PC, the server included. Our post on Project Zomboid server requirements covers sizing in detail.

Fix 5: the ports are already taken

Project Zomboid uses UDP 16261 (DefaultPort) and UDP 16262 (UDPPort) by default, plus 27015 for RCON when RCONPassword is set. Only one program can hold a port. If an old copy of the server never closed, or a second server on the same machine uses the same numbers, the new one cannot open them.

• Close the old process in Task Manager on Windows, or find it with ps on Linux, then start again.
• For a second server on the same machine, give it other ports with -port and -udpport, or with DefaultPort and UDPPort in its own .ini.

Closed ports on your router do not stop the server from starting. They stop players from joining, which is a connection problem.

Fix 6: Build 41 vs Build 42 (server, mods and save must match)

Build 42 has been the stable branch since 42.20 on July 29, 2026, and Build 41 now lives in the legacy41 beta, according to the developers' announcements. A SteamCMD install takes the current branch unless you ask for another. To stay on Build 41:

steamcmd +force_install_dir /opt/pzserver +login anonymous +app_update 380870 -beta legacy41 validate +quit

• Mods. The PZwiki's Mod structure page shows that Build 42 mods use a 42 folder and a common folder, which Build 41 does not recognize. A mod can ship both layouts, but many support only one build. Read each mod's Workshop page before you add it.
• Saves. The developers say Build 41 saves are not compatible with Build 42. Do not point a Build 42 server at a Build 41 world: start a new world, or move the server back to legacy41.
• Backups. The official advice is to back up before you switch branches.

Not sure which build to run? Read Project Zomboid Build 42 vs Build 41.

Fix 7: repair the server files

If the errors point to the game's own files and not to a mod, often after an update that was interrupted, run SteamCMD again with validate, which checks the install and downloads anything missing or damaged. Your settings and saves live in the Zomboid folder, outside the install folder, but back that folder up anyway before you start.

steamcmd +force_install_dir /opt/pzserver +login anonymous +app_update 380870 validate +quit

A Project Zomboid server stuck initializing on TheGameHosting

Half of these problems come from running the server on a home PC. On TheGameHosting's Project Zomboid hosting that half is handled, and you only deal with your mods:

• Memory that matches the plan. Project Zomboid starts on our 8 GB plan ($6.96 USD/month), and large mod lists move up to 12 or 16 GB. If you think the memory setting does not match your plan, check the Startup tab or ask us in the chat.
• Console shows the startup live, so you see the exact last line when something fails.
• Files opens servertest.ini, the sandbox file and the logs in your browser, and full SFTP access handles big uploads.
• Backups before every mod change or build switch, and Schedules for automatic restarts.
• No port forwarding. The panel gives you the IP and port to share, with DDoS protection included.
• AMD Ryzen 9950X and 7950X3D CPUs up to 5.7 GHz, DDR5 RAM and Samsung NVMe storage, in Dallas or Amsterdam.

If the log still makes no sense, our support team answers 24/7 by chat, email and tickets. Send them the last 50 lines of the log and your Mods=, WorkshopItems= and Map= lines.

Checklist: Project Zomboid server stuck initializing

1. Read the end of server-console.txt and search for STACK TRACE.
2. Start once with empty Mods= and WorkshopItems=. If it starts, the cause is a mod.
3. Check that every Workshop ID exists, is public and has its mod ID in Mods=.
4. Add each dependency from the require= line of the mods you use.
5. Put Muldraugh, KY last in Map=.
6. Set -Xmx by the 3 GB + 500 MB per player rule and stay under 80% of the RAM.
7. Close any old server process that holds UDP 16261 or 16262.
8. Match the server branch, the mods and the save: Build 42, or Build 41 on legacy41.

A server that hangs at start costs you an evening of digging through files. If you would rather spend it playing, pick a plan with enough RAM for your mod list: your Project Zomboid server is ready about 60 seconds after payment, runs 24/7 without your PC, and comes with Backups to roll back the next mod that breaks it.

FAQ

Hosting for these games

• Project Zomboid hosting8 GB plan from $6.96/month
• 7 Days to Die hostingSurvive the blood moons together
• DayZ hostingYour own Chernarus, online 24/7