Upload Configs
Configuration files are small, but they define how the whole server behaves. Uploading them without checking names, map order, and mod references can break a healthy world faster than a bad loot run ever could.
What Config Files Usually Control
| Server rules | Passwords, pause behavior, anti-cheat posture, and administrative options. |
|---|---|
| Sandbox behavior | Loot, zombies, utilities, XP pace, and other world-level rules. |
| Mods and maps | Workshop references, map stack order, and any related start-up expectations. |
Upload Process
- Back up the current live config before you replace anything.
- Compare the incoming config against the current world name, map list, and workshop IDs.
- Upload the files with the server stopped so they are not overwritten or read mid-change.
- Restart and validate joining, world loading, and mod synchronization before you announce the update.
High-Risk Mistakes
- Applying a config from a different server name or world profile.
- Changing map order by accident while updating only one seemingly harmless file.
- Treating workshop and map configs as interchangeable when they are not.
Verified 2026 Detail
Config migrations are easiest when the server branch has not changed underneath you. Because Project Zomboid still treats unstable betas as a distinct opt-in lane, a copied config should be read like a branch-specific artifact, not a universally portable profile.
Current Official Note
The official Project Zomboid site still separates stable from unstable testing builds. That matters for config moves too: a server profile copied from one branch can look valid at a glance while still referencing assumptions that no longer match the target build.
Need a stable place to test changes before you touch a live world? Launch your Project Zomboid server with Supercraft.