As a rule of thumb, small Paper or Vanilla servers with up to 10 players need 3 to 4 GB RAM. Medium servers with plugins sit at 4 to 6 GB, modpacks at 8 to 12 GB. Besides the player count, what matters most is view distance (loaded chunks), entities such as animals and farms, and the number and type of mods or plugins.
More RAM does not automatically make a server faster: once memory is sufficient, extra RAM brings no benefit – too little RAM, however, causes crashes and long garbage collection pauses. Start with the guideline and increase it specifically when usage shows the need.
View distance is the biggest lever
Every player keeps a circle of chunks loaded around them. At view-distance 10 that's 441 chunks, at 16 already 1,089. With Paper you can lower the view distance and set the simulation-distance separately – saving RAM and CPU without the world feeling smaller.
Paper instead of Vanilla
Paper and Purpur significantly optimise tick processing, chunk loading and redstone. For servers with several players they are almost always the better choice. Our guide shows how to set up Purpur.
Java heap and server RAM
The value after -Xmx (Java heap) should be slightly below the server's RAM, because Java also needs memory outside the heap. The calculator therefore shows both: the recommended heap and the server RAM including headroom.
Startup flags for Paper
For Paper servers, the so-called Aikar flags for the G1 garbage collector have proven themselves. Set -Xms and -Xmx to the same value so memory doesn't constantly grow and shrink.
When more vCores help
Minecraft's game loop runs on one core – clock speed counts there. Additional cores are used for chunk generation, garbage collection and asynchronous plugins. 2 to 4 fast vCores are enough for most servers; networks with several servers need more.
Sizing modpacks correctly
Large modpacks load several gigabytes at startup. Plan for 8 GB or more from the start and check the modpack author's recommendation – it is usually the best starting point.