"How many GB of RAM for my Minecraft server?" is the question our support gets most. The answer depends on three things: player count, server type, and view distance. Here are concrete reference points.
Memory reference points
| Setup | Players | Recommended RAM |
|---|---|---|
| Vanilla or Paper, with friends | 5–10 | 4 GB |
| Paper with a few plugins | 10–20 | 8 GB |
| Light modpack (30–60 mods) | 5–15 | 8–12 GB |
| Large modpack (150+ mods) | 10–20 | 16 GB |
| Public server, several worlds | 30–60 | 16–24 GB |
These figures assume a sensible view distance (8–10 chunks server-side). Going from 10 to 16 chunks can double the memory needed, because every loaded chunk takes space.
Why the CPU matters more than you'd think
Java Edition Minecraft is almost single-threaded for world logic: one task computes blocks, entities and redstone. Adding cores doesn't speed that loop up — only clock speed does.
That's why our game nodes run Intel Xeon Gold 6248R at 4 GHz rather than many-core but slower processors. A server dropping below 20 TPS is almost always CPU-bound, not memory-bound.
Too much RAM can hurt
Counter-intuitive but real: allocating 32 GB to a server that uses 6 lengthens the Java virtual machine's garbage collection pauses. Every pause shows up as a micro-freeze in game.
Good practice is to allocate roughly 1.5× what the server actually uses at peak, with suitable startup flags (Aikar's flags remain the reference for a Paper server).
What actually consumes resources
In order of impact:
- Entities. Mob farms, dropped items, item frames. A badly designed farm alone can sink your TPS.
- Loaded chunks. View distance, chunks force-loaded by mods, players scattered across the map.
- Complex redstone. Fast clocks are computed every tick.
- Badly written plugins. One plugin querying the database on every movement is enough.
The Spark plugin profiles all of this from the console and identifies the culprit in minutes.
Our practical advice
Start at 8 GB if you're playing with friends and plugins, 4 GB if you're a handful on vanilla. Watch the TPS for a week: if it stays at 20 and memory sits below 70%, you're sized right.
Upgrading happens from the client area without losing your world, with downtime limited to a restart — so there's no need to oversize "just in case".
All our Minecraft plans include the Pterodactyl panel, Premium DDoS protection and automatic backups.