How Much Server Memory for Project Zomboid Player Counts (Build 42.19)
Build 42.19 · Host defaults, server options, and launch path
memory=4096). Treat player-count tables as planning ranges, not hard guarantees. Raise the heap only after you see sustained high heap or process memory under real play, and leave OS headroom for the host machine.
Quick planning ranges
Project Zomboid does not publish a “2 GB base + 0.5 GB per player” formula in the current client or server options. Community rules of thumb can under- or over-size a server. Start from the Host UI default, then adjust for spread-out players, zombie density, mods, and long-running worlds.
| Scenario (planning only) | Suggested starting Java heap (-Xmx) |
Host / OS RAM note |
|---|---|---|
| 2–4 players, vanilla or light mods, same town | 4 GB (Host default) | On the same PC as the game client, prefer 16 GB+ system RAM so client + server + OS fit |
| 4–8 players, moderate exploration, a few heavy mods | 6–8 GB | Dedicated box: leave several GB free outside the heap for native memory, disk cache, and OS |
| 8–16 players or large mod packs / high population | 8–12 GB+ | Expect CPU and network to matter as much as RAM; measure before buying larger plans |
Near MaxPlayers (default 32; higher has official streaming/desync warnings) |
Size from measured peaks, not a fixed formula | Game tooltip warns counts above 32 can hurt map streaming and desync—do not treat “more RAM” as a fix for that design limit |
Build 42 multiplayer status
Build 42.19 still presents multiplayer as a MP test build on Unstable. Future Unstable updates can break ongoing multiplayer saves. Plan memory and hosting around that risk—do not treat B42 MP as a finished “stable, always cheaper” stack.
Host memory control (current)
In-game Host exposes a Server memory combo from 768 MB to 16 GB in 256 MB steps. The default is 4096 MB. That value is written to host.ini as memory=… and applied as JVM -Xmx, not as a Memory= key inside servertest.ini.
Heap vs system RAM
The Host memory control and dedicated-server -Xmx set the Java heap ceiling. Process working set (RSS) is usually higher: native libraries, metaspace, thread stacks, and OS file cache sit outside the heap. If the machine has 8 GB total and you set -Xmx8G, the process and OS will fight for memory and can thrash or get killed.
- Same-PC Host: budget client + server + browser/Discord + OS. A 4 GB server heap on an 8 GB laptop is often too tight.
- Dedicated server: leave headroom beyond
-Xmx(commonly multiple GB free, more with heavy mods or large worlds). - Client RAM is separate: changing the game client’s own launch JSON does not replace server heap settings. For client allocation, see how to allocate more RAM to Project Zomboid.
Where to set memory
A. In-game Host (friends co-op on your PC)
- Launch the Project Zomboid client.
- Open Host (not Manage Settings alone for the memory control).
- Choose the server settings profile, then set Server memory on the Host screen (default 4 GB).
- Use Edit Settings / Manage Settings for name, password, ports, mods, sandbox—those live in the server INI and sandbox files.
- Start the server from Host. The chosen memory is saved in user data
host.iniasmemory=<MB>and passed into the server process as-Xmx<MB>m.
DefaultPort, PublicName, Password, and related server fields. Heap size for Host is the separate memory control that writes host.ini.
# Example host.ini keys written by Host (values are illustrative)
servername=servertest
username=admin
memory=4096B. Dedicated server (standalone tool / VPS)
Dedicated launches do not read a Memory= line from the server INI. Set the JVM heap in the start script, panel “Java arguments”, or process manager environment—for example -Xmx4096m or -Xmx8G. Keep -Xms equal to or below -Xmx only if you know you want a fixed minimum reservation.
# Conceptual dedicated start (paths and wrapper names vary by OS / host panel)
cd /path/to/pz-server
# Wrong: ./start-server.sh -Xmx8G (if the script does not forward JVM flags)
# Right: put -Xmx in the script’s java line, or the panel’s JVM args field
java ... -Xmx8192m ... zombie.network.GameServer
On a panel (Pterodactyl, gameserver hosts, etc.), use the provider’s memory / JVM field. Raising the container RAM limit without raising -Xmx (or the reverse) leaves performance on the table or causes OOM kills.
For broader host setup beyond memory, see the server hosting guide and server settings guide. Admin options that affect load (PVP, loot, backups) are covered in server administrator tips.
Ports and config keys that are often wrong online
Memory guides often paste outdated INI fragments. On current Build 42.19 options, use these names:
| Topic | Current key / behavior | Do not use |
|---|---|---|
| Join password | Password= in the server INI (ignored when using the Host button for some co-op flows—see in-game tooltip) |
ServerPassword= |
| Network ports | DefaultPort default 16261, UDPPort default 16262 (two UDP ports) |
Per-player chain 16262, 16263, 16264… as required “player slots” |
| Workshop downloads | WorkshopItems= Steam Workshop file IDs, semicolon-separated |
Putting Workshop numeric IDs in Mods= |
| Enabled mod IDs | Mods= mod load IDs from each mod’s mod.info / info text |
Assuming one Workshop URL equals one mod ID automatically |
| Server heap | Host: host.ini memory= / dedicated: JVM -Xmx |
Memory= inside the server INI, or fictional keys like ZombieUpdateFreq for RAM |
Adding mods increases both download size and often heap pressure. Keep Workshop IDs and mod IDs in the correct fields; see adding mods to a Project Zomboid server.
How to decide whether you need more memory
- Record the scenario: player count, whether people are in different cells, sandbox population, mod list size, and uptime.
- Watch the process, not just the slider: OS tools (Task Manager, Activity Monitor,
top/htop) show RSS; JVM tools or GC logs show heap use if you enable them. - Raise in steps: from 4 GB to 6 GB to 8 GB rather than jumping to the Host maximum of 16 GB.
- Correlate symptoms: long freezes, GC thrash, and OS swap point at memory. High tick lag with free RAM often means CPU, disk, or player scatter—not a bigger
-Xmx. - After crashes: check server logs for out-of-memory errors before assuming “Build 42 always needs more RAM.”
Password if the server is public-facing, and only increase heap after a real session shows pressure. Prefer whitelisted or private servers while Build 42 MP remains a test/Unstable track.
FAQ
Is 2 GB enough for two players?
The Host UI still allows values down to 768 MB, but the default is 4 GB for a reason. Two local players on vanilla might run on less; recommending 2 GB as a general requirement is risky. Prefer 4 GB unless you have measured a lighter footprint on your own hardware.
Does Build 42 need less RAM than Build 41?
This page does not claim that. There is no side-by-side B41/B42 comparison table here. Build 42 multiplayer is still labeled a test/Unstable experience; do not plan capacity on “B42 is always lighter.”
Can I set memory in servertest.ini?
Not as a first-class server option named Memory in the current options set. Use Host’s memory control / host.ini, or dedicated JVM arguments.
Why is the server still laggy after 16 GB?
Extra heap does not fix weak single-thread performance, overloaded disks, bad routing, or too many simultaneous simulation cells. Split bases across the map and dense zombie settings can dominate. Profile before renting more RAM.
What about MaxPlayers above 32?
The current tooltip warns that counts above 32 can cause poor map streaming and desync. Treat that as a gameplay/network design warning, not something more heap automatically solves.
Related Articles
