How much RAM does a Minecraft server actually need per player?

Short answer: not very much, and the number you keep seeing online ("1 GB per player") is wrong in both directions. A vanilla server with 4 players idling in spawn does not need 4 GB. A 6-player modpack with create mod and a dozen automated factories absolutely does.

RAM use is driven by loaded chunks and entity count, not the player count itself. Players are just the most common reason chunks get loaded. So sizing by player count is a proxy, and a leaky one.

The lever you actually pull is chunks × entities, not headcount. A 4-player server with one chunk-loaded mob farm can use more RAM than a 20-player server where everyone is exploring fresh wilderness.

Here is what we actually see on servers we host, by version family and player count. Numbers are working set under load, not allocation. Always allocate more than working set so the JVM has headroom.

Vanilla Java 1.20+

Players	Working set	Recommended allocation
1 to 4	600 MB to 1.2 GB	2 GB
5 to 10	1.0 to 1.8 GB	3 GB
10 to 20	1.5 to 2.5 GB	4 GB
20 to 40	2.5 to 4 GB	6 GB

Vanilla is efficient. Most "I need 8 GB for 10 players" advice is leftover from the 1.7 era.

Paper / Purpur 1.20+

Same as vanilla, sometimes 100 to 200 MB lower because Paper does smarter chunk handling. The reason to run Paper is performance and plugins, not RAM savings.

Forge / Fabric modded

Here the player count stops mattering and the modpack starts mattering. Working set depends on:

• Number of registered items, blocks, recipes, entities (loaded once at startup).
• Whether the pack has chunk loaders (Create contraptions, AE2 networks, mob farms).
• World generation complexity (Terralith, BoP, Tectonic add overhead).
• View distance and simulation distance.

Rough guide by modpack size:

Pack size	Mod count	Working set, 1 to 5 players	Recommended allocation
Small / sided	30 to 60	1.5 to 2.5 GB	4 GB
Medium "kitchen sink"	100 to 200	3 to 5 GB	6 to 8 GB
Large expert-style	250+	5 to 8 GB	10 to 12 GB
Create-heavy with automation	varies	add 1 to 2 GB on top	add a tier

Add roughly 200 to 400 MB per active player on top of the base, for their loaded chunks and inventory state.

What actually consumes RAM

A typical modded server's heap, broken down by what's eating it:

In order, what each line means:In order, what each line means:

1. Loaded chunks. Each chunk is a few hundred KB to a few MB depending on data. View distance of 10 means each player loads about 441 chunks (21 by 21). Simulation distance is what the server ticks.
2. Item registry and recipe cache. Loaded at startup. Pure function of pack size. You pay this whether one or 50 players are online.
3. Entities. Mob farms, animals, item frames, armor stands, especially in chunk loaders. This is the number one cause of "server was fine yesterday, dying today."
4. Plugin / mod state. Economy plugins, claim plugins, large land claims, dynmap caches.

Player count drives (1) and (3) indirectly. Bigger view distance and active automation matter more than headcount.

How to right-size in practice

The key trap: look at post-GC heap, not allocated heap. The JVM will use whatever you give it. The number that matters is what is still alive after garbage collection.

A common trap: oversizing hurts you

Giving a 4 GB workload 12 GB of heap is not free. Garbage collection pauses scale with heap size on most collectors. A bloated heap with G1GC can produce longer pause spikes than a right-sized one, which players feel as lag spikes. For modern Minecraft on Java 17+, ZGC handles large heaps better, but the principle holds: do not throw RAM at a server in hopes of fixing lag. Diagnose first.

What we actually recommend

• 1 to 10 vanilla players: 3 GB.
• 10 to 30 vanilla players: 4 to 6 GB.
• Any medium modpack: start at 6 GB, scale based on telemetry.
• Any expert-style pack: 10 to 12 GB.
• If you do not know your pack size, 6 GB is the safest universal starting point.

The 4 GB minimum we apply to paid plans exists because below that, modded servers thrash and vanilla servers feel constrained at modest player counts. Above 12 GB, you are almost always solving the wrong problem.