What a Minecraft server uses memory for
A Java server keeps everything it simulates in memory: the chunks around each player, the entities in them (mobs, dropped items, minecarts), the data of every plugin or mod, and Java's own overhead. So three things drive RAM: how many players are online at once and how far they see, which software you run (Forge with 200 mods needs several gigabytes before anyone joins) and how many extra worlds you load.
Player count matters less than people think. Ten players standing together load roughly the same chunks; ten players exploring in ten directions load ten times as many. That's why view distance is one of the biggest levers you have. View distance vs simulation distance explains both settings.
How much RAM by players, plugins and mods
These figures come straight from our plan calculator, using the same model it uses for its recommendations: a base for the software, a cost per plugin or mod, a cost per player that grows with view distance, and 20% on top for Java itself.
| Your server | RAM to start with | Plan that fits | Price |
|---|---|---|---|
| Vanilla, 5 friends | 2 GB |  Apolo | $3.00/month |
| Paper SMP, 10 players, 20 plugins | 3 GB |  Ares | $6.00/month |
| Paper, 25 players, 40 plugins | 5 GB |  Atenea | $9.00/month |
| Paper, 50 players, 60 plugins | 7.5 GB |  Hades | $12.00/month |
| Fabric, 10 players, 100 mods | 6 GB | Atenea | $9.00/month |
| Forge modpack, 10 players, 250 mods | 14 GB |  Odín | $24.00/month |
Why more RAM doesn't make a server faster
Memory is a bucket, not an engine. Once the server has enough to hold what it simulates, extra gigabytes sit idle. Java will happily fill a bigger bucket with garbage before cleaning it, so a server can look like it uses everything you give it without actually needing it.
What decides whether a Minecraft server lags is the main thread: each world ticks 20 times per second, and every tick has 50 milliseconds to finish. If mobs, redstone, hoppers and plugins take longer than that, TPS drops and everyone feels it. No amount of RAM shortens a tick; a faster processor core does. That's the whole story behind why we picked a Ryzen 7 9700X.
- Out-of-memory crashes (
OutOfMemoryError) → you do need more RAM. How to confirm it. - TPS below 20 with memory to spare → it's processor time: entities, redstone or a plugin. Find the cause.
- Lag for only one player → it's their connection or their PC. TPS or FPS?
DDR4 vs DDR5 ECC: does the kind of memory matter?
On speed, DDR5 has more bandwidth than DDR4, which helps when the processor moves a lot of chunk data, but on a small server you won't see it as extra TPS. What matters more for a machine that runs for months is ECC, error-correcting code.
Memory occasionally flips a bit on its own. On a gaming PC that's a rare crash you blame on a driver. On a server running 24/7 with your world in memory, a flipped bit can mean a crash or, worse, a corrupted chunk written to disk. ECC memory detects and corrects single-bit errors before anything uses the bad value. It's standard in data centres and uncommon in budget game hosting.
| Typical budget host | EnduranceNodes | |
|---|---|---|
| Memory | Usually DDR4; ECC rarely mentioned | DDR5 ECC |
| Bit errors | Unnoticed until something crashes | Single-bit errors corrected on the fly |
| What you notice | Rare crashes nobody can explain | Nothing, which is the point |
The node's full spec sheet is on the hardware page.
Minecraft hosting plans by RAM
Every EnduranceNodes plan runs on the same node with the same features. Only the size changes, and every size costs the same per gigabyte, so the choice really is just how much memory your world needs:
| Plan | RAM | CPU | NVMe | Price |
|---|---|---|---|---|
 Hermes | 1 GB | 1 vCore | 15 GB | $1.50/month |
| Apolo | 2 GB | 1.5 vCores | 25 GB | $3.00/month |
| Ares | 4 GB | 2 vCores | 40 GB | $6.00/month |
| Atenea | 6 GB | 2.5 vCores | 55 GB | $9.00/month |
| Hades | 8 GB | 3 vCores | 70 GB | $12.00/month |
 Poseidon | 10 GB | 3.5 vCores | 85 GB | $15.00/month |
 Thor | 12 GB | 4 vCores | 100 GB | $18.00/month |
| Odín | 16 GB | 5 vCores | 130 GB | $24.00/month |
 Zeus | 20 GB | 6 vCores | 160 GB | $30.00/month |
 Cronos | 24 GB | 7 vCores | 190 GB | $36.00/month |
 Atlas | 28 GB | 8 vCores | 225 GB | $42.00/month |
 Ender | 32 GB | 10 vCores | 260 GB | $48.00/month |
Start one size smaller than you think. If the server outgrows it, upgrading takes a minute in the client area and you pay only the prorated difference for the rest of the cycle. The world stays where it is.
If you remember one thing
Size for what you run, not for what you fear: 2–4 GB for friends, 6–8 GB for a community, more only for big modpacks. When it lags, measure before upgrading; the answer is usually processor time, and that's where good hardware earns its price.
Questions people ask
For vanilla or Paper with up to about 5–8 players, yes. Add plugins, more players or mods and you'll want 4 GB or more.
Light Fabric packs run in 4–6 GB; big Forge modpacks with 200 or more mods usually need 10–16 GB. Check what the modpack itself recommends for servers.
Extra RAM won't speed the server up, and giving Java far more than it needs can make garbage collection pauses longer. Size for your real use.
Not directly. It keeps a 24/7 server stable by correcting memory errors that would otherwise cause crashes or corrupted data.
Yes, any time from the client area. You pay only the prorated difference for the days left in your billing cycle, and your world stays on the server.
About this article: It comes from what I have learned running EnduranceNodes, and it is published here first. We sell Minecraft hosting, so everything I say about us can be checked on this site, and I point out where we are not the best fit.