Minecraft hosting guide
How many players per GB of RAM
There is a rule of thumb, and it is useful as long as you know the two things it leaves out. This page gives the rule, the two things, and a table that turns them into a plan size for the group you actually have.
The short answer
The rule
2 GB before the first player, then 1 GB per 4 to 5 players on a vanilla or lightly plugged world.
What it forgets
Modpacks, and the processor. One core steps the whole world in fifty milliseconds, and farms tick with nobody online.
So for a normal evening
Up to 5 players on Mini Performance, 6 to 20 on Starter Performance, more or a modpack one size up. The table below has every row.
Below is the rule worked out, the two things it leaves out, and how to read the number on your own server.
The rule, and the two gigabytes it forgets
- 2 GB base
- 1 GB per 4 to 5 players
- Vanilla
- Plugins
- Modpacks
A Minecraft server needs about two gigabytes before the first player logs in. That is the world it keeps loaded around spawn, the Java runtime itself and the software on top of it. Everything above those two gigabytes is what players use, and on a vanilla or lightly plugged server, one gigabyte carries roughly four to five people who are exploring, building and fighting at the same time.
So four gigabytes carries eight to ten players: two gigabytes of base plus two of headroom. The plain rule would say sixteen to twenty, because it starts counting from zero instead of from the two gigabytes of base. The rule of thumb is right once you start counting from that base number and count only the memory above it.
| Server | Players per GB above the base | Why |
|---|---|---|
| Vanilla or Paper with a few plugins | 4 to 5 | The world is the only thing in memory |
| Paper with twenty or more plugins | 3 to 4 | Each plugin keeps its own tables and caches |
| Light modpack (under 100 mods) | 2 to 3 | Every mod adds blocks, items and recipes to memory |
| Heavy modpack (ATM, RLCraft, Pixelmon) | 1 to 2, after a 6 GB base | The pack itself needs six to eight gigabytes before anyone joins |
Why the processor decides before memory does
Memory sets how much the server can hold. The processor sets how fast it can step through it, and one tick has fifty milliseconds to move every loaded mob, run every hopper and load every chunk somebody walked into. That work runs on one core, and when it takes longer than fifty milliseconds the server drops below twenty ticks a second whether or not memory is half empty.
The practical result: a busy server with forty players and a wandering explorer generating new terrain runs out of tick before it runs out of memory. That is why the table below stops at forty on the standard line, and why the Performance line exists: the same memory with vCPU that are reserved for your server on an AMD Ryzen 9 5900X in Germany or an AMD Ryzen 9 7950X with DDR5 RAM in Poland, a full thread each on a faster machine.
What TPS and MSPT measure, and how to read them on your own server
Plan size by player count
Take the row for the group you have on a normal evening, not the largest evening you can imagine. A server can move up a size later without a reinstall, and the world moves with it.
| Players at once | Vanilla or light plugins | Heavy plugins | Modpack |
|---|---|---|---|
| Up to 5 | Mini Performance, 4 GB | Mini Performance, 4 GB | Starter Performance, 8 GB |
| Up to 10 | Mini Performance, 4 GB | Starter Performance, 8 GB | Standard Performance, 12 GB |
| Up to 20 | Starter Performance, 8 GB | Standard Performance, 12 GB | Premium Performance, 24 GB |
| Up to 40 | Standard Performance, 12 GB | Premium Performance, 24 GB | Premium Performance, 24 GB on the Performance line |
The Java flag that sets the heap is set for you in the panel, and it is set below the plan size on purpose: a server with all of its memory given to Java has nothing left for the system that runs it, and swaps.
The longer memory guide, with the view distance and pack sizes
Check the number on your own server
The panel draws memory and tick time as a graph. Memory near full with a tick time that is fine means the server holds more than it has room for, and a bigger plan is the answer. Memory half empty with a tick time climbing towards fifty milliseconds means one core is running out of time, and more memory changes nothing. Read both while the server is busy: an empty server sits at twenty ticks on any plan we sell.
The four sizes in the table
Memory and processor are stated on every plan page, the nightly backup costs nothing, and moving up a size keeps the world.
Questions people ask about memory
How many players can a 4 GB Minecraft server hold?
Eight to ten on a vanilla or lightly plugged world, because two of the four gigabytes go to the world and the runtime before anyone joins. With a modpack, four gigabytes is for one or two people.
How many players can an 8 GB server hold?
Twenty to thirty on vanilla or light plugins, ten to fifteen with a heavy plugin set, and five to ten on a light modpack. A heavy pack like All the Mods wants eight gigabytes for the pack alone.
Does more RAM make the server faster?
Only when memory was the thing that was short. A server sitting at half its memory with a rising tick time gains nothing from doubling it, because the tick runs on one core and that core is what ran out.
Should I give Java all of the memory?
No. The panel sets the heap below the plan size, so the system that runs the server keeps enough to breathe. A heap that equals the plan size pushes the server into swap and makes everything slower.
How much RAM does a modpack server need?
Six to eight gigabytes for the pack itself, then one gigabyte per one or two players. Twelve gigabytes is the size most heavy packs are comfortable on with a group of friends.
Written and checked by the Astroworld Hosting team. Last reviewed on 6 September 2026.
Delivery: most servers are handed over instantly and run within seconds of payment, the rest follow within 60 minutes during the day and within 12 hours at night.