Project Zomboid Dedicated Server Hosting: Full Guide

Survival in Project Zomboid isn’t just about staying alive; it’s about keeping your world alive, too. Player-hosted games often lag, crash, or vanish when the host logs off. A Project Zomboid dedicated server fixes that. It runs nonstop, saving your world and progress 24/7. 

A Project Zomboid dedicated server setup moves the heavy load off your PC and keeps every zombie, base, and survivor active even when you’re offline. For modded maps, roleplay servers, or streamers, reliable Project Zomboid server hosting means no lost saves, no downtime, and a smoother apocalypse.

Now, let’s go step by step through how to set up, configure, and optimize your own dedicated server for a world that never sleeps.

Key Takeaways

• Dedicated servers run 24/7, keeping your world alive even when you’re offline—so no more lost progress or random crashes.
• RAM scales with players: 8GB handles 4-8 players, while 16+ players need 12-24GB for stable performance.
• NVMe storage reduces lag by speeding up saves and map loading, especially critical for modded servers.
• At minimum, open 16261 UDP (main) and 16262 UDP (client). If you use RCON, also open a separate TCP port such as 27015 for remote admin.
• Use semicolons in server.ini to separate Workshop IDs and Mod IDs; commas break your mod list.
• Linux + systemd (configured correctly) offers strong uptime with automatic restarts and low overhead, but you should still ensure safe shutdown handling before relying on it.
• RCON is unencrypted; bind it to localhost or secure it with a VPN / SSH tunnel.
• Daily automated backups prevent world loss from crashes, corruption, or bad mod updates.
• High CPU clock speed matters more than cores; single-thread performance drives tick rate and world logic.
• Schedule restarts every 24 hours to clear memory creep and maintain smooth performance under heavy mods.

Server Requirements and Performance Scaling for Project Zomboid Dedicated Server

To keep your Project Zomboid dedicated server stable, you need the right mix of hardware performance and network bandwidth. A well-configured setup ensures your persistent zombie world remains live for all players without lag, crashes, or lost saves.

Players	CPU (min)	RAM	Storage	Network upload
4	4 cores @ ~3.5 GHz	6 GB	SSD	≥ 10 Mbps
8	6 cores @ ~3.7 GHz	8 GB	NVMe	≥ 20 Mbps
16	8 cores @ ~4.0 GHz	12 GB	NVMe	≥ 30 Mbps
32	10–12 cores @ >4.0 GHz	32 GB	1 TB NVMe	≥ 50 Mbps

Why Specs Matter

• CPU clock speed and core count directly impact tick rate, world logic, and mod performance in modded servers.
• RAM helps handle modded logic, player actions, and continuous saves, especially on Project Zomboid dedicated server mods.
• NVMe storage reduces I/O delays so saves and map data load faster in larger multiplayer worlds.
• Network upload ensures data flows smoothly for all connected clients; for 16-32 players, aim for at least 30–50 Mbps to avoid lag spikes or synchronisation issues.

Recommended Hardware Tiers 

Tier	Use Case	Hardware
Entry	4–8 players on light mods	4 cores, 8 GB RAM, SSD, 10 Mbps upload
Mid	8–16 players + some mods	8 cores, 12–16 GB RAM, NVMe, 30 Mbps upload
High	16–32 players + heavy mods	10+ cores, 24–32 GB RAM, 1 TB NVMe, 50 Mbps+ upload

Installation Walkthrough (Windows & Linux Step-by-Step)

Whether you’re hosting friends or building a public server, let’s walk through the fastest and most reliable way to set up a Project Zomboid dedicated server on both Windows and Linux.

Windows: Fast Setup via Steam Tools

• Install the server package
  • Open Steam → Library > Tools → search Project Zomboid Dedicated Server (App ID 380870).
  • Install it in a clear path (example: C:\PZServer).
• Locate files

Default install path:

C:\Program Files (x86)\Steam\steamapps\common\Project Zomboid Dedicated Server

