Self-Hosted vs Managed Project Zomboid Servers (B42)

Build 42 multiplayer dropped, your group wants to play, and now you need a server. You have three real options: run it on your own hardware, rent a managed game server, or spin up a VPS. Each one has genuine tradeoffs, and the right answer depends on how you actually play.

This is an honest breakdown. If self-hosting makes sense for your situation, we’ll say so. If managed hosting is the better call, we’ll explain why. The goal is to help you pick the right setup and stop researching.

Self-Hosting: Running PZ on Your Own Hardware

Self-hosting means installing the Project Zomboid dedicated server on a machine you control - your gaming PC, a spare desktop, or a home server. It’s the most hands-on option and costs nothing beyond what you already have.

What You Actually Need

Hardware: Build 42 is hungry. The server alone needs 6-8GB of RAM for a small group (2-4 players), and that’s before your operating system and anything else running on the machine. Larger or modded groups need more - see our RAM guide for the full breakdown by player count and mod load. If you’re hosting on the same PC you play on, you need enough RAM for the game client and the server - that’s 24-32GB total to be comfortable. CPU matters too: PZ benefits from strong single-core performance, and Build 42’s simulation is heavier than Build 41.

Network: A stable connection with at least 5-10 Mbps upload. More important than raw speed is consistency - packet loss and jitter cause rubber-banding that no amount of bandwidth fixes.

Ports: You need to forward UDP 16261 (handshake) and TCP 16262 (map streaming) through your router. If you want more than a few player slots, you may need additional TCP ports in the 16262-16272 range.

Operating system: Windows or Linux both work. Linux is lighter on resources if you’re comfortable with command-line server management.

The Real Cost of “Free”

Self-hosting has no subscription fee, but it’s not free.

Electricity: A desktop running 24/7 draws 100-200W depending on the hardware. At the US average of about $0.16/kWh, that’s $12-23/month just in power. A laptop draws less, but laptops aren’t designed to run under constant load for months.

Hardware wear: Hard drives, fans, and power supplies have finite lifespans. Running a machine 24/7 accelerates wear. You probably won’t notice this for months, but it’s a real cost over time.

Your time: Setting up SteamCMD, configuring the server, troubleshooting port forwarding, applying updates, managing saves - this is time you could be playing. Some people enjoy the tinkering. If that’s you, it’s a feature, not a cost.

Opportunity cost: While your PC is running a server, it’s using resources you might want for other things. Build 42 servers using 8-16GB of RAM is RAM you can’t use for anything else.

Where Self-Hosting Works Well

• Short sessions with friends. If everyone plays at the same time and you shut the server down after, self-hosting is simple and practical.
• You already have a spare machine. An old desktop with 16GB of RAM and a decent CPU makes a fine PZ server for a small group.
• You want to learn. Setting up a game server from scratch teaches you about networking, Linux administration, and server management. That knowledge has value beyond Project Zomboid.

Where Self-Hosting Falls Apart

Port forwarding and CGNAT. This is where most self-hosting attempts die. You need to access your router’s admin panel, set up port forwarding rules, and hope your ISP isn’t using Carrier-Grade NAT (CGNAT). If they are, no amount of router configuration will make your server reachable from the internet. CGNAT is increasingly common, especially with mobile ISPs, some fiber providers, and most ISPs outside North America. You can check by comparing the WAN IP on your router with your public IP - if they don’t match, you’re behind CGNAT.

Uptime. Your server is only online when your machine is on and the server process is running. Power outages, Windows updates forcing a restart, someone bumping the power strip - these all take the server down. If your group plays across different time zones or wants to drop in whenever, this is a real limitation.

Build 42’s frequent patches. Build 42 reached the stable branch with version 42.20, so you’re no longer opting into an unstable beta to run it - but it still gets patched often, sometimes multiple times a week. Each update requires you to manually update the server, and everyone needs to be on the same version to connect. Miss an update and half your group can’t join. On some updates, the server binaries change enough that you need to validate files or re-download through SteamCMD.

