Minecraft server RAM: how much do you need?
Player count is a poor guide to Minecraft memory. What the server actually pays for is loaded chunks and the entities in them — so a group of ten crowded into one base is cheaper to host than three friends wandering off in three different directions, each dragging their own patch of world into memory.
Recommendation
You need a server with at least
3GB
- Engine / Base OS:
- 2 GB
- Player Overhead:
- +1.0 GB
- Estimated Raw Usage:
- 3 GB
- Suggested cores:
- 2
- Disk to allow:
- 10 GB+
Almost entirely single-threaded. A high clock speed beats extra cores, and no number of cores fixes a low-clock CPU.
View 3GB PlansAdvertisement
What uses the memory in Minecraft
Everything comes down to the Java heap. A small group on vanilla or Paper sits happily in 2-4 GB. Modpacks are a different calculation altogether: a 200-mod pack registers thousands of blocks, items and recipes during startup and wants 8 GB before anyone has logged in. View distance scales all of it, and cutting it from 12 to 8 frequently frees more memory than an extra gigabyte would add.
Minecraft server RAM by player count
The calculator above, run for 4 common sizes. Each figure is rounded up to a plan size people actually sell.
| Players | Vanilla / Spigot | Light Mods (1-30) | Heavy Mods (30-100) | Massive Modpacks (200+) |
|---|---|---|---|---|
| 10 | 3 GB | 6 GB | 8 GB | 12 GB |
| 25 | 6 GB | 8 GB | 12 GB | 16 GB |
| 50 | 8 GB | 12 GB | 16 GB | 24 GB |
| 100 | 12 GB | 16 GB | 24 GB | 32 GB |
Advertisement
Where people get it wrong
Handing the entire machine's memory to the JVM. The operating system and Java's off-heap allocations need room outside the heap, and a heap that is too large makes each garbage-collection pause longer rather than shorter. Players do not experience that as more capacity; they experience it as lag spikes on a timer.
Setting the heap
Memory is given to Minecraft through two Java flags: -Xms, the heap it starts with, and -Xmx, the most it may use. Set them to the same value. The start script generator on this site does exactly that, and it leaves one to two gigabytes of the machine's memory outside the heap for the operating system and Java's own overhead. On a 6 GB machine that means a 4.5 GB heap, not a 6 GB one.
Exploration is the expensive part
Generating new terrain costs far more than loading terrain that already exists, so a server's worst moments are when several players fly or sail into unexplored land at once. Two settings keep that under control. A world border, or max-world-size in server.properties, caps how far the world can grow. Pre-generating the area inside it with a plugin such as Chunky does the expensive work once, before anyone joins, instead of during play.