Home — Home › Server Requirements
How much RAM, CPU, and bandwidth a Minecraft server actually needs — with a RAM-to-players table for vanilla, plugins, and modpacks.
The single most common question when hosting a Minecraft server is "how much RAM do I need?" The honest answer is: it depends on your edition, how many players you expect, and — by far the biggest factor — whether you run vanilla, plugins, or mods. This page breaks down the real requirements and gives you a table to match a RAM tier to your community.
Minecraft servers are memory-hungry. Every loaded chunk, entity, and mod lives in RAM, so running out of memory is the most common cause of lag and crashes. Player slots are almost never the real limit — RAM is. A server "for 20 players" that only has 2 GB will stutter long before it fills up, while the same 20 players on 8 GB run smoothly.
Give the server dedicated RAM rather than sharing it, and do not allocate literally all available memory — the operating system and Java overhead need headroom. On FluxCraft each plan tier is a fixed RAM allocation, so you always know exactly what your world has to work with.
Use this as a starting point. Modded servers need far more RAM per player than vanilla, and heavy modpacks can double these numbers:
| RAM | Vanilla / light plugins | Modded | Good for |
|---|---|---|---|
| 2 GB | Up to ~10 players | Not recommended | Friends group, vanilla survival |
| 4 GB | ~10–15 players | Small/light packs | Small plugin server (Paper/Spigot) |
| 6 GB | ~15–25 players | Light–medium modpacks | Growing community or a light pack |
| 8 GB | ~25–40 players | Medium modpacks | Active plugin server or ATM-style pack |
| 12 GB | 40+ players | Heavy modpacks (RLCraft, big AtM) | Large modded community |
| 16 GB+ | 60+ players | Very heavy packs / large map | Networks and big public servers |
Minecraft's server tick loop is largely single-threaded, so a CPU with high per-core (single-thread) performance matters more than a high core count. This is why a fast modern core outperforms many slow cores for one world. More cores help when you run several separate servers or use Paper's parallel world features, but for one busy world, clock speed and IPC win. Keeping the server tick at a healthy 20 TPS is the goal — drops below that are what players feel as lag.
A vanilla world starts small but grows as players explore and generate chunks; modded worlds and backups need more disk. Bandwidth requirements are modest per player, but a public server with many concurrent players and a large view-distance adds up. View-distance and simulation-distance are two of the highest-impact settings you control: lowering them from the default can dramatically cut both RAM and CPU load on a busy server.
Estimate your peak concurrent players, then decide vanilla vs plugins vs mods, and size up one tier if you plan to grow or run a demanding modpack. It is always easier to start a tier higher than to fight constant lag. On FluxCraft you can scale RAM up or down as your community changes, so you are never locked into an oversized plan.
2 GB for vanilla with up to ~10 players, 4 GB for small plugin servers, 6–8 GB for light-to-medium modpacks, and 12 GB or more for heavy modpacks like RLCraft or large All the Mods packs.
There is no fixed cap. Practically, a 2 GB vanilla server holds ~10 players, 8 GB can handle 25–40, and 16 GB+ supports 60+ — but mods, view-distance, and world size lower these numbers substantially.
RAM is usually the first bottleneck, but Minecraft's tick loop is largely single-threaded, so single-thread CPU speed strongly affects TPS (tick rate) on a busy world. You want both: enough RAM and a fast core.
Far more than vanilla. Light packs are fine on 4–6 GB, medium packs want 8 GB, and heavy packs such as RLCraft or big All the Mods versions need 8–12 GB or more.
Deploy a Minecraft server on FluxCraft in under 30 seconds — first month free.