How Much RAM Does a Minecraft Server Need per Player? Vanilla vs. Modded vs. Minigames (2025 Guide)

A vanilla Minecraft server for a handful of friends needs 3 to 4 GB. Ten or more players wants 6 to 8 GB. A light modpack starts at 6 to 8 GB, and heavy packs like ATM9 or RLCraft want 8 to 12 GB or more. The number that matters is not players, it is what the server loads at startup.

That last point is the one most guides miss. Mods load into the heap whether anyone is online or not, so a two-player modded server can need more memory than a fifteen-player vanilla one.

RAM by setup

| Setup | RAM | What drives it | |---|---|---| | Vanilla, 1 to 5 players | 3 to 4 GB | Modern versions are heavier than old guides assume | | Vanilla, 5 to 15 players | 4 to 6 GB | Chunk loading, entity count | | Vanilla, 15+ players | 6 to 8 GB | View distance becomes the lever | | Light modpack | 6 to 8 GB | Paid at startup, not at peak | | Heavy modpack (ATM9, RLCraft) | 10 to 16 GB | Hundreds of mods, each with its own registry |

More RAM does not fix tick lag

This is the most expensive misunderstanding in Minecraft hosting, and it costs people money at every host including ours.

Minecraft's tick loop is largely single-threaded. If the server cannot finish a tick in 50 ms, TPS drops below 20 and everything feels slow. That is usually CPU or workload, not memory. Adding RAM to a CPU-bound server changes nothing, and can make it slightly worse, because a larger heap means longer garbage collection pauses.

The symptoms separate cleanly:

• Low TPS, memory not full means CPU or entity load. Look at hoppers, mob farms, chunk loaders and redstone before buying anything.
• Sawtooth memory, periodic freezes means garbage collection. That is a tuning problem.
• java.lang.OutOfMemoryError means you genuinely need more RAM, and that one is unambiguous.

Set Xms and Xmx to the same value

Two flags decide how the JVM uses the memory you paid for:

• -Xms is the starting heap, -Xmx is the maximum.
• Set them equal. If the heap can grow at runtime, growth triggers extra garbage collection, and that shows up as tick lag.
• Never allocate the whole plan to the heap. Leave roughly 20% for the JVM itself and the operating system. Allocating 8 GB of an 8 GB plan is how servers get killed by the host rather than by Minecraft.

On Paper, Aikar's flags are the common standard because they tune the G1 collector for exactly this workload. A well-tuned 6 GB heap beats a badly tuned 12 GB one, which is why buying more memory is usually the second thing to try, not the first.

What to check before buying more

1. View distance. Dropping from 10 to 6 often does more than doubling RAM, because it cuts the number of chunks the server keeps live per player.
2. Entity count. Mob farms and dropped items are the usual culprits.
3. The server software. Paper handles the same workload for less than vanilla or Forge.
4. Then the plan size.

If you are troubleshooting rather than sizing, reducing server lag covers the tuning side in more detail, and the same tick-versus-memory logic applies to Terraria and Project Zomboid, which fail in recognisably similar ways.

Our Minecraft server hosting lets you change the heap and the flags from the panel, so trying a smaller, better-tuned heap costs nothing.

When you are overbuying

If five people play vanilla on a small world and TPS sits at 20, you do not need 8 GB, and no amount of extra memory will make the game feel better than it already does. Buy the tier that matches the workload and spend the difference on a location closer to your players, which you will actually notice.