How the Minecraft RAM calculator works
The calculator looks at the things that actually fill a Minecraft server's memory, then leaves room for Java on top. Its results are based on real servers we run and match the ranges in our guide on how much RAM a Minecraft server needs.
- Server software. Even an empty server needs memory once spawn is loaded. Forge and NeoForge start higher because the mod loader and its registries load first.
- Mods and plugins. Most Paper plugins are small. Mods weigh more, because their code, textures and recipes all load into memory, and large modpacks are where RAM matters most.
- Players and chunks. Each player keeps a square of chunks loaded around them. The higher the
view-distance, the bigger that square. Players who stay together share chunks, so ten players in one town cost less than ten players spread out. Exploring new terrain costs the most, because the server has to generate and hold fresh chunks. - Extras. Web maps, crossplay with Geyser, additional worlds and heavy automation all add to the total.
The total is the memory your server is expected to use at its busiest. The recommended RAM rounds that up to a common plan size, leaving room for Java's own overhead.
Minecraft server RAM by player count
These figures are for a Paper server with 10 plugins, the default view distance of 10 and a pre-generated world.
| Players online | Expected use | Recommended RAM | Java heap (-Xmx) |
|---|---|---|---|
| 1 - 5 | 1.5 - 2.1 GB | 3 - 4 GB | 2 - 3 GB |
| 10 | 2.8 GB | 4 GB | 3 GB |
| 20 | 4.0 GB | 6 GB | 5 GB |
| 30 | 5.1 GB | 7 GB | 6 GB |
| 50 | 7.2 GB | 10 GB | 8.5 GB |
| 100 | 12.0 GB | 14 GB | 12 GB |
A server that has not been pre-generated needs roughly 10 - 20 percent more, and a server with a web map and 30 or more plugins needs another 1 - 2 GB. Above 50 players, most networks split into several servers behind a proxy such as Velocity rather than growing one server forever.
RAM for modded Minecraft servers
Modpacks are where RAM matters most. These figures are for a Forge or NeoForge pack on 1.18 or newer with 5 players online.
| Mods in the pack | Typical pack | Recommended RAM |
|---|---|---|
| Around 50 | Light adventure or quality-of-life packs | 5 GB |
| Around 100 | Medium tech or magic packs | 7 GB |
| Around 150 | Larger themed packs | 8 GB |
| Around 200 | Kitchen-sink packs | 10 GB |
| 300 or more | All the Mods and similar | 12 GB or more |
With 20 players instead of 5, add roughly 3 GB. Fabric packs of a similar size usually need 1 - 2 GB less, especially with performance mods such as Lithium, FerriteCore and ModernFix installed.
Why the recommended RAM is higher than the heap
The -Xmx flag sets the Java heap, which holds the world, entities and mod data. Java also needs memory outside the heap for metaspace, thread stacks, the garbage collector and native libraries. The calculator leaves room for this, which is why the heap it suggests is always a little smaller than the recommended RAM.
The startup command uses Aikar's flags, the garbage collection settings recommended by the Paper team. They switch to the larger-heap values automatically once the heap reaches 12 GB.
When the estimate will be off
A calculator cannot see your world, so treat the result as a starting point. It will be too low if one mod or plugin leaks memory, if players build huge mob farms that keep chunks loaded, or if you run a 1.12 pack with a very large mod list. It will be too high if your players mostly stay in one town. The reliable way to check is the spark profiler: run spark health at your busiest time and compare the memory used with your limit.
If lag is the problem rather than crashes, more RAM may not help at all. Our guide to fixing Minecraft server lag shows how to tell a memory problem from a CPU problem.