Project Zomboid Build 42 server RAM requirements

What do The Indie Stone and PZwiki say about server hardware?

No official Project Zomboid server hardware figure was found. On 8 November 2026, projectzomboid.com refused automated access (HTTP 403), so its pages could not be read. The Steam news feed, which carries The Indie Stone's announcements, was readable in full for the latest 40 items and gives no server RAM figure.

The community-written PZwiki dedicated server page reports: "By default the StartServer64 batch file specifies 16GB of starting memory". It says to edit -Xms and -Xmx to suit your server or it will fail with memory errors, and its example uses 6 GB. The wiki doesn't say which build that applies to, and a shipped default is a setting and not a requirement.

Is Build 42 stable or unstable today?

Build 42 is the default Stable branch of Project Zomboid. The Indie Stone released 42.20.0 to Stable on 29 July 2026 and 42.21 on 28 September. On 27 October it put 42.22 on a new Pre-Release branch replacing Unstable, telling regular players to stay on Stable and inviting server admins to test. Builds are planned to stay on Pre-Release for at least a week before moving to Stable. Hotfixes 42.22.1 and 42.22.2 followed on 4 and 6 November.

Two details affect sizing. Hotfixes 42.20.1 (5 August) and 42.20.3 (17 August) both address memory leaks "that could lead to performance degradation and crashes over time", so run the latest Stable patch before judging your server. RAM articles written earlier, including those citing 42.19 or Unstable, may not describe current behaviour.

What do publishers report for Build 42?

None of these publishers shows how it got its numbers. Each sells hosting except pzfans, which says nothing about selling it.

Connect Hosting reports that an 8 GB container was killed twice while generating a world, with usage peaking above 9 GB. That is one anecdote from a seller of 10 GB plans, with no log shown, and its own page variously says plans start at 8 GB and at 10 GB. It also gives a 6 GB heap for a 10 GB machine in one place and 7 GB in another.

How much RAM does a Build 42 server need for your group?

Pick the Project Zomboid row nearest your group, and read heap and plan RAM as separate numbers. The last column is a reading of the table above, not a measurement.

Connect suggests sizing for "month three, not day one", which is advice and not a measured result. Its 9 GB world-generation report is a reason to watch the first boot closely on small plans.

Why can 4 GB and 10 GB both appear?

Those two Project Zomboid numbers usually describe different things. pzfans gives the Java heap, the memory the game's Java process may use for objects, while Connect Hosting gives machine RAM beside its heap figures, which must also cover the Java runtime, the operating system and memory outside the heap. Connect says to leave about 3 GB for those. WinterNode and Pine don't say which kind of number they mean, and Supercraft says the "server memory" in a host's plan menu is the -Xmx value, so its "server memory" bands read as heap sizes on that definition.

Hosts handle this differently, which is why you should ask. Supercraft says the "server memory" in a host's plan menu is the -Xmx value. Connect says its servers set the heap to 75% of the plan. pzfans says dedicated launches take -Xmx from the start script or panel and don't read a memory line from the server INI, and that the in-game Host screen writes memory= to host.ini with a 4,096 MB default.

What makes a Build 42 server need more?

Mods, zombie population, explored map and uptime move Project Zomboid's memory most, according to publishers.

• Mods. WinterNode says quality-of-life mods add little, while item, vehicle, weapon and map mods add much more. Connect says a single map mod can move the baseline by a gigabyte.
• Zombie population. WinterNode says "Insane" might need 2-3 GB more than "Low".
• Exploration and age. WinterNode says wide exploration is a main driver of growth. Connect says a three-month world holds much more than a fresh one.
• Uptime. WinterNode says memory can bloat 30-40% after 6-8 hours with 10 or more players and suggests restarts every 6 to 12 hours. It shows no data.
• Animals. Connect says herds simulate continuously server-side, WinterNode calls the vanilla impact modest, and Host Havoc's January 2025 post says Build 42 has "better memory management". None shows figures, so log your own.
• Player cap. pzfans says the default MaxPlayers is 32. The Indie Stone's 42.20.3 notes add support for up to 254 players, with no memory figure.

What CPU, storage and ports does a Build 42 server need?

No official Project Zomboid server CPU or disk figure was found either, so these are sellers' opinions. Supercraft asks for high single-core speed (3.5 GHz or more for up to 8 players, 4.5 GHz or more for 16 to 64) and fast NVMe storage, with 50 GB or more for large servers. Pine Hosting says strong per-core performance beats many slower cores. The Indie Stone's 42.22 notes mention improved server backup performance. PZwiki lists UDP ports 16261 and 16262.

How can you tell whether a Build 42 plan is enough?

Watch both heap and process memory across several busy sessions and the first boot of a new world.

pzfans' memory guide says admins with the Statistics permission can use /stats or the Admin panel to see Used and Max, and that peak Used is the number to size against. For process memory, sample resident size each minute:

while true; do
  echo "$(date -Is),$(ps -o rss= -p "$(pgrep -f zombie.network.GameServer | head -n1)")" >> pz-rss-kb.csv
  sleep 60
done

PZwiki's launch line shows that class name; confirm it with ps first. Add 20% headroom to the observed peak, as Connect Hosting suggests, and note the player count, mod list and sandbox settings beside each file. How to benchmark your game server covers keeping runs comparable.

What should you check on a host's Project Zomboid plan?

Ask these before buying a Project Zomboid plan:

• Is the advertised RAM the plan total or the heap, and can you edit -Xmx?
• Which branch can you run? Stable and Pre-Release differ, and server admins are invited to test the second.
• Can you schedule restarts and take backups without using up your disk?
• Are both UDP ports exposed, and how are Workshop mods installed?
• What is the CPU model, and are cores shared?
• Can you resize without moving the save, and is there a refund window that covers your first world generation?

For arithmetic, the server RAM calculator can model heap plus overhead from published inputs.

What does GameServerBench plan to record?

GameServerBench holds no Project Zomboid measurements. The planned protocol would run a fixed map with different animal density settings and log heap and process memory, including the first-boot world-generation peak, then publish the raw logs with dates. Hosts' terms may restrict automated load; see independence and host terms.

Next, compare plan structures on the Project Zomboid hosting hub.