• Allow required ports
  Open Windows Firewall → Inbound Rules → Add Rule → Allow UDP for:
  • 16261 UDP (main port)
  • 16262 UDP (direct connection / clients)
  • Optional: 8766–8767 UDP (legacy Steam query ports some hosts still open by default)

• Adjust memory if needed

Create a copy of StartServer64.bat (name it StartMyServer.bat), edit the copy, and set:

-Xms8G -Xmx8G

•  to match your RAM.

• First launch
  • Run StartMyServer.bat from now on.
  • Enter server name and admin password when prompted.
  • Config files (e.g., servertest.ini, SandboxVars.lua) generate automatically.

Linux: SteamCMD + Systemd for 24/7 Uptime

Install prerequisites (Ubuntu 22.04 / Debian 12 example)

sudo apt update && sudo apt upgrade -y

sudo apt install steamcmd tmux ufw -y

Create a service user

sudo useradd -m zomboid

sudo su – zomboid

mkdir ~/pzserver

Download the dedicated server (using App ID 380870)

steamcmd +login anonymous +force_install_dir ~/pzserver +app_update 380870 validate +quit

Open ports

sudo ufw allow 16261/udp

sudo ufw allow 16262/udp

sudo ufw reload

Run the server manually (first-time config)

cd ~/pzserver

./start-server.sh -servername MyWorld

On first start, it creates your config files in ~/Zomboid/Server and your world save in ~/Zomboid/Saves/Multiplayer/MyWorld (or whatever you use as -servername).

Keep it alive in a tmux session

tmux new -s zomboid “./start-server.sh -servername MyWorld”

Detach with Ctrl+B D and re-attach anytime with tmux attach -s zomboid.

Auto-Restart via systemd

[Unit]

Description=Project Zomboid Dedicated Server

After=network.target

[Service]

User=zomboid

WorkingDirectory=/home/zomboid/pzserver

ExecStart=/home/zomboid/pzserver/start-server.sh -servername MyWorld

Restart=always

RestartSec=30

TimeoutSec=300

[Install]

WantedBy=multi-user.target

Enable and start:

sudo systemctl daemon-reload

sudo systemctl enable zomboid.service

sudo systemctl start zomboid.service

Expert Tips

• Headless Linux preferred: lower idle load and fewer restarts than Windows.
• Run inside tmux/screen: keeps the server live after SSH logout.
• Ports and IDs: confirm that both App IDs (380870 for Dedicated Server, 108600 for base game) update together when validating.
• Monitor logs: check Zomboid/Logs/ for startup and network errors.

Configuration Deep Dive: Server.ini, SandboxVars, and Gameplay Settings

Let’s break down each configuration file and see exactly how it affects your Project Zomboid dedicated server settings and overall gameplay. 

Server.ini, Core Server Logic

This file manages your server identity, ports, admin roles, and connection behaviour.

# server.ini (servertest.ini or <servername>.ini)

Open=true              # True = public, False = whitelist only

AdminPassword=MySecret

RCONPassword=RConPwd123

DefaultPort=16261      # Game port

SteamPort1=8766        # Steam query

SteamPort2=8767        # Lobby

PVP=true

PauseEmpty=false       # Keeps world running when empty

What it does:

• Open toggles public or whitelist access.
• RCONPassword allows secure remote console commands.
• PVP controls player combat.
• PauseEmpty=false ensures crops grow and timers progress even when no one’s online.

Ports to open:

• 16261 UDP, Main server port (handshake + game traffic)
• 16262 UDP, Direct connection/player traffic
• Optional: 8766–8767 UDP, Legacy Steam query ports, some host templates still open

Tip: For modern dedicated servers, you only need 16261 and 16262 UDP. If your host panel pre-opens 8766–8767 or extra TCP ranges, it’s safe to leave them, but not required for normal gameplay.

SandboxVars.lua, The World Ruleset

