Project Zomboid Server Hosting

Project Zomboid's dedicated server is a Java process that holds the whole of Knox County in memory, and memory use rises with the cells your survivors explore, the zombie population multiplier and every mod in your list. Running it on a spare desktop usually ends in heap errors. Here it sits on Ryzen 9 hardware with DDR5 ECC memory, NVMe storage and DDoS protection at no extra cost.

The panel covers day to day operations: a live console for admin commands and RCON-style output, a task scheduler for the nightly restart most modded servers need, network tools for the game and UDP query ports, and automatic daily backups with ten rolling slots protecting your entire Saves directory.

A serious Project Zomboid server is defined by its mod list. Open the server ini in the panel file manager and fill in WorkshopItems with the workshop IDs and Mods with the mod names, keeping the order your map mods require so their spawn regions resolve correctly. Add map folder names to the map line and restart from the console to let the server download the subscriptions.

Because storage is unmetered NVMe, a hundred-item mod list costs nothing extra, and unmetered databases are there if a mod or admin tool wants one. The daily backup rotation lets you test an unfamiliar mod knowing last night's working state is a single restore away from being back online.

Difficulty lives in the SandboxVars.lua file for your save: zombie speed, strength, population multiplier, loot rarity, day length, water and electricity shutoff, and experience rates. Edit it in the file manager between restarts and your changes apply to the existing world. The spawn regions file controls where new survivors start, which matters when a map mod adds a town you want as the default landing point.