How much RAM does a Minecraft server need? Real numbers by player count and mods

Short answer for Minecraft Java 1.21.4: a vanilla or Paper server for up to 5 players runs well on 2 to 3 GB. A lightly modded Fabric server wants 4 GB. A large modpack with 150+ mods needs 6 to 8 GB before the first player even joins, and 10 GB or more with a full group online. View distance above 12 adds another 1 to 2 GB on top of any of those.

Those are the working numbers. The rest of this guide explains where they come from, how to adjust them for your exact setup, and the counterintuitive part: why allocating too much RAM actively makes your server stutter.

The quick reference table

Want a number tuned to your exact player count, mod profile, and view distance? Use our Server RAM Calculator. It applies the same model as this table and shows hosting plans that match the result.

What actually consumes server memory

Three things dominate the heap of a Minecraft server, and none of them is "the world file".

Loaded chunks. Every player keeps a radius of chunks loaded around them, set by view-distance in server.properties. Chunk count grows with the square of the radius: view distance 16 holds roughly 2.5 times the chunks of view distance 10. Players spread across the map each load their own set; players standing in one base share most of theirs. This is why "how many players" is really a proxy for "how many separate chunk areas".

Entities and block entities. Mobs, items on the ground, hoppers, chests with inventories, and every machine block from tech mods. A single overloaded mob farm can hold more live objects than five idle players. If your memory use seems too high for your player count, an entity-heavy farm is the usual suspect. Our iron golem farm guide covers rates-per-entity design, and a mob switch can shut down hostile spawns entirely when you need to isolate the cause.

Mod and plugin code. Every mod's classes, configs, and registries are loaded permanently. This is a fixed cost paid at startup, which is why a 150-mod pack idles at 5+ GB with zero players online. Plugins on Paper are lighter than full Fabric/Forge mods but follow the same principle.

Vanilla and Paper: 2 GB is genuinely enough

Mojang's own dedicated server guidance has held steady for years: small vanilla servers run inside 2 GB. Paper, despite adding hundreds of optimizations, has the same baseline footprint. For a friends server of 2 to 5 players at default view distance 10, allocating 3 GB gives you a comfortable margin for exploration bursts (lots of new chunks generating at once).

If you self-host, set the allocation in your startup script:

java -Xmx3G -Xms3G [Aikar's flags] -jar server.jar nogui

Set -Xms (starting heap) equal to -Xmx (maximum heap). Growing the heap at runtime causes avoidable pauses. The full startup script with Aikar's garbage collector flags is in our complete server setup guide.

Modded servers: count your mods, not your players

For modded servers the mod list sets the floor and players add on top:

• Performance-focused Fabric stack (Lithium, Krypton, a handful of QoL mods): treat it like vanilla plus 1 GB. These mods are designed to be lean. See the Fabric performance mods guide for the recommended stack.
• Content mods under 50 (Create, Farmer's Delight, a biome mod): 4 GB floor for a small group. Create in particular adds block entities that tick constantly once players start building contraptions.
• Large packs, 150+ mods: 6 to 8 GB floor. Kitchen-sink packs from our modpack roundup typically publish their own minimums; trust the pack author's number when it is higher than ours, they know their pack's hungriest mods.

Why too much RAM makes lag worse

This is the part most "more RAM = better" advice gets wrong. Java's garbage collector periodically scans the heap to reclaim dead objects, and the duration of those scans scales with heap size. A vanilla server given 16 GB accumulates garbage for a long time, then pays for it with a longer collection pause: that is the rhythmic, every-few-minutes freeze that players report as "the server heartbeat lag".

A right-sized heap with G1GC (the collector Aikar's flags configure) does many small, predictable collections instead of rare giant ones. Allocate the recommendation from the table, not your machine's maximum.

If your server stutters and you are not sure memory is the cause, profile before buying anything: spark shows GC pause times directly, and our lag troubleshooting guide walks through separating GC pauses from tick-time problems and network issues.

Renting a server: how much RAM to buy

Hosting plans are priced almost linearly per GB, so the table above translates directly into a monthly price. Two renting-specific notes:

1. Shared hosting overhead. Budget hosts run many servers per machine. The advertised RAM is your allocation, but CPU is shared, and a large modpack is usually CPU-starved before it is RAM-starved. Past 8 GB, prioritize hosts with better per-thread CPU performance rather than more memory.
2. Start one tier lower than you think. Upgrading a plan takes minutes on every host we have reviewed; downgrading after overbuying feels worse. If /spark gc shows healthy pause times and your TPS holds at 20, you bought enough.

FAQ

Is 2 GB enough for a Minecraft server? Yes, for a vanilla or Paper server with up to about 5 players at view distance 10. It is not enough for any meaningful mod list.

How much RAM does a modded Minecraft server need? Count mods, not players, first: under 50 mods needs a 4 GB floor, 150+ mods needs 6 to 8 GB, then add roughly 1 GB per 5 concurrent players beyond the first few.

Does more RAM make a Minecraft server faster? Only up to the point where the workload fits comfortably. Beyond that, extra heap increases garbage collector pause times and the server feels worse. TPS problems past the minimum allocation are almost always CPU or tick-time problems.

How much RAM do I need for 10 players? Vanilla or Paper: 4 GB. Lightly modded: 6 to 8 GB. Large modpack: 10 GB or more. Spread-out players load more chunks than players sharing a base, so survival servers with explorers sit at the high end.

Why does my server use all the RAM I give it? The JVM grows into whatever heap you allow before collecting garbage; high usage is normal and not a leak. What matters is GC pause time, not the usage graph. Check it with spark before adding memory.

---

Updated for Minecraft 1.21.4 on June 10, 2026. When a new version ships, numbers are re-checked and this log is updated.