This file defines zombie behaviour, environment, and item rarity.

SandboxVars = {

  Zombies = 2,

  ZombieRespawn = 0,

  DayLength = 2,    — 2-hour real days

  StartTime = 9,

  FoodLoot = 1,     — 1 = normal

  WeaponLoot = 0.5,

  RainStrength = 2,

  Temperature = 3,

  Transmission = 1, — bites + scratches

  WaterShut = 14,

  ElecShut = 14

}

Why it matters:

• Lower ZombieRespawn for stable populations.
• Transmission=1 enables infection realism (bites and scratches).
• Shorter DayLength keeps pacing dynamic.
• WaterShut and ElecShut add urgency for survival-based play.

Common issue: Changes don’t apply until you restart the server or delete map_sand.bin in your save folder.

spawnpoints.lua / spawnregions.lua, Player Spawning

These control where players appear in your world.

spawnregions.lua defines map regions:

function SpawnRegions()

   return {

  { name = “Muldraugh, KY”, file = “media/maps/Muldraugh, KY/spawnpoints.lua” },

  { name = “West Point, KY”, file = “media/maps/West Point, KY/spawnpoints.lua” }

   }

end

spawnpoints.lua defines exact coordinates:

{ worldX = 38, worldY = 31, posX = 120, posY = 230, posZ = 0 }

Important:

• Coordinates are case- and syntax-sensitive. Always include posZ=0 for ground level.
• If your custom map doesn’t load spawn regions, check that Map= in server.ini matches folder names exactly.
• Docker and some hosting panels skip auto-generating these files; create them manually if missing.

Example Configurations

Mode	server.ini	SandboxVars.lua Highlights
Public Survival Server	Open=true, PVP=true, no whitelist	Zombies=3, FoodLoot=1.2, WeaponLoot=1.0, Respawn=0.05
Private / RP Server	Open=false, PVP=false, whitelist enabled	Zombies=2, FoodLoot=0.8, Transmission=2 (saliva only), Respawn=0

Common Configuration Mistakes

• Case Errors: Use true/false in lowercase (that’s the standard format) 
• Mismatched Filenames: servertest_SandboxVars.lua must match your server name.
• Forgotten restarts: Edits won’t apply until the next boot.
• Missing Spawn Files: If you see only “default spawn,” create spawnregions.lua manually.

Recommended Sandbox Profiles

Profile	Recommended Settings
PvE Relaxed	Zombies=1, Respawn=0.02, FoodLoot=1.5, RainStrength=1
RP Immersive	Zombies=2, Respawn=0, FoodLoot=0.8, Transmission=2
Hardcore Realism	Zombies=3, Respawn=0, WaterShut=10, ElecShut=10, FoodLoot=0.5

• Always back up your Zomboid/Server folder before edits.
• For multiple worlds, each server instance needs a unique name and config file set.
• On Linux, run chmod +x start-server.sh after updates to avoid permission errors.
• Docker or panel users: verify config templates are current; older builds may miss new sandbox variables.

Admin Control and RCON Management

Let’s discuss how to create admins, assign roles, and manage your Project Zomboid dedicated server remotely through RCON, all while keeping your setup secure and efficient.

Run your world like a professional host.

When your apocalypse runs 24/7, you need control that’s fast, secure, and remote. This section shows how to manage admins, configure RCON, and execute commands safely, without risking your world’s stability.

Create Admins and Assign Roles

Project Zomboid servers use access levels to manage permissions. The modern, preferred method is:

/setaccesslevel “PlayerName” admin

Supported roles include:
admin, moderator, overseer, gm, observer, or none.

To create a new user on a whitelisted server:

/adduser “PlayerName” “password”

Then assign privileges:

/setaccesslevel “PlayerName” admin

Note: The older /grantadmin command still works but is considered legacy. Stick with /setaccesslevel for consistency and reliability.

RCON Setup, Secure Remote Control

RCON (Remote Console) lets you run server commands without direct access to the host.

