Menu
 

Best Project Zomboid Server Hosting (2026): Build 42, Mods, and Backup Checklist

Last reviewed: 2026-09-02 · Build 42 dedicated-server hosting · A buyer’s decision guide, not a paid ranking

Project Zomboid rewards a persistent server: the map, sandbox rules, safehouses, loot, and character stories continue after the group logs off. It also punishes a careless update or mod change, especially when a server moves between Build 41 and Build 42 or between stable and a test branch.

The best host is the one that makes the build, Workshop collection, sandbox configuration, and save recovery visible. Use the player tiers below as a starting point, then size around the map and mod workload you intend to keep for months.

Game-specific criteriaLive plan data where availableSave and version checksNo fake provider rankings

The short version

BuildThe current Supercraft page is organized around Build 42 stable and its Workshop workflow; confirm the branch before joining.
CapacitySupercraft lists up to 5, 10, and 30 players on S, M, and L.
SimulationZombies, vehicles, towns, sandbox settings, map size, and long-running persistence shape CPU and save load.
ModsSteam Workshop maps/mods require an exact collection, load order, and client/server version match.
OperationsThe source page lists automatic backups, FTP/RCON, Build 42 handling, and four regions.

What actually matters when choosing Project Zomboid hosting

Use these checks when comparing any provider. They are deliberately tied to this game’s server model, so a high slot number or generic “unlimited” badge cannot answer them for you.

1. Build 42/stable branch correctness

A server on the wrong branch can look healthy while every player receives a version or mod mismatch.

Check: Make the target build explicit and ask how stable/test branch changes are applied and reversed.

2. Sandbox settings and map workload

Zombie population, respawn, loot, vehicles, erosion, and map size affect the server beyond the online headcount.

Check: Choose a plan for the ruleset and map you will actually run, not a default fresh world.

3. Workshop collection management

One missing dependency can block a join or break an established save. The list must be reproducible.

Check: Verify collection import, load order, update controls, client download behavior, and mod rollback.

4. CPU, RAM, and save I/O

AI, vehicles, large towns, and a long-lived save can cause tick or save delays even with few players online.

Check: Ask what CPU priority and storage are included and how the host investigates lag rather than only restarting.

5. Character and world recovery

The loss is not only the map; it is characters, safehouses, vehicles, and months of emergent history.

Check: Require scheduled/downloadable backups, a restore procedure, and a test before changing builds or mods.

6. Admin, RCON, and price transparency

A community needs moderation and safe configuration without making every change a support ticket.

Check: Compare RCON/admin access, FTP, whitelist/passwords, regions, billing terms, and upgrade behavior.

Green flags and red flags

Use these as questions for a provider, not as a substitute for testing the exact game build, map, mod list, or save.

Green flags

  • Build 42 and the active branch are named.
  • Sandbox, map, and mod load are part of sizing.
  • Workshop collections and restore points are reproducible.
  • Admins can use RCON/file access and download their saves.

Red flags

  • The provider says “latest Zomboid” with no build choice.
  • A 30-player plan is promised without map/mod/AI context.
  • Mods update automatically with no rollback.
  • Backups cannot restore characters and world state together.

Where Supercraft fits the checklist

Supercraft is the operator behind the offer shown below, so this section is an affiliation disclosure as well as a comparison. The useful claim is limited to what the corresponding hosting page actually lists; verify unusual mods, platform mixes, or capacity assumptions before ordering.

S/M/L cover 5/10/30 concurrent players, with the source page positioning M/L for Workshop and heavier communities.
Build 42 stable, automatic backups, FTP/RCON, DDoS protection, and four regions are described on the hosting page.
Use the local wiki for server setup, sandbox settings, mods, RCON, backups, and Build 42 recovery.
Start small for a private group and upgrade as the map/mod state becomes the workload.
Record the exact build, Workshop IDs, sandbox settings, and save date in every backup.

Current Project Zomboid hosting offer

These are the current plan facts collected from the canonical hosting page. Prices are loaded from WooCommerce at request time and adapt to the visitor’s store currency; no static price is embedded in the guide.

Choose a billing period
Prices are rendered from the current store currency and product data.

The cards show Supercraft’s current plan structure for this game. They are included so you can compare a concrete offer against the checklist; they are not a claim that Supercraft is objectively the best provider for every group.

See the full Project Zomboid server hosting page

Project Zomboid hosting FAQ

Which Project Zomboid build should I host?

Match the server to the build your group intends to play. The Supercraft page is maintained around Build 42 stable; do not assume a Build 41 or test-branch mod set will carry over unchanged.

How many players do the plans support?

The current tiers list up to 5 on S, 10 on M, and 30 on L. Map size, zombie settings, vehicles, Workshop content, and save age can make a smaller group the heavier workload.

Can I use Steam Workshop mods?

Yes, but the server and every client need compatible Workshop IDs, dependencies, load order, and versions. Back up the save and mod list before changing the collection.

Can I move my Zomboid save?

Choose a host that lets you download the world and player data and import them later. Keep the original copy until the new server has been tested with the same build and settings.

What makes a Zomboid host worth paying for?

Always-on uptime, stable Build 42 handling, accessible sandbox/config files, Workshop management, RCON, backups, and a safe restore path are the useful differences.

Top