Project Zomboid mods: how to add Workshop mods to your server in Build 42
Published on 31 October 2026
Project Zomboid mods from the Steam Workshop go into your server’s .ini file on two lines. The Workshop ID after WorkshopItems= tells the server what to download; the Mod ID after Mods= tells it what to load. A map mod also needs its folder name after Map=. In Build 42 only mods with a Build 42 or common folder load, and players download the server’s mods automatically when they join. Checked on 31 October 2026, with Build 42.21 as the stable version.
Workshop ID, Mod ID and map folder: what goes where?
| Name | Where you find it | Line |
|---|---|---|
| Workshop ID | The number at the end of the mod’s Workshop link | WorkshopItems= |
| Mod ID | The line id= in the mod’s mod.info, or its details under Mods in the main menu | Mods= |
| Map folder | The folder name in the mod’s media/maps | Map= |
The quickest way to look them up: subscribe to the mod and open Mods in the main menu. For each mod it shows the Mod ID, the Workshop ID, the game versions it supports and the mods it needs. On every line, separate the entries with semicolons.
- One item, several mods. A Workshop item can contain more than one mod, such as optional add-ons. Its Workshop ID goes in once; after
Mods=you list only the Mod IDs you want. - Required mods. They are on the Workshop page under Required Items and in mod.info after
require=. They need both lines as well.
How to add mods to your Project Zomboid server
- Back up and stop your server, see Create and restore a backup.
- Collect the IDs of the mod and of every mod it requires, and check that it supports Build 42.
- Open the .ini file. On our servers it is in
.cache/Serverand named after the Server Name in Startup, for exampleMyServer.ini. Open it in File managers or over SFTP. - Fill in both lines, plus
Map=for a map mod, and save the file. - Start the server and watch the console. Errors also end up in
server-console.txtin the.cachefolder. - Join and test, then add the next mod. One at a time shows straight away which mod causes trouble.
Let the game write the lines. For Build 42, The Indie Stone tied every Mod ID to its Workshop ID, so players load the right mod even when two Workshop items use the same Mod ID. The surest way to get the exact notation: subscribe to the mods, choose Host and Manage Settings in the main menu, edit a settings file, add your mods and save. The game stores it as an .ini file in Zomboid/Server in your user folder. Copy its WorkshopItems= and Mods= lines into your server’s file exactly as they are.
Your other server options, such as PvP and safehouses, are in the same file: see Project Zomboid server settings.
Which mods work on Build 42?
Build 42 changed how a mod is put together. Inside the mod folder there is now a version folder, such as 42 or 42.21, and often a common folder for shared files. A mod needs at least one of the two, or the game doesn’t see it. A mod made only for Build 41 keeps its files directly in the mod folder, so Build 42 ignores it until the maker adds a Build 42 version.
- In the game: the Mods menu shows the lowest and highest game version a mod supports.
- On the Workshop: filter on the Build 42 tag. The maker picks that tag, so read the description and recent comments too.
- Java mods are a different story. On 21 October 2026 The Indie Stone stressed that only Lua mods are officially supported. Java mods usually need a manual install or a special loader, can change the game’s code directly and can break with any update. Most of them can’t be installed through the two Workshop lines, and you should only run them from makers you trust.
A modded run that stays online? On a Project Zomboid server from CakeHosting your world keeps running between game nights, with your own mod list. Cake 6 GB (€6.95) suits a group with a handful of mods. See the Project Zomboid server plans.
Map mods and the Map= line
Map= lists the map folders, separated by semicolons. Keep the default map Muldraugh, KY at the end of the line: if it comes first, it overwrites your map mods, which then load cut off or not at all. Spawn points for a new map and more on Knox Country are in the Project Zomboid map guide.
Do your players need to install the mods?
No. Workshop mods on the server are downloaded automatically when a player connects. Players do need the same game version as the server; since 42.21, anyone who connects with another version gets a message saying so. Still stuck on a mod? The PZwiki advice: close the game, unsubscribe from that mod, subscribe again and reconnect.
How to update mods after a Workshop update
When it starts, the server downloads the items on WorkshopItems=, so a restart brings mod updates in. To check first, type checkModsNeedUpdate in the console; the answer goes to the log. Then:
- Warn your players with
servermsg "Restart for a mod update in 5 minutes". - Type
saveand restart the server.
A nightly restart under Schedules does this for you, see Schedule automatic restarts. Apart from urgent hotfixes, new game versions now spend at least a week on the Pre-Release branch before they reach Stable, which gives server admins and modders time to test.
Removing a mod without breaking your world
It can be done, but the PZwiki warns that removing a mod can delete its items for good.
- Make a backup and stop the server.
- Remove the Mod ID from
Mods=, and for a map mod its folder fromMap=. Leave the Workshop ID until no mod from that item is in use. - Start the server and check that the world loads and players can join.
- Broken? Restore the backup. If a save won’t load without the mod, the PZwiki calls it permanently broken, so the backup is your way back.
Hunting for the mod behind an error? The PZwiki advises doing that on a new save. On our servers, a different Server Name in Startup gives you a fresh .ini file and world; switch back and your old world returns.
What goes wrong most often?
- The Workshop number on
Mods=. That line takes the Mod ID; the number belongs onWorkshopItems=. - Only one line filled in.
WorkshopItems=downloads,Mods=loads: a mod needs both. - A Build 41 mod. It downloads but never loads. Check the Mods menu or the Workshop page.
- A missing required mod. A mod shown in red in the Mods menu misses a mod it depends on.
- A missing semicolon between two entries, so the server reads them as one name.
- The wrong file. Your server reads the .ini named after its Server Name, not any other .ini in the folder.
- Editing while the server runs. Stop it, edit, save, then start it.
A long mod list needs more memory: 8 GB or more, and 12 GB for lots of players with lots of mods. The server size calculator helps, and you can upgrade your plan later.