How Much RAM Does a Minecraft Server Need?

Every hosting page sells you gigabytes, and almost none of them tell you how many you actually need. This guide gives you real numbers — measured on the hardware we rent out, not copied from a spec sheet — so you can pick a plan once and stop worrying about it.

The short answer

Every server ships on vanilla, and the panel switches you to Paper, Purpur or Spigot in a click. Paper is worth having the moment you want plugins — but it runs more threads and a heavier chunk system than vanilla, so we only recommend it from 2 GB (Gold) upward. That is also where the panel's mod browser unlocks — mod loaders and individual mods need 2 GB, and one-click modpack installs need 3 GB (Diamond). Plugins are the exception: the plugin browser is open on every plan, including Coal. Custom jars and modpacks belong on 2 GB and up.

If you're torn between two rows, take the larger one. Running out of memory doesn't slow a Minecraft server down gracefully — it kills the process outright.

What actually uses the memory

Player count is the number everyone asks about, but it's rarely the thing that fills your heap.

World size and exploration. Every chunk a player loads stays in memory for a while. A group of four sprinting into fresh terrain with elytra generates far more memory pressure than twenty people standing in a spawn town.

View distance. This is the single biggest lever you control. Dropping view-distance from 10 to 6 in server.properties can cut memory use dramatically, and most players won't notice on a survival server.

Plugins. A dozen small utility plugins are cheap. Anything that stores per-block data — world protection, block logging, chunk-based economies — is not. CoreProtect logging a busy server will happily use hundreds of megabytes on its own.

Mods. Modpacks are in a different category entirely. A 150-mod pack wants 4 GB before a single player joins, which is what our Emerald tier is for. We gate one-click modpack installs at 3 GB (Diamond) for exactly this reason — below that a real pack doesn't finish loading, and selling you the button would just be selling you a crash.

Entities. Mob farms, item-sorting systems and dropped-item pileups all cost memory and CPU. If your server slows down after a build project, entities are the first thing to check.

Matching a plan to your server

Our five tiers are all priced the same per gigabyte — $7/GB, so nothing is a trap:

• Coal — 1 GB, $7/mo — vanilla survival with a handful of friends.
• Iron — 1.5 GB, $10.50/mo — a small SMP with a sensible plugin list.
• Gold — 2 GB, $14/mo — plugin-heavy servers and small modpacks.
• Diamond — 3 GB, $21/mo — mid-size modpacks and communities that outgrew one world.
• Emerald — 4 GB, $28/mo — large modpacks, or a crowd.

Every plan gets the whole amount to itself. We never sell memory we don't have, so the RAM you pay for is yours alone — a busy neighbour can't take your ticks.

How to tell you need more

Watch for these, in roughly the order they appear:

1. "Can't keep up! Is the server overloaded?" in your console. Occasionally is normal after a world save. Constantly is not.
2. TPS below 18. Run /tps if you have a plugin that provides it. Twenty is perfect; below 15 is visible as rubber-banding and slow block breaking.
3. Long pauses every few seconds. That's garbage collection thrashing because the heap is nearly full.
4. The server restarting on its own, with the console showing an exit before any shutdown message. That's the out-of-memory killer.

Before you upgrade, try lowering view-distance and simulation-distance, and check whether one plugin is responsible. If the numbers don't move, you need more RAM.

Upgrading without losing anything

Changing plans doesn't touch your world. Open a ticket from your billing account, tell us which tier you want, and we move the limits on the existing server — same files, same IP and port, same players' bookmarks. There's a short restart and that's the whole disruption.

Common questions

Does more RAM increase my player slots? Not directly — slots are a setting, not a resource. Memory determines how many players your server can hold smoothly. Every plan we sell has unlimited slots configured; the RAM is what decides the practical number.

Is more RAM always better? No. Giving Java a huge heap can make garbage collection pauses longer, not shorter. Sized correctly is better than oversized.

Do modpacks really need 4 GB? Most mid-size packs run in 3 GB. Large kitchen-sink packs want 4 GB or more, and their own launcher usually states a figure — trust it, and remember the server needs about as much as the client.

What about CPU? Minecraft's main loop is single-threaded, so a fast core matters more than many cores. Every plan here gets at least a full core of an AMD EPYC 9354P, which is why our smallest tier still keeps up with more players than its RAM suggests.

Still unsure? Tell us what you're building — the mod list, the plugin list, roughly how many friends — and we'll tell you which tier fits. We'd rather put you on the right plan than sell you the big one.