Can you add mods to an existing Project Zomboid save?

⚡ The short answer

Yes, in most cases, and without starting over. Three caveats: the mod has to match your game version (Build 41 or Build 42), map mods are the exception, and removing a mod is riskier than adding one. Before you touch anything, back up the save.

💾 In a single-player save

Enabling the mod in the Mods menu on the main screen isn't enough: that doesn't change saves that already exist. You have to add it to the save itself:

• From the main menu go to Load, not Continue, and select your save.
• Click More… and then Choose mods.
• Enable the new mod and anything it requires, confirm, and load the save.

Saves are stored in C:\Users\YOUR_NAME\Zomboid\Saves. Copy your save's folder somewhere else before you change its mods.

🖥️ On a server

In multiplayer, mods don't depend on each player but on the server's configuration. They live in two lines of the servertest.ini file (in the Zomboid/Server folder), separated by semicolons:

• WorkshopItems= holds the Workshop numbers: what the server downloads.
• Mods= holds the Mod IDs: what the server loads. One Workshop item can contain several Mod IDs.

You add the new mods to both lists and restart. The world and the characters stay, and players get the mods when they connect.

At ZentexNode you don't edit that file: in the panel's Mods tab you paste the link to a mod or to a Steam Workshop collection, and the server loads them on the next restart. The steps are in how to add mods to Project Zomboid.

🗺️ What you'll notice and what you won't

Type of mod	On a world already in progress
Interface, sound, quality of life	Works from the next load.
Items, recipes, vehicles	Recipes usually show up right away. New loot and vehicles mostly in areas you haven't visited yet.
Maps	Only if nobody has been through that area yet. What's already generated isn't replaced.
Mods that ask for a "new save"	Do what their Workshop page says.

The reason is that the game decides what's in each area the first time someone passes through it, and saves it. A mod added later doesn't rewrite what's already saved, so to see its content you'll need to explore new areas. Maps work the same way, but with no simple fix: if the area of the new map has already been visited, the reliable route is a new world.

⚠️ Removing mods is the risky part

Once a world has used a mod, removing it orphans its objects: that mod's furniture, containers and vehicles disappear along with whatever was inside, and there are cases where the save, or the server's world, stops loading. If a mod has already placed things in your world, the sensible move is to leave it enabled. And if something breaks after you remove one, enable it again or restore your backup.

🔢 Build 41 and Build 42

Build 42 has been the stable version since 29 July 2026 and includes multiplayer. Build 41 saves don't work on Build 42, and neither does a mod that hasn't been updated for Build 42: check its Workshop page before adding it. If you want to carry on with a Build 41 world, Steam keeps the legacy41 branch.

✅ The safe way to do it

• Back up before every change. On a ZentexNode server you do it from the panel: how to create and restore backups.
• Add mods a few at a time, restart, and join to check everything works before going on.
• Read each mod's Workshop page: game version, dependencies, and whether it asks for a new save.
• If a mod depends on another one, the base mod goes first in the list.

If you play with friends and the world lives on one person's PC, a Project Zomboid server keeps it open for everyone, with mods managed from the panel and a backup at hand before every change.