Edit your server.ini file:

RCONPort=27015

RCONPassword=Str0ngPwd!

Bind RCON to 127.0.0.1 (safe) if using an SSH tunnel, or 0.0.0.0 (risky) if connecting via Public IP.

Then restart your server.

Important security tips:

• Choose a unique, unused port (not 16262).
• Never expose RCON directly to the internet, use a VPN or SSH tunnel.
• RCON is unencrypted by default; assume plain text transmission.

Connect using an RCON client like rcon-cli:

rcon -a 123.45.67.89:27015 –password Str0ngPwd! “help”

You’ll receive instant console responses, just like local admin access.

Essential Command Table

Command	Function
/setaccesslevel “Player” admin	Grants admin privileges
/removeadmin “Player”	Revokes admin rights
/banuser “Player” -ip -r “reason”	Bans a player by name and IP
/servermsg “text”	Sends a global message
/save	Instantly saves world data
/changeoption Option “Value”	Edits live server settings (e.g., PVP=false)
/quit	Gracefully shuts down the server

Each command works through both the in-game console and RCON. Use them carefully,  especially /quit, which ends the active session.

Example RCON Usage

Example of checking connected players and sending alerts:

rcon -a 123.45.67.89:27015 –password Str0ngPwd! “players”

rcon -a 123.45.67.89:27015 –password Str0ngPwd! “servermsg \”Server restarting in 5 minutes!\””

You can automate this for daily restarts or backups using cron or PowerShell scripts.

Security Best Practices

• Always use complex passwords with letters, numbers, and symbols.
• Restrict RCON access to trusted IPs only.
• Rotate credentials if any admin leaves your team.
• Avoid sharing console logs containing the RCON password.

Managing Mods & Workshop Content Like a Pro

Keep your world stable, fast, and easy to update. This guide goes beyond “paste an ID” and shows real workflows for Project Zomboid dedicated server mods on any Project Zomboid server host.

Workshop ID vs Mod ID 

The following table highlights the workshop ID vs mod ID

Term	What it is	Where you find it	Use it for
Workshop ID	Numeric Steam item ID (e.g., 2286124930)	On the mod’s Steam Workshop URL	Downloading the mod to the server
Mod ID	The mod’s internal load name from mod.info (e.g., BritaArmor)*	…/mods/<ModName>/mod.info (mod_id=…)	Loading/activating the mod on the server

*The Mod ID is not the workshop title. It’s the mod_id value inside mod.info.

Correct Configuration In server.ini

Use semicolons as separators. Put Workshop IDs in WorkshopItems= and Mod IDs in Mods=. Keep dependency order first in Mods=.

# server.ini (excerpt)

SteamWorkshopEnabled=true

WorkshopItems=2286124930;2932848597;2985484631

Mods=ModDependency;CoreFramework;YourMainMod

Map mods: also add the map folder to the Map= line and keep “Muldraugh, KY” at the end:

Map=YourMapFolder;Muldraugh, KY

How SteamCMD Auto-updates Mods

• On start, the server checks WorkshopItems= and auto-downloads/updates listed items.
• You can force a refresh during maintenance with SteamCMD:
  • steamcmd +login anonymous +workshop_download_item 108600 <WorkshopID> validate +quit
• After updates, restart the server to load new versions.

Troubleshooting (fix issues fast)

Symptoms → Fixes

• Mod doesn’t load: Confirm the Mod ID (from mod.info) is in Mods=, not the Workshop ID.
• Only first mod works: You used commas. Switch to semicolons in both lines.
• Version mismatch / red errors: Stop the server, remove the mod’s folder in steamapps/workshop/content/108600/<WorkshopID>, then re-download or validate.
• Map not selectable: Check Map= order and exact folder names; base map must end the line.
• Missing deps: Add all required mods and load them first in Mods= (see dependency chain below).
• Stuck cache / weird conflicts: Clear the server’s Zomboid/Workshop or the specific workshop item folder, then restart.

