How to Allocate More RAM in Project Zomboid (Build 42, 2026)
Short answer: open ProjectZomboid64.json in your Steam install folder, find the -Xmx line, set it to -Xmx8192m for vanilla / light mods, -Xmx12288m for heavy modded multiplayer, save, restart. Leave at least 4 GB free for the OS.
Project Zomboid is memory-hungry, Build 42 even more so. Map streaming, mod-loaded textures, vehicle pools, and the new lighting / weather work in B42 all live inside the JVM heap, and the default -Xmx is set for a vanilla 2-player session, not a 50-mod community pack. Symptoms of an under-allocated heap: long loading screens (5+ minutes to main menu), map holes (missing tiles when sprinting), "OutOfMemoryError: Java heap space" in the log, and chunk-load stutter spikes that look like FPS drops.
1. Default is way too small
Out of the box, Project Zomboid often launches with -Xmx3072m (3 GB). On Build 42 with any meaningful mod list, the JVM hits that ceiling during chunk load and crashes.
2. Mod bloat is real
Every item, vehicle, tile, and texture introduced by a mod lives in RAM. Brita's Weapon Pack alone reserves ~1 GB; large map overhauls (Raven Creek, Bedford Falls) add another ~1.5 GB just to load.
3. Build 42 raised the floor
Build 42 needs about 6 GB just to initialise, before any players or mods. Multiplayer adds ~0.5 GB per active player. Plan on 8 GB minimum if you intend to play anything modded.
Step-by-Step: Increase Client RAM (Steam)
- Open your Steam Library.
- Right-click Project Zomboid → Manage → Browse Local Files.
- Locate the file named
ProjectZomboid64.json. - Right-click the file → Edit (Notepad++ keeps the JSON valid; plain Notepad works too).
- Find the line containing
-Xmx. It will look like:"-Xmx3072m", - Change the number (in megabytes) to your desired ceiling:
- 4 GB:
"-Xmx4096m", vanilla singleplayer only - 6 GB:
"-Xmx6144m", Build 42 vanilla minimum - 8 GB:
"-Xmx8192m", light-modded singleplayer / 2-player co-op - 12 GB:
"-Xmx12288m", heavy modded multiplayer - 16 GB:
"-Xmx16384m", overhauls + 4+ player community pack
- 4 GB:
- Keep the trailing comma. Save the file.
- Launch the game and verify in the console (or the launch log) that the JVM came up with the new ceiling.
Recommended Settings (Build 42 / 2026)
| Playstyle | -Xmx value | Notes |
|---|---|---|
| Vanilla singleplayer | 6 GB (6144m) | Build 42 vanilla floor. 4 GB will technically launch but stutters on chunk load. |
| Vanilla multiplayer (2 to 4 players) | 8 GB (8192m) | Comfortable for vanilla servers with friends. |
| Modded (10 to 50 mods) | 10 GB (10240m) | Necessary for weapon and vehicle packs. |
| Heavy modded (100+ mods) | 12 to 16 GB (12288 to 16384m) | Required for global map overhauls + high-particle weapons. |
| Local host (hosting friends from your PC) | Client + Server both 8 GB+ | You run client AND server. Memory budget doubles, see below. |
Client vs Server: Two Different -Xmx Files
Sizing a dedicated box rather than fixing a client? Our Build 42 server requirements guide has the server-memory table by player count.
This trips people up. ProjectZomboid64.json controls only the client (the game launched from Steam). If you run a dedicated server alongside it, either locally (hosting for friends) or on a separate machine, the server has its own start script with its own -Xmx:
- Client:
ProjectZomboid64.json→ controls the game you play. - Server (Windows):
StartServer64.bat→ look for-Xmxinside thejava.exeline. - Server (Linux):
StartServer64.sh→ same; the script invokes java with-Xmxas an argument.
Local-host setups need both raised. A common failure pattern: player raises the client's -Xmx, launches the server with default 3 GB, then the server runs out of memory mid-session. See Increase Project Zomboid server RAM for the server-side walkthrough.
What a Real Server Actually Holds in Memory
Every number above is a ceiling. -Xmx tells the JVM how far it may
grow; it is not how much the server uses. That distinction is the single most common
reason people over-buy a box, so here is the measurement rather than the advice.
We host Project Zomboid, so we can read it off our own fleet. Over the seven days to 18 September 2026 we sampled 62,677 memory readings from 122 running Project Zomboid servers across 15 machines. Taking each server's own median first, so a chatty server cannot skew the result, and then looking at how those 116 servers with enough samples are distributed:
| Percentile | Resident memory | Reading |
|---|---|---|
| P10 | 1,852 MB | the lightest tenth |
| P25 | 2,502 MB | a quarter sit below this |
| P50 (median) | 3,170 MB | the typical server |
| P75 | 3,747 MB | three quarters sit below this |
| P90 | 4,300 MB | nine in ten sit below this |
The typical Project Zomboid server holds about 3.1 GB, and nine in ten stay
under 4.3 GB. That is a long way below the 8 GB an -Xmx table will
tell you to set, and both can be true at once: you give the JVM room to grow into, and it
mostly does not need it. Size a box on the P90 plus headroom for the operating system,
not on the ceiling you type into a launch script.
Read this as the resting footprint, not peak load. Our player-occupancy detection for Project Zomboid only started reporting reliably on 18 September 2026, so almost every sample in this window is a server that was empty or lightly populated. A busy server with a large explored map will sit higher. The honest use of these numbers is as a floor to budget from, not as a promise about a full server.
Measured: What Our Project Zomboid Servers Actually Use
| Players online | Servers | Typical memory | Busy memory (90th percentile) | Typical CPU | Busy CPU (90th percentile) |
|---|---|---|---|---|---|
| 1 to 2 | 112 | 4.7 GB | 8.3 GB | 0.1 cores | 0.6 cores |
| 3 to 5 | 76 | 5.8 GB | 9.2 GB | 0.2 cores | 0.8 cores |
| 6 to 10 | 16 | 8.9 GB | 9.5 GB | 0.4 cores | 0.9 cores |
| Every reading, players or not | 199 | 3.4 GB | 5.5 GB |
Project Zomboid's memory climbs with players: 4.7 GB typical with one or two online, 5.8 GB with three to five and 8.9 GB with six to ten, with the busiest readings between 8.3 and 9.5 GB. The servers we run include modded ones, which is part of why the advice above to plan on 8 GB for anything modded holds. CPU stays low, under one core even at the busiest.
Memory here is everything the server process holds, including anything moved to swap. CPU is in cores, where 1.0 is one full core. Typical is the median reading; busy is the reading only one in ten went above.
-Xms vs -Xmx: What's the Difference?
| Flag | Meaning | Recommended setting |
|---|---|---|
-Xmx | Maximum heap the JVM may use | Raise this, your real "RAM ceiling" |
-Xms | Initial heap reserved at launch | Leave default (small). Lets the JVM grow into the heap instead of pre-claiming all of it at startup. |
You will see guides recommending you set -Xms equal to -Xmx. That is true for Minecraft servers. For Project Zomboid it is not necessary and can slow startup, the JVM grabs all that RAM up front and starves the OS during the heaviest load (chunk streaming).
Common Pitfalls
| Mistake | Consequence |
|---|---|
| Set -Xmx equal to system RAM | OS, Steam, GPU driver and Discord starve. Stutter, swap, hard freeze, sometimes BSOD. |
| Forgot the trailing comma in JSON | ProjectZomboid64.json fails to parse and the game falls back to defaults silently. |
| Used "g" / "G" instead of megabytes | The flag accepts -Xmx8g or -Xmx8192m. Mixing them ("8gb", "8gm") makes the JVM ignore it and use defaults. |
| Raised client RAM but server still 3 GB | Mid-session OutOfMemory on the server side; clients see "connection lost." Raise both. |
| Mistaking CPU bottleneck for memory bottleneck | If one CPU core is pinned at 100% and RAM use is well below -Xmx, more RAM will not help. Look at mod load order and disable script-heavy mods instead. |
Verify Your Allocation Worked
Launch the game, open the in-game debug console (after enabling debug mode), and check the JVM startup arguments. The cleaner cross-platform way:
- Windows Task Manager: Sort processes by Memory.
ProjectZomboid64.exeshould be allowed to climb past 3 GB once you load a save. - Linux:
top -p $(pidof java)while the game runs. - The launch log:
console.txtin%USERPROFILE%/Zomboid/(Windows) or~/Zomboid/(Linux) prints the JVM args at startup. Grep for-Xmx.
Safety Warning
Never allocate more than ~75% of total system RAM, and always leave at least 4 GB free. If your computer has 16 GB, cap -Xmx around 10 to 12 GB. If you have 32 GB, 20 to 24 GB is the ceiling. The OS, Steam, GPU driver, and any background app all need memory; if the JVM swallows all of it, you will see swap-driven stutter or hard system freezes.
Related Project Zomboid Guides
- Increase Project Zomboid server RAM (dedicated server)
- Build 42 dedicated server setup
- Build 42 performance tuning
- Build 42 multiplayer lag optimisation
- "Stuck on server info", what to do
- Project Zomboid troubleshooting guide
- Project Zomboid Wiki home
Stutter-free survival. Host a Project Zomboid server with Supercraft, dedicated hardware so your local PC stays free for the client.
Frequently asked questions
How much RAM does Project Zomboid Build 42 actually need?
Build 42 needs roughly 6 GB just to initialise the JVM and load the world, even before mods. Plan on 6 GB base + ~0.5 GB per active player or per heavy mod, so a 4-player vanilla session is comfortable at 8 GB, a 50-mod community pack pushes 10 to 12 GB, and a heavily modded multiplayer setup with map overhauls and weapon packs lands at 12 to 16 GB.
Where do I edit -Xmx for Project Zomboid?
Right-click Project Zomboid in Steam → Manage → Browse Local Files. Open ProjectZomboid64.json in a text editor (Notepad++ recommended) and find the line starting with -Xmx. Change the number to the megabytes you want (8192 = 8 GB, 12288 = 12 GB) and save. Restart the game. On Linux the same file lives in the install directory; the syntax is identical.
What is the difference between -Xmx and -Xms in ProjectZomboid64.json?
-Xmx is the maximum heap the JVM is allowed to use. -Xms is the initial heap reserved at launch. For Project Zomboid the safe pattern is to keep -Xms low (the default) and raise -Xmx, this lets the JVM grow into the heap instead of pre-allocating it and competing with the OS during loading.
Can I just set -Xmx to all of my system RAM?
No. The operating system, Steam, the graphics driver, Discord and any background app also need RAM. Leave at least 4 GB free on the system. On a 16 GB machine, cap -Xmx around 10 to 12 GB; on a 32 GB machine, 20 to 24 GB is the practical ceiling. Setting -Xmx equal to system RAM will cause swapping, stutter, or hard system freezes.
Does -Xmx in ProjectZomboid64.json affect the dedicated server too?
No. ProjectZomboid64.json only changes the client (the game you launch from Steam). A dedicated server uses StartServer64.bat / StartServer64.sh which has its own -Xmx flag. If you host a server for friends you need to raise both files independently, see our server-side memory guide.
Why does the game still stutter after I raised -Xmx?
Two common causes: (1) the JVM is garbage collecting because you left -Xms tiny and it has to keep resizing the heap; (2) the bottleneck is the disk or the CPU, not RAM, Build 42 map streaming hits the disk hard, and mods with lots of script reloads can pin one CPU core. Check your task manager: if RAM use is well below your -Xmx and the CPU is at 100% on one core, more memory will not help.
Why do I get 'OutOfMemoryError: Java heap space' in Project Zomboid?
The JVM hit the -Xmx ceiling and could not allocate more. Raise -Xmx in ProjectZomboid64.json (or in the StartServer script if the error happens on the server side) and restart. On modded sessions, also check the launch log for a single offending mod that leaks textures or tiles on chunk load, the OutOfMemory is sometimes a symptom of a leaky mod rather than a ceiling that is too low.