Security. Opening ports on your home network exposes your IP address to anyone who connects. For a private server with trusted friends, this is usually fine. For a public server, you’re inviting strangers to know your home IP and send traffic to your network.

Managed Game Server Hosting

Managed hosting means renting a server from a hosting provider that handles the infrastructure. You get a control panel, the server files are pre-installed, and you manage the game settings without worrying about the underlying machine.

What You Get

A control panel for starting, stopping, and configuring your server without touching command lines or config files.

Automatic backups. No more manually copying save folders to a USB drive. Most hosts run scheduled backups, though frequency and retention vary wildly between providers.

Always-on uptime. The server runs in a data center with redundant power and network connections. Your friends can connect at 3 AM regardless of whether your PC is on.

Support. When something breaks, you can ask support for help instead of searching through Steam community posts and Reddit threads.

No port forwarding. The server gets a public IP or a port allocation that just works. No router configuration, no CGNAT issues.

What You Give Up

OS-level access. You’re working within the hosting provider’s control panel, not a full operating system. If you want to run custom scripts, install additional software alongside PZ, or do things the panel doesn’t support, you’ll hit walls.

Some control over timing. When the host updates their node software or does maintenance, your server may go down briefly. Good hosts schedule this during off-peak hours and notify you. Bad ones don’t.

What It Actually Costs

Build 42’s RAM requirements make this more expensive than hosting some other games. Here’s what the market looks like for PZ Build 42 hosting:

Prices vary significantly between hosts. Some charge per-GB (like WinterNode at $1.99/GB), while others sell fixed plans where the per-GB cost goes up or down depending on which tier you pick. Watch out for “first month” discounts that make plans look cheaper than they actually are - the price doubles on month two.

VPS / Cloud Hosting: The Middle Ground

A VPS (Virtual Private Server) gives you a virtual machine in a data center with root access. You install everything yourself - SteamCMD, the PZ server, any dependencies - but you get 24/7 uptime and a real public IP without managing physical hardware.

When a VPS Makes Sense

• You want full control over the operating system and can install whatever you want alongside PZ
• You plan to run multiple game servers or other services on the same machine
• You’re comfortable with Linux command-line administration
• You want to learn server administration with a real-world project

When It Doesn’t

• You’re paying more than managed game hosting for the same RAM, because you’re renting a general-purpose VM instead of optimized game server hardware
• You’re the sysadmin now - OS updates, security patches, firewall configuration, and troubleshooting are all on you
• No game-specific control panel unless you install one yourself (something like Pterodactyl or AMP)
• If the PZ server crashes at 2 AM, there’s no support team restarting it for you unless you’ve set up watchdog scripts

For Build 42, a VPS with 8-16GB of RAM typically costs $20-60/month depending on the provider, the CPU specs, and whether you’re getting dedicated or shared resources. That’s often more than managed game hosting for the same RAM allocation, and you’re doing all the work yourself.

Which Option Fits Your Situation

There’s no universally correct answer here. It depends on how you play and what you value.

“We play together on weekends and don’t need the server up otherwise.” Self-host. Start the server when you play, shut it down after. Zero cost, minimal hassle. One person hosts, everyone else connects. Just make sure you can forward ports - check for CGNAT first.

“We want a persistent world that’s always online.” Managed hosting. You want uptime, backups, and the ability for anyone in your group to connect whenever. The $16-32/month is worth not having to leave a PC running 24/7 and hoping nothing goes wrong.

“I want root access and plan to run other services too.” VPS. You get full control and always-on uptime. Just know you’re signing up to be the server admin for everything, not just PZ.

“I’m not sure yet and want to start simple.” Start with managed hosting. You can always migrate your save files to self-hosted or a VPS later if you outgrow it. Going the other direction - from a broken self-hosted setup to managed - usually happens after someone spends a weekend fighting port forwarding and gives up.