Performance Impact (be ruthless with your list)

• Large mod packs increase RAM, load times, and can reduce tick stability.
• Trim overlaps (don’t run two overhaul mods that touch the same systems).
• Group heavy mods together and test in batches.
• Watch memory and CPU during peak hours; remove the top offenders. Your players will feel the difference.

Expert Tip: Respect the Dependency Chain

If Mod A requires Mod B and C, the Mods order must load B and C before A:

Mods=RequiredLib;ArmorCore;YourArmorPack

Load order lives in Mods=, not WorkshopItems=.

Sample Profiles You Can Copy

Small survival server (stable, light QoL)

WorkshopItems=2286124930;2985484631

Mods=QoLCore;SmallTweaks

Heavier RP server (framework + content packs)

WorkshopItems=2932848597;2985484631;3011122244;3045567788

Mods=RPFramework;RPAnimations;VehiclesPlus;ClothingPack

Rule: list dependencies first; then frameworks; then the big content packs.

 Troubleshooting: Real Fixes to Real Problems

Every issue has a cause and a direct fix. Here’s how to solve the problems that clog most Project Zomboid dedicated servers, and keep your world alive without wipes or resets.

Common Problems and Proven Fixes

Here are the common problems and proven solutions. 

Problem	Cause	Fix
Server not responding	Closed UDP ports.	Open these ports on your host or router: 16261 UDP (main), 16262 UDP (client). (Optional: 8766–8767 UDP for legacy templates.)
Mods not loading	Mod ID and Workshop ID mismatch, or dependency order wrong.	Confirm IDs in server.ini: WorkshopItems= uses Workshop IDs, Mods= uses mod_ids from mod.info. Use semicolons (;) and load dependencies first. Restart to apply.
RCON connection refused	Wrong password, same port as client, or no encryption.	Use a different port (e.g., 27015), strong password, and connect via VPN or SSH tunnel. Example:

“rcon -a 123.45.67.89:27015 –password MyStrongPwd “players”

Never expose RCON publicly, it’s unencrypted by default. Always restrict it through a VPN or SSH tunnel.

If your save becomes corrupted after a crash or version mismatch, follow this order:

1. Stop the server immediately to prevent overwriting autosaves.
2. Copy your latest backup folder and rename it to match the corrupted save’s name.
3. Replace the map_ver.bin file inside the corrupted world with one from a working or freshly created save.
4. Restart the server and check if it loads normally.
5. If corruption persists, restore additional .bin files like chunkdata_x_y.bin and map_p.bin from your backup.

Log File Locations (for real debugging)

Logs tell you what went wrong.

Windows:

C:\Users\<User>\Zomboid\Logs\

Linux:

~/Zomboid/Logs/

Look for these patterns:

• “Connection failed” → check ports/firewall.
• “Error loading mod” → bad ID or missing dependency.
• “World version is 0” → corrupted save version file.
• “RCON refused connection” → wrong password or bad network rule.

Open logs with Notepad++ or less for easier reading; errors are often within the last 50 lines.

 Pro Recovery Workflow for Corrupted Worlds

• Stop the server immediately (don’t overwrite auto-saves).
• Go to your Zomboid/Saves/Multiplayer/<servername> folder.
• Copy a backup folder from /Backups/.
• Rename it to the same as the corrupted world.
• Copy map_ver.bin and missing .bin files from a new save or backup.
• Restart and check the console for version sync messages.

Recovery works best if mods and versions match exactly between old and backup saves.

Performance Optimization and Backup Automation

The following proven optimization steps help you maintain consistent tick rates, reduce crashes, and keep automated backups running without manual intervention. Perfect for advanced users managing a dedicated Project Zomboid server or high-population worlds.

CPU Optimization

Project Zomboid’s dedicated server is mostly single-thread dependent; the main simulation and chunk updates run on one core.

