Project Zomboid · More guides

Project Zomboid Build 41 vs Build 42 for servers

Build 42 or Build 41 for your Project Zomboid server? What changed for servers, why worlds and many mods don't carry over, and how much RAM each needs.

By Last reviewed 4 min read

For most groups, Build 42 is the right choice. It’s the current stable version of Project Zomboid, it’s what Steam gives players by default, and it gets the fixes and new content. Pick Build 41 only if your group wants to finish a Build 41 world or depends on mods that haven’t moved to Build 42.

The short answer

Build 42 Build 41
Status Current stable version since 29 July 2026 Older version, kept for existing servers
Steam branch Default (public) legacy41
Multiplayer Yes, since 42.20 on the stable branch Yes, mature and well known
New content and fixes Yes Occasional security fixes only
Mods Growing, but many older mods aren’t updated yet The biggest library of server mods
RAM About a third more Less
Worlds Can’t load Build 41 worlds Can’t load Build 42 worlds

What changed for servers in Build 42

Build 42 is the biggest update Project Zomboid has had. For a server owner, these are the changes that matter:

  • Multiplayer arrived later. Build 42 was single player only at first. Multiplayer came to the testing branch in version 42.13 in December 2025 and reached the stable branch with 42.20 on 29 July 2026.
  • A bigger, busier world. Build 42 adds animals and farming with livestock, basements, a reworked Knox County map with new buildings, and much more crafting. More world means more for the server to keep in memory.
  • Reworked anti-cheat. 42.20 switched the anti-cheat back on with server-side checks and better logs for admins.
  • New server options. For example, you can show or hide map coordinates for everyone, and the player lists show each player’s ping.
  • A pre-release branch. Since 42.22, new versions go to a “Pre-Release” branch for at least a week before they reach stable. Server admins can use it to test mods before an update lands.
  • Mod changes. Build 42 changed how mods are built, and server files now write mod IDs with a backslash in front. See mods.

The newest stable version on 12 November 2026 is 42.22.2.

Which build to choose

Choose Build 42 if:

  • You’re starting a new world.
  • Your friends just bought the game or play on the default Steam branch.
  • You want animals, basements and the new map.

Choose Build 41 if:

  • You have a Build 41 world you want to keep playing.
  • Your group depends on big Build 41 mod packs that don’t support Build 42 yet.
  • Everyone in your group is happy to switch their game to the legacy41 branch.

Whichever you pick, everyone has to be on the same build as the server. See joining a Build 41 server.

Worlds don’t carry over

The Indie Stone is clear that Build 41 saves won’t work in Build 42. It doesn’t work the other way either. Even within Build 42, saves from the 42.19 testing branch couldn’t load in 42.20.

What this means for your server:

  • Moving to Build 42 means a new world.
  • Your Build 41 world isn’t lost. Keep it as its own save in Games and switch back to it whenever your group wants. Switching takes a backup first and keeps your address.
  • Before you switch builds, download a backup from Backups for safekeeping.

Mods don’t all carry over

Many Build 41 mods don’t work on Build 42 until their authors update them. Some mods have a separate Workshop page for each build.

  1. List the mods your group can’t play without.
  2. Check each Workshop page for Build 42 support.
  3. If a must-have mod is Build 41 only, stay on Build 41 for now, or find a Build 42 replacement.

The Mods tab shows which mods match your server’s build.

RAM: Build 42 needs more

A Build 42 server uses about a third more memory than Build 41 with the same players, zombies and mods. As a rule of thumb:

On Build 41 you used On Build 42 plan for
8 GB 10 to 12 GB
10 GB 12 to 16 GB
12 GB 16 GB

See the performance guide for what else fills memory.

Switch builds on Wilderack

  1. Download a backup of your current world from Backups.
  2. Open Settings and change Server type to Build 41 or Build 42.
  3. We take a backup and warn you about mods that won’t carry over.
  4. Start a new world for the new build, or switch to a save that already uses it in Games.
  5. Tell your friends to switch their Steam branch if they need to.

The server installs the right build from Steam. Build 41 uses the legacy41 branch of the Project Zomboid Dedicated Server, the same branch name players use.

Questions

When did Project Zomboid Build 42 become stable?

Build 42.20 went to the stable branch on 29 July 2026, with multiplayer included. It's now what Steam installs by default. Later updates, such as 42.21 and 42.22, have followed.

Can I still host a Build 41 Project Zomboid server?

Yes. Build 41 is still on Steam as the legacy41 branch, for the game and the dedicated server. On Wilderack, pick Build 41 when you create the server or under Server type in Settings.

Can I move my Build 41 world to Build 42?

No. The Indie Stone says Build 41 saves won't work in Build 42. To play Build 42, start a new world. You can keep the old world as a separate save and switch back to it any time.

Does Build 42 need more RAM than Build 41?

Yes. A Build 42 server uses about a third more memory than Build 41 with the same players and settings. If your Build 41 server ran well on 8 GB, plan for 10 to 12 GB on Build 42.

Sources we checked

  1. Build 42 stable plansThe Indie Stone
  2. B42 checklistThe Indie Stone
  3. Project Zomboid Build 42.20 releasedThe Indie Stone
  4. Build 42.21 stable releasedThe Indie Stone

Run your Project Zomboid server on Wilderack

Daily backups, DDoS protection and free game swaps come with every plan. Wakes the moment you join.

Wait! Get 25% off your server

Don’t miss the best Project Zomboid hosting.

Your codeTOSK25

Use my 25% off

25% off your first payment, for new customers. Then the normal price; cancel any time. The button takes the code to checkout for you.