Every hosting plan leads with a RAM number, and every new server owner asks the same question: how much is enough? The honest answer is that there is no official standard — Mojang does not publish a RAM table — so everything below is a rule of thumb drawn from community practice, the ranges experienced server owners actually run. Treat them as starting points, watch your server’s behaviour, and adjust. What eats RAM is not player count alone: loaded chunks, entities, mods and plugins, and how spread out your players are all matter as much.
This page contains affiliate links — see our affiliate disclosure. If you buy through one of these links we may earn a commission, at no extra cost to you.
Rules of thumb by play style
| Play style | Players | RAM starting point |
|---|---|---|
| Vanilla, a few friends | 1–5 | 2 GB |
| Vanilla or Paper with a handful of plugins | up to ~10 | 3–4 GB |
| Plugin-heavy Paper (economy, minigames, many plugins) | 10–25 | 4–6 GB |
| Light to medium modpack | a few to ~10 | 6–8 GB |
| Large modpack | 10+ | 8–12 GB |
| Big community, heavy modpack or huge pre-generated world | 25+ | 12–16 GB or more |
Read the table with its warning label on: these are experience-based ranges, not guarantees. A quiet 10-player vanilla server can run happily at the low end; five players flying in five directions on elytras can stress a server more than twenty players standing in one town.
What actually drives RAM use
- Loaded chunks. Every player loads the chunks around them, set by the server’s view-distance and simulation-distance. Ten players in one place share most of their chunks; ten players exploring separately load roughly ten areas at once.
- Entities. Farms, villager trading halls, item piles and mob grinders all hold entities in memory. Entity count is the most common hidden cause of “we have enough RAM but it still lags”.
- Plugins and mods. Each one adds its own memory footprint and its own loaded data; a modpack’s RAM appetite is set by the pack, not by Minecraft.
- World size on disk is not RAM — a 20 GB world does not need 20 GB of RAM, because only loaded chunks sit in memory. But big explored worlds correlate with more loaded areas, more entities and longer backups, which is why pruning dead chunks (server pruning guide) still helps.
RAM is not the whole story
Minecraft’s main world logic runs largely on a single thread, so CPU single-core performance is the other half of the equation — a smaller plan on a fast modern core can feel better than a bigger plan on slow shared cores. Fast NVMe storage helps chunk loading and generation. This is why the cheapest per-GB plan is not always the best-performing one, a point we weigh host by host in the hosting comparison.
Signs you genuinely need more RAM
- The console repeats “Can’t keep up!” warnings while players are online.
- Tick rate (TPS) falls when players spread out or explore, and recovers when they gather.
- Lag spikes hit exactly when new chunks generate, in several directions at once.
- The server crashes with out-of-memory errors after adding a modpack or a wave of plugins.
Before paying for a bigger plan, run through the free fixes: lower view-distance a notch, prune dead chunks, pre-generate the area your players actually use, and check for one entity farm doing the damage. If the warnings survive all of that, then upgrade — the optimisation work still pays off on the bigger plan.
Two buying mistakes to avoid
- Over-buying. Unused RAM does not make a server faster. Buy the range your play style suggests and upgrade when the signs above appear; every host in our comparison lets you move up a tier.
- Allocating everything on a self-host. If you run the server on your own machine or VPS, leave memory for the operating system and Java’s own overhead — giving the server process every last gigabyte invites the OS to kill it under pressure.
Ready to match a plan to your number? Compare Apex Hosting and Shockbyte for panel hosting, or Hostinger’s Game Panel VPS plans if you want the RAM inside a machine you fully control.
Download MCA Selector 2.9
Every server-side job in this guide starts with a local edit. Get the current release from the MCA Selector download page — the Windows installer, the cross-platform .jar, the macOS .dmg and the Linux .deb/.rpm, every button pointing at the official GitHub release files with the SHA-256 checksum listed, plus a clearly labelled site mirror as a fallback. It is free and open source under the MIT licence.