How Much RAM Does a Minecraft Server Need?

The most common question when setting up a Minecraft server is "how much RAM should I buy?" The honest answer depends less on player count and more on what the server runs. Below is a table based on real scenarios, plus an explanation of where the RAM actually goes.

Recommended RAM by player count

These are starting points. Map size, the number of loaded chunks and heavy redstone all push the requirement up.

The server software changes the requirement

• Vanilla: Mojang's own server. The simplest option, and the one that struggles first under load.
• Paper / Purpur: Includes optimisation patches, delivers higher TPS on the same hardware and supports plugins. The common choice for community servers.
• Forge / Fabric / NeoForge: Adds mod support. Every mod loads its own data into memory, so modpack servers need more RAM regardless of player count.
• BungeeCord / Velocity: A proxy layer that spreads players across sub-servers. It needs little RAM itself, but every sub-server behind it needs its own.

View distance settings

Two settings in server.properties directly affect RAM and CPU:

• view-distance: the chunk radius sent to players. The default is 10; on a 32-player server, 6–8 gives noticeable relief.
• simulation-distance: the radius where mobs, crops and redstone are processed. Lowering it cuts CPU load without changing what players see.

Lowering these two is faster to try — and often more effective — than buying more RAM.

Where does the RAM go?

Three things consume RAM on a Minecraft server: loaded chunks, entities in the world and the data of your plugins or mods. More players mostly means more loaded chunks, which is why 20 players spread across the map can need more RAM than 40 players standing in one town.

Setting -Xmx correctly

Do not give Java all of the server's memory. Leave room for the operating system and background services. On a machine with 8 GB, -Xmx6G is a sensible start.

java -Xms6G -Xmx6G -jar paper.jar nogui

Setting -Xms and -Xmx to the same value stops Java from resizing its heap while running, which reduces stutter.

More RAM does not fix TPS

If the server lags (TPS below 20) the bottleneck is usually the CPU, not memory. A Minecraft server runs world logic mostly on a single core, so a fast single core beats many slow ones. The AMD Ryzen 9 9950X in our plans was chosen for exactly this.

When TPS drops, check mob farms, always-on redstone, an oversized view-distance and badly written plugins. /timings or the Spark plugin will show you what is eating the tick.

How to monitor memory use

In the server console, /tps shows the tick rate and, on Paper, /spark health reports memory and garbage collection. Memory constantly above 90% with frequent GC pauses means RAM really is the limit. Plenty of free memory with low TPS points at the CPU instead.

On Linux you can watch the java process with htop; on Windows Server, Task Manager shows the same.

How many players can join?

Our plans are defined by CPU, RAM and disk rather than slots. You set the player limit yourself with max-players in server.properties; the practical limit is the resources of the plan you choose.