You’ll get the biggest gains from high-clock CPUs and smart process pinning.

# Run the server on a specific CPU core with higher priority

nice -n -5 taskset -c 2-4 ./start-server.sh -servername MyWorld

• taskset binds the process to a specific core range. We use a range (e.g., 2-4) rather than a single core to ensure the Java Garbage Collector has room to run without freezing the main game loop.
• nice -n -5 raises priority for smoother tick handling.
• Works best on CPUs with strong single-core clocks (e.g., AMD Ryzen 7000 / Intel i7-13700K+).

Expected benefit: small but noticeable stability gains (smoother ticks and lower CPU spikes), especially under modded, 20-player+ loads.

Automated Backups

Backups prevent permanent loss from crashes, mod conflicts, or corruption. Use this simple script:

#!/bin/bash

# daily backup at 3 AM

rsync -a –delete /home/zomboid/Zomboid/Saves/Multiplayer/MyWorld /backups/pz/MyWorld_$(date +%F)

tar -I zstd -cf /backups/pz/MyWorld_$(date +%F).tar.zst /home/zomboid/Zomboid/Saves/Multiplayer/MyWorld

Then schedule it with cron:

0 3 * * * /usr/local/bin/pz_backup.sh

• rsync keeps incremental copies for fast recovery.
• tar + zstd compresses backups efficiently.
• Store at least 7 daily backups and one weekly archive off-disk or in cloud storage.

Daily Restarts

Even well-optimized servers can show memory creep, especially with mods or long sessions.
Set an automated restart to reclaim memory and clear temporary cache:

30 4 * * * /usr/local/bin/pz_maint_pz_a.sh

Make sure your maintenance script sends a save and quit (via RCON or a FIFO) before it stops the service, so the world shuts down cleanly.

• Restarts clear heap fragmentation and stale Lua allocations.
• Recommended once every 24 hours during low-traffic hours.
• Prevents “gradual lag” from long uptimes rather than fixing a guaranteed leak.

Advanced Management, Persistence, Automation, and Scaling

Let’s discuss advanced management, persistence, automation, and scaling for serious hosts running growing player communities

Persistent Saves: How Your World Stays Alive

Every server name creates its own save namespace:

Default path (Linux):
~/Zomboid/Saves/Multiplayer/<ServerName>/

Each instance must have a unique -servername and matching configuration. Always back up the entire folder (including .bin files and map_ver.bin).

Best practice:

1. Stop the server before backing up.
2. Use rsync or tar for consistent copies.
3. Keep seven daily and one weekly backup, store at least one off-box or off-region.

Never snapshot while the server is saving. Some hosts support atomic snapshots, but manual backups after shutdown are safest.

Running Multiple Servers on One Machine

You can host multiple instances if you give each one unique names, ports, and save paths.

Example Configuration

• Instance A: -servername PZ_A → Ports 16261/UDP, 16262/UDP, Steam 8766–8767
• Instance B: -servername PZ_B → Ports 16271/UDP, 16272/UDP, Steam 8776–8777

# /etc/systemd/system/[email protected]

[Unit]

Description=Project Zomboid (%i)

After=network.target

[Service]

User=zomboid

WorkingDirectory=/home/zomboid/pzserver

ExecStart=/home/zomboid/pzserver/start-server.sh -servername %i

Restart=always

RestartSec=30

[Install]

WantedBy=multi-user.target

Start both:

sudo systemctl enable –now zomboid@PZ_A

sudo systemctl enable –now zomboid@PZ_B

Avoid port conflicts:
Double-check that client, RCON, and Steam query ports (e.g., 8766–8767) don’t overlap between instances.

Automating Updates, Restarts, and Backups

Use a daily cron job during low activity (e.g., 04:00 UTC) to refresh and safeguard your server.

#!/bin/bash

rcon -a 127.0.0.1:27015 –password “$RCON” ‘servermsg “Maintenance in 2 minutes”‘

sleep 120

rcon -a 127.0.0.1:27015 –password “$RCON” save

systemctl stop zomboid@PZ_A

steamcmd +login anonymous +app_update 380870 validate +quit

WORLD=/home/zomboid/Zomboid/Saves/Multiplayer/PZ_A

STAMP=$(date +%F)

rsync -a –delete “$WORLD” /backups/pz/PZ_A_$STAMP

tar -I zstd -cf /backups/pz/PZ_A_$STAMP.tar.zst -C “$WORLD” .

systemctl start zomboid@PZ_A

Cron entry:

0 4 * * * /usr/local/bin/pz_maint_pz_a.sh

Use UTC in cron to avoid timezone drift during daylight changes.

Docker or Containerized Deployment

Developers or DevOps teams can containerize servers for version control and automation.

Guidelines:

• One container per instance.
• Map unique ports and mount save/config volumes.
• Persist workshop cache and SteamCMD files.
• Set proper permissions (UID/GID) so the container can read/write to host volumes.

Example Compose:

services:

  pz_a:

    image: your/pz:latest

ports:

      – “16261:16261/udp”

      – “16262:16262/udp”

      # Optional legacy ports if you really want them:

      # – “8766:8766/udp”

      # – “8767:8767/udp”

    volumes:

      – /data/pz/PZ_A:/home/zomboid/.local/share/Zomboid/Saves/Multiplayer/PZ_A

    command: [“./start-server.sh”,”-servername”,”PZ_A”]

Add health checks and scheduled container restarts to prevent memory creep.

Why This Step Matters

• Persistence: Isolated save structures prevent world corruption and simplify backup rotation.
• Scalability: Multi-instance hosting lets you run PvE, PvP, or RP worlds on the same hardware.
• Stability: Scheduled restarts and validated updates keep uptime consistent for months.
• Automation: Cron or Docker workflows cut manual downtime and recovery effort.

Why Choose RedSwitches for Your Project Zomboid Server Hosting

When it comes to survival worlds that never sleep, performance and reliability aren’t optional, they’re everything. RedSwitches gives you both, with enterprise-grade infrastructure built specifically for demanding multiplayer environments like Project Zomboid.

Launch your world in minutes with instant provisioning, and never worry about lag or downtime again. Every server comes with unmetered bandwidth, ensuring your gameplay stays smooth even with heavy mods, high player counts, or automated map backups. Our 99.99% uptime guarantee means your world stays online, even when you’re offline.

Need migration? We’ll handle it free of charge. Our global 24/7 support team responds in under five minutes, keeping your community running without interruptions. 

Start your Project Zomboid dedicated server on RedSwitches today and experience unmatched speed, stability, and scalability.

FAQ

Q. How many players can I host on 8 GB RAM?

You can comfortably host around 6–10 players on 8 GB RAM, depending on map size and mod count. For larger or modded servers, upgrading to 16 GB or more is recommended for smoother tick rates.

Q. Can I host on Linux or Windows?

Yes. Project Zomboid supports both Linux and Windows dedicated servers. Linux offers better performance and uptime for 24/7 hosting, while Windows is easier for beginners to configure.

Q. What ports need to be open?

Open 16261 (UDP) and 16262 (UDP); for most home and dedicated setups that’s enough to get players connected. If you use RCON, also open 27015 (TCP). Some guides and host templates also open 8766–8767 (UDP) and a TCP range like 16262–16272; those are optional for most modern dedicated servers but safe to leave open if your host enables them by default.

Q. How do I fix mod mismatches?

Ensure every player has the same Workshop and Mod IDs in the same order within Server.ini. Clear the server’s mods cache and force a Workshop re-download if errors persist after updates.

Q. What’s the cheapest way to host a Project Zomboid server?

Self-hosting on your PC is free but unstable. For reliable performance, get a dedicated Project Zomboid server from RedSwitches, offering affordable bare metal servers with unmetered bandwidth and instant setup.