
Project Zomboid's Steam Workshop has thousands of mods, from new cars and guns to whole new towns. Adding them to a dedicated server is simple once you know the one thing that trips everyone up: every mod has two different IDs, and the server needs both.
Stop the server and open its settings file, servertest.ini by default. Add each mod's Workshop ID (the number in its Workshop URL) to WorkshopItems= and its Mod ID (listed on the Workshop page) to Mods=, separated by semicolons. Map mods also go in Map=, before Muldraugh, KY. Start the server and it downloads everything; players get the mods automatically when they join.
| Detail | Workshop ID | Mod ID |
|---|---|---|
| What it is | The Steam Workshop item | The mod inside that item |
| Looks like | A number: 1234567890 | A name: ExampleMod |
| Where to find it | At the end of the Workshop page's URL (?id=…) | At the bottom of the Workshop description, or in the mod's mod.info |
| Goes in | WorkshopItems= | Mods= |
The Workshop ID tells the server what to download. The Mod ID tells it what to turn on. Most mod pages list both at the bottom of the description, as Workshop ID: and Mod ID:.
One Workshop item can contain several mods: a main mod with optional add-ons, or separate versions for different builds of the game. List the Workshop ID once, then only the Mod IDs you want to turn on.
A Project Zomboid server reads its settings from an .ini file named after the server: servertest.ini, unless you changed the server name. It's in the Server folder of the server's Zomboid data folder, next to servertest_SandboxVars.lua (the sandbox settings) and servertest_spawnregions.lua. Edit it in the panel's file manager or over SFTP.
A running server can write over its settings file, so stop it before you edit anything.
For each mod, note its Workshop ID and Mod ID. Then check the Required items box on its Workshop page: those are other mods it needs, and they need both IDs too.
Find the WorkshopItems= and Mods= lines and add your IDs, separated by semicolons without spaces:
WorkshopItems=1234567890;2345678901;3456789012
Mods=ExampleLibrary;ExampleMod;ExampleMod_AddonMods load in the order the Mods= line lists them, so put libraries first and add-ons or patches after the mods they change. The order of WorkshopItems= doesn't matter.
The server downloads every Workshop item before it finishes starting, so the first start after adding mods takes longer. Watch the console for errors that name a mod.
Players don't need to subscribe to anything. When they connect, the game downloads the server's mods for them, so the first join takes a little longer too.
Mods made for Build 41 don't work on Build 42, and the other way around. The server and every player have to be on the same build, and the server only loads mods made for the build it runs.
\ExampleMod. If your Mods= line already lists mods that way, add new ones the same way.Map mods need a third line. Find the map's folder name on its Workshop page (usually listed as Map Folder) and add it to the Map= line, before the vanilla map:
Map=ExampleTown;Muldraugh, KYMuldraugh, KY always stays last. Map mods still need their Workshop ID and Mod ID on the other two lines, too. On an existing save, new map areas only appear in parts of the world nobody has explored yet, because areas players have visited are already saved.
On our Project Zomboid server hosting, you can install Steam Workshop mods with one click from the control panel, manage mod collections and keep everything updated, without touching the ini. Build 42 is supported, and daily backups protect your save. Plans start at $8.99/month, and the most popular 20 GB plan handles 32–64 players.
When a mod gets an update on the Workshop, players who download the new version can't join a server that is still on the old one: they get an error saying a Workshop item doesn't match the server's. Restart the server and it downloads the latest versions.
Mods= or spelled differently. Copy it exactly, capitals included.WorkshopItems=, or the item is private or friends-only, which the server can't download.Map= before Muldraugh, KY, and that you're looking at an area nobody had explored yet.If you remove a mod, the items, vehicles and buildings it added can break or disappear from your world. Take a backup before you remove one, so you can roll back.
Not directly: the ini file has no setting for collections, so every item's IDs have to be listed one by one. Our control panel can manage collections for you.
No. The game downloads the server's mods for them when they join.
Usually, yes. Most mods work on an existing save, but map mods only change unexplored areas and some big overhauls ask for a new save. Back up first either way.
There's no fixed limit, but every mod adds memory use and startup time. Big mod lists need more RAM, and you can upgrade your plan later without losing your save.
Project Zomboid servers from $8.99/month, with Build 42 support, one-click Workshop mods, daily backups and free DDoS protection.