The short answer: start a small vanilla or Paper server for 2–5 friends with 2–3 GB. Use 4 GB for roughly 6–10 simultaneous players or a modest plugin set. A small modpack commonly needs 6–8 GB, while large packs may need 8–12 GB or more. Treat those as starting points, not guarantees: the pack author’s requirements and your own measurements win.
RAM is only one part of performance. Adding memory will not fix an overloaded main thread, slow storage, a bad plugin, excessive entities, or poor network latency. If the server already has memory headroom, diagnose it with the Minecraft server lag checklist before buying more.
RAM starting points by workload
| Server workload | Players online at once | Sensible starting point |
|---|---|---|
| Vanilla or Paper | 2–5 | 2–3 GB |
| Vanilla or Paper | 6–10 | 4 GB |
| Paper with a modest plugin set | 6–10 | 4–6 GB |
| Vanilla or plugins | 11–20 | 6–8 GB |
| Small or carefully optimized modpack | 5–10 | 6–8 GB |
| Large modpack | 5–15 | 8–12+ GB |
These figures assume a current Java runtime, ordinary survival play, and reasonable view and simulation distances. A heavily explored world with farms, chunk loaders, large redstone machines, or map-rendering plugins can change the result.
Simultaneous players matter more than total members
A server can have 50 people on its whitelist while only five play together. Memory pressure follows what is loaded now: online players, chunks, entities, plugins, and mod content. That is why a plan described as suitable for “about 10 players at once” is not necessarily limited to ten invitations.
Plan for your busiest normal session, then keep some headroom. Do not size for a one-off event where every person you have ever invited appears at spawn simultaneously; temporarily upgrading for that event is usually cheaper.
Why modpacks need more memory
Modded servers load extra registries, blocks, items, recipes, dimensions, and code. Some packs also encourage automation or chunk loading that keeps more of the world active. Use the pack’s server documentation as the first reference because two packs with a similar mod count can have very different requirements.
Avoid assigning every spare gigabyte to Java. An oversized heap can produce longer garbage-collection pauses, while the operating system and server panel still need memory of their own. Increase the allocation gradually and observe usage during a real session.
How to tell whether RAM is actually the problem
Check the server under normal load, not while it is empty. Memory is a likely constraint when the Java heap repeatedly fills, garbage collection runs very often, or the process is killed for exceeding its limit. A low TPS reading with plenty of unused memory points elsewhere.
Use this order:
- Measure heap use and garbage-collection behavior during a busy session.
- Check TPS and tick-time data with the tools recommended by your server software.
- Look for one plugin, mod, farm, or area responsible for a spike.
- Reduce view or simulation distance if chunk activity is the cause.
- Add memory only when the evidence shows sustained memory pressure.
Paper’s current documentation covers profiling and performance tools; use the documentation for the exact version you run rather than copying old JVM flags from a forum post.
CPU and storage still matter
Minecraft’s main game loop makes strong per-core CPU performance important. Fast storage matters during world saves and chunk loading. A host that advertises a large RAM number but places many servers on slow, oversubscribed hardware can feel worse than a smaller plan on a modern machine.
That does not mean you need a separate article’s worth of hardware shopping before inviting friends. It means RAM should be treated as capacity, not as a universal speed score.
A practical buying rule
Choose the smallest plan that meets the normal workload, verify it during your busiest week, and upgrade only when measurements justify it. Ask whether the host allows easy upgrades and whether CPU access is clearly described. For the wider price decision, see what a Minecraft server actually costs.
For WorldFolder’s planned plans, memory is bundled around a stated simultaneous-player use case rather than sold through an open-ended slider. Those estimates remain guidance, not hard player caps, and early-access performance still needs real-world validation.
Bottom line: 2–4 GB covers many small vanilla groups, 4–6 GB suits a larger plugin-based world, and modpacks commonly start around 6–8 GB. Measure before you upgrade; more RAM is useful only when RAM is the bottleneck.