Minecraft Server RAM Requirements, Sized Honestly
Minecraft server RAM requirements without the guesswork: what vanilla, plugins, and modpacks really need, and why more memory is often not the fix.
Minecraft server RAM requirements are the first thing people get wrong, usually in the expensive direction. The honest version is short: memory is not what makes a world feel fast, it is what stops a world from crashing. Buy enough that the server never runs out, then spend the rest of your attention on the settings that actually decide whether the game stutters.
The short answer to Minecraft server RAM requirements#
Start from what you are running, not from how many friends you have. A handful of players on vanilla Minecraft is a small job; the same handful on a hundred-mod pack is not.
| What you are running | Start at | Why |
|---|---|---|
| Vanilla Java, a few friends | 2 GB | The floor we quote for Minecraft, and it holds for a small survival world. |
| Paper with a handful of plugins | 4 GB | Plugins such as CoreProtect keep history in memory before it reaches disk. |
| A published modpack, 10 to 20 players | 8 GB | Mods add blocks, entities, and terrain, and all of it lives in the loaded chunks. |
| Heavy modded, or a public server | 16 GB | Large packs plus many players loading chunks in different directions at once. |
Treat these as starting points with headroom, not ceilings to run at. A server that regularly touches the top of its heap spends its time collecting garbage instead of ticking the world, and players feel that as lag long before anything crashes.
What actually eats the memory#
Almost all of it is loaded chunks. A chunk is a 16 by 16 column of the world, and the server holds one in memory for every area a player can see. That count is not driven by player numbers alone; it is players multiplied by how far each can see, squared. Doubling view-distance roughly quadruples the chunk load per player.
The server.properties default is view-distance=10, a sensible middle. The other consumers, in rough order:
- Entities. Mobs, dropped items, and armour stands. A big automated farm can hold thousands of them in memory permanently.
- Mods. Every mod loads its classes, blocks, and recipes at startup, before a single player joins, so a modpack costs you memory on an empty server.
- Plugins with history. Block logging and economy plugins buffer in memory. Several of them want a MySQL database, which moves that load off the heap.
- World generation. Exploring new terrain is the most expensive thing a player can do. Pre-generating the map with a plugin such as Chunky turns that spike into a one-time job you run when nobody is on.
Vanilla, Paper, and modded are three different purchases#
The Startup tab switches between Vanilla, Paper or Purpur, Fabric, and Forge, and that choice moves your memory bill more than any player-count estimate will.
Paper and Purpur are optimised rebuilds of the vanilla server. They will not halve your memory, but they run plugins, which are far cheaper than mods because the client does not need them. Fabric and Forge run true mods, and that is where the numbers climb: the fifty-mod Forge pack we loaded with ten friends for our 2025 Minecraft hosting comparison needed considerably more headroom than vanilla did with the same people online.
One version detail catches people out: the Java runtime has to match the game version. 1.17 through 1.20.4 want Java 17, 1.20.5 and newer want Java 21, and 1.16 and older run on Java 8 or 11. All of those images are in the panel, and the Minecraft quickstart covers switching them.
Why more RAM is often not the fix#
This is the part that saves people money. Minecraft's tick loop, the twenty-times-a-second pass that moves every mob and grows every crop, is largely single-threaded. When it cannot finish in fifty milliseconds, the server drops below twenty ticks per second and everything feels sluggish. Adding memory does nothing for that. Clock speed does, which is why our game servers run on AMD EPYC 4000 or Intel Xeon 6300 series processors at 4.3 GHz and up, on NVMe storage doing better than 1 GB/s, rather than on a pile of slow cores.
Two more traps worth knowing:
- Do not hand the whole plan to the Java heap. The JVM needs memory outside the heap for its own bookkeeping, and so does everything else in the container. Leaving some back is what keeps the process from being killed outright.
- A bigger heap is not a free upgrade. More heap means more to sweep when the collector runs, so an oversized allocation can trade a rare small pause for an occasional long one.
If the symptom is stutter rather than crashes, start with view-distance and simulation-distance, look for entity farms, and check the panel graphs before you buy anything.
What our Minecraft plans give you#
Our Minecraft hosting plans are sold by resources, not by player slots, so a friend joining never costs you anything. These are live figures:
| Plan | Memory | vCPU | Storage | Monthly |
|---|---|---|---|---|
| Stone Basic | 2 GB | 1 | 40 GB SSD | $6.99 |
| Iron Plus | 4 GB | 1.5 | 20 GB SSD | $9.99 |
| Diamond Plus | 8 GB | 2 | 40 GB SSD | $14.99 |
| Netherite Ultra | 16 GB | 3 | 50 GB SSD | $19.99 |
Storage matters more than it looks there, because panel backups need free space to write into. A world and a few backups fit fine on a 20 GB plan; a heavily explored modded world on a nightly schedule wants more room.
How to tell you have actually outgrown your plan#
Watch the console and the panel graphs for a week before deciding. Running out of memory looks like the server hitching every few minutes and then dying with an out-of-memory error, usually while somebody is exploring new terrain. Running out of CPU looks like steady, boring lag that gets worse with player count and never crashes.
The first is a memory purchase. The second is a settings problem first and a clock-speed problem second. Either way, moving between our plans is a prorated upgrade, and if you would rather run several servers and the tooling around them on one machine you control, game server hosting versus a VPS works through that trade.
FAQ#
How much RAM do I need for a Minecraft server with 10 players?
On vanilla or Paper, 4 GB is comfortable for ten people in a settled world. On a modpack, plan for 8 GB, because the mods cost you memory whether anyone is online or not. Player count matters far less than what those players are loading.
Is 2 GB enough for a Minecraft server?
For vanilla Java with a few friends in a world you have already explored, yes, and that is the floor we quote. It is not enough for a modpack, and it leaves little room for a large plugin set or a big automated farm.
Does more RAM increase TPS?
Only if you were running out. The tick loop is limited by single-thread CPU speed, so a server that is low on ticks per second with plenty of free heap will not improve with more memory. Reduce view distance, thin out entities, and pre-generate chunks instead.
How much RAM does a modded Minecraft server need?
Start at 8 GB for a published pack with a normal player group, and 16 GB for a large pack or a public server. Check the pack author's own recommendation, then leave headroom rather than allocating every last megabyte to Java.