How much RAM does a Minecraft server need?
"How much RAM do I need?" is the question right behind every crash and lag complaint. Here's honest guidance by player count and vanilla vs modded, and why throwing RAM at lag often doesn't help.
Out-of-memory errors and lag are two of the most common walls people hit, especially on free tiers and on modpacks. The instinct is to buy as much RAM as possible, and that's usually the wrong move.
RAM matters, but only up to what your server actually uses. A lot of what feels like a memory problem is really single-thread CPU. Here's a realistic starting point and how to tell which problem you actually have.
In this guide
At a glance
Starting points, not promises, and the Modded column is the least reliable of the three. A big modpack is its own category: start from the figure on the pack's own page, which beats every table on the internet including this one.
Start from player count and setup
Start at roughly 2 GB for a few friends on vanilla, around 4 GB once you're at 10–20 vanilla players, and 6 GB or more the moment mods enter the picture.
Two things move the number, and player count is the smaller one. What people are doing matters more than how many of them there are: a group of four building a mob farm and flying around at 32 chunks of view distance is a heavier server than twelve people standing in one town. Start from those numbers, then watch the real figure.
The catch
Don't spend the whole box. Java needs memory on top of whatever you hand the server, and the machine's operating system needs its own. Give the server every gigabyte and there's nothing left for either, so the system's out-of-memory killer ends your server mid-session. Leave headroom above what the server actually uses instead of maxing the slider.
Vanilla vs modded is the real split
Best for: Vanilla or a few plugins: the small sizes are genuinely enough, and cheaper.Not for: A big modpack on a small size: that's the one case where under-buying costs you the evening instead of a few cents.A handful of vanilla friends barely touch memory. A heavy modpack can use several times more for the same player count, because every mod loads its own blocks, items, recipes and world generation into the same world.
It's the number of mods that drives it, not the number of players, which is why a 200-mod pack with three people on it needs more than a vanilla server with twenty. If you're running something at the scale of RLCraft or All The Mods, take the pack's own recommendation seriously; it comes from people who've watched that pack boot.
The catch
A pack's recommended RAM is usually written for the client, the server, or both without saying which. When the pack's page is ambiguous, the server side is generally the lighter of the two, but this is worth reading twice rather than sizing on a number that meant something else.
Know when more RAM won't help
Past what your server actually uses, extra RAM does nothing at all for lag. It sits there, allocated and empty.
Minecraft's server does its world simulation on one thread, so tick lag (redstone contraptions, big mob farms, a high view distance, thousands of loaded entities) is a single-thread CPU problem. No amount of memory touches it. The tell is which number is moving: memory climbing toward the ceiling is a RAM problem, a tick time above 50 ms with memory sitting comfortably is not.
The catch
This is the one that costs people real money. "It's lagging, buy more RAM" is the most-repeated bad advice in Minecraft hosting, and every host on earth is happy to sell you the upgrade that doesn't fix it.
Right-size instead of over-buying
Lower your view distance, find the laggy chunk, and try Paper before you buy a single gigabyte: the cheap fixes work more often than the expensive one.
Then watch the actual memory figure over a week of normal play. If it sits well under the ceiling, you're already the right size; if it climbs to the top and stays there, that's your signal to step up, and only then.
Lower view distance, then simulation distance. These two are the biggest single lever on a laggy server, and they cost nothing.
Find the laggy chunk. One overbuilt farm or a pile of dropped items usually accounts for most of it.
On a plugin server, try Paper instead of vanilla: it's free, and it does more for tick time than a memory upgrade would.
Only now, if memory is genuinely at the ceiling, add a gigabyte or two. Not five.
What the RAM actually costs
Best for: A group whose play is bursty: pay for the evenings you're on, nothing for the days you're not.Not for: Anyone who wants one predictable monthly charge and never wants to think about hours again. That's a flat plan, and plenty of hosts sell a good one.Voxi is priced per gigabyte per hour that a server is actually running: $0.005 per GB-hour, which works out to $3.60 per GB for a month if it literally never sleeps. A 2 GB world running around the clock is $7.20 a month; 4 GB is $14.40; 8 GB is $28.80. A world that naps when nobody's on costs a lot less than that: the same 2 GB world at about three hours most nights is around $0.90 a month.
The honest catch: the smallest top-up we sell is $5, so a world costing under a dollar a month means topping up rarely rather than paying a small amount often. And if you'd rather have one flat number you never think about, a fixed monthly plan somewhere else is a legitimately better fit than counting hours. Right-size it, watch what it really uses, and step up only when the number tells you to.
FAQ
How much RAM for 10 players?
For vanilla, around 4 GB is a sensible starting point for roughly 10–20 players. Add mods or plugins and you'll want 6 GB or more.
Is more RAM always better?
No. Past what your server actually uses, extra RAM doesn't reduce lag. Much of what feels like lag is single-thread CPU (redstone, mob farms, view distance), which more memory can't fix.
How much RAM does a modded server need?
More than vanilla: 6 GB and up as a floor, and large modpacks want more. Every mod loads extra content, so modded memory needs scale with the pack, not just the player count. Use the figure on the pack's own page over any general rule.
What does a gigabyte actually cost?
On Voxi, $0.005 per GB for every hour the server runs ($3.60 per GB a month if it never sleeps), so a 2 GB always-on world is $7.20 a month and a napping one is far less. The smallest top-up is $5.
My server has plenty of RAM free and still lags. Why?
Because that lag isn't a memory problem. Minecraft simulates the world on one thread, so redstone, mob farms, entity pile-ups and a high view distance show up as tick lag no matter how much memory is free. Lower view and simulation distance first.
Read next: how to install a modpack on your Minecraft server.
Comparing hosts? See how Voxi compares to Aternos, Minehut, Exaroton and the paid hosts.
Find out what your world actually uses
Start a free server on Voxi, play a normal week, and read the real memory figure before you size anything. It's $0.005 per GB-hour while it runs and nothing while it sleeps. If you'd rather have one flat monthly bill, a fixed plan elsewhere is the better fit.