Confirm the Migration Actually Worked

If you’re moving an existing world from a self-hosted setup to managed hosting, don’t consider it done until you’ve checked these four things:

• The world loaded correctly. Your base, inventory, and explored map match where you left off, not a fresh world.
• Your intended mods are available. Everything from your mod list is installed and enabled, not just the vanilla save.
• Friends can actually join. Have at least one other person connect and confirm before you call the migration finished.
• You understand the backup/restore route. Know where to find backups in the panel and how to restore one, before you need it under pressure.

The upload steps themselves - compressing your Zomboid folder, uploading it via File Manager or SFTP, and matching your port and server name - are covered in our world migration walkthrough.

What to Look for in a Project Zomboid Host

If you go the managed hosting route, not all hosts are equal. Here’s what actually matters for Project Zomboid, especially with Build 42:

Build 42 out of the box. This is table stakes right now. Build 42 reached the stable branch with version 42.20, so a new server should default to it without any beta opt-in. Where branch-switching support still matters is the other direction - rolling back to legacy Build 41 if a mod you rely on hasn’t been ported yet. Look for a panel option or startup parameter that lets you switch branches without contacting support.

Enough RAM. Build 42 needs 6-8GB for a small group (2-4 players), and 12-16GB or more is safer if you plan to run mods or have more than 4-5 regular players. If a host tries to sell you a 4GB PZ server for Build 42, they either haven’t tested it or don’t care whether it works.

No CPU limits. PZ’s simulation is CPU-intensive, especially during horde events and when many players are exploring different map cells simultaneously. Hosts that oversell their nodes or impose hard CPU caps will limit your server during the moments it needs performance the most.

File access. You need to be able to upload mods, edit sandbox settings, and manage save files. SFTP access is important for larger file transfers - a web file manager works for quick edits but becomes painful for uploading mod collections.

Backup frequency and retention. Backups matter more for PZ than most games because world saves are large and a Build 42 patch can still change how a save behaves even on the stable branch. Daily backups are good. Twice-daily is better. Check how long they keep backups too - 7 days is too short if you don’t notice corruption for a week.

Support quality. Can you get help from someone who understands PZ, or are you talking to a generic support agent following a script? This matters most on Build 42, since it still gets patched often enough that new issues surface between updates.

How WinterNode Handles PZ Hosting

We built our hosting around the problems PZ server owners actually have, and Build 42 hasn’t changed that approach - just the scale of what the server demands.

New servers run Build 42 by default. No beta opt-in needed. If you need legacy Build 41 instead - for an unported mod, say - branch switching is a panel option in Server Options followed by a reinstall, no tickets or waiting. Our beta branch guide walks through the steps.

RAM starts at $1.99/GB with no CPU limits. An 8GB Build 42 server costs $15.92/month. A 16GB server for larger groups costs $31.84/month. Your server uses whatever CPU it needs under our fair usage model - no hard caps on cores, and we keep nodes running well under capacity so burst headroom is real rather than theoretical.

Backups run every 12 hours with 45-day retention. That’s 90 restore points at any time. When a patch breaks something, you can roll back to before the update without losing more than half a day of progress.

Unmetered storage. PZ world saves grow over time as players explore more of the map. You won’t hit a storage cap or get charged extra as your world expands.

Mod support with full SFTP access. Upload mods through the file manager for quick additions, or connect via SFTP for bulk mod uploads. The choice is yours depending on how many files you’re moving.

Support from people who play PZ. When you open a ticket about Build 42 desync or a mod conflict, you’re talking to someone who has actually dealt with it - not someone reading from a troubleshooting script for the first time.

Get your Project Zomboid server →

If you’re setting up a Build 42 server for the first time, our multiplayer setup guide covers the full process from ordering to connecting. For tuning your server settings, the sandbox settings guide breaks down what each option actually does.