Most Minecraft servers need between 2 and 8 GB of RAM. A small vanilla server for a few friends runs well on 2-3 GB, a plugin server for a growing community wants 4-8 GB, and modpacks start around 4-6 GB and climb from there. The exact number depends on four things: how many players are online at once, whether you run plugins or mods, how far players can see, and which edition you play.
This guide explains where the memory goes, gives a number for the setups people ask us about most, and shows how to tell whether your server actually needs more.

The quick answer: Minecraft server RAM by setup
| Setup | Players online | RAM |
|---|---|---|
| Vanilla | 1-5 | 2 GB |
| Vanilla | 5-10 | 3-4 GB |
| Vanilla | 10-20 | 4-6 GB |
| Paper or Spigot, 10-30 plugins | 10-30 | 4-8 GB |
| Paper, large public server | 40+ | 8-12 GB |
| Light modpack (15-30 mods) | 1-10 | 4-6 GB |
| Medium modpack (30-50 mods) | 1-10 | 6-8 GB |
| Heavy modpack (FTB, All The Mods, 100+ mods) | 1-10 | 8-12 GB or more |
| Bedrock Dedicated Server | 1-10 | 1-2 GB |
These are starting points for Java Edition. For a number built from your own player count, server type, mods and world size, use the Minecraft RAM calculator. It runs the same model as this table.
What actually uses RAM on a Minecraft server

The server itself
An empty Java server already uses about 1-1.5 GB: the Java runtime plus the game, before anyone joins. That base is why 1 GB plans struggle even with one player, and why 2 GB is the realistic minimum.
Players and loaded chunks
Every player keeps a square of chunks loaded around them. At the default view distance of 10 that is 441 chunks per player, and players who spread out across the map load separate areas instead of sharing one. Plan for roughly 100 MB per player on a vanilla or Paper server, more when they explore fast with elytra or fly around to load new terrain.
View distance is the biggest lever you have. Dropping it from 10 to 6 or 7 cuts the chunks per player by more than half and most players never notice. You change it in server.properties (view-distance), and Paper also has a separate simulation-distance that controls how far mobs and farms keep running.
Plugins
Paper and Spigot run plugins, and most of them are small. Chat, permission and teleport plugins use a few MB each. The heavy ones are those that keep data or worlds in memory: Dynmap and other web maps, Citizens NPCs, big economy and world-management plugins, and extra worlds for minigames. Budget about 1-2 GB on top of the vanilla number for a typical 20-30 plugin setup.
Mods and modpacks
Mods are where RAM really climbs, because every added block, item, machine and dimension lives in memory. The pack size matters more than the player count: a 300-mod pack needs its 10-12 GB even with two players on, while 20 players on a 30-mod pack can run comfortably on 6 GB.
Two rules hold for almost every pack:
- Check the pack's own server requirements first. Most popular packs on CurseForge and Modrinth list a recommended server RAM, and the authors have tested it.
- Fabric packs are lighter than Forge packs of the same size, and performance mods like Lithium, FerriteCore and ModernFix lower memory use on both loaders.
Bedrock Edition
The Bedrock Dedicated Server is not Java and uses far less memory: 1-2 GB covers most servers with up to 10 players, and 2-4 GB handles 10-30. Add-ons add a little on top. If you instead let Bedrock players join a Java server through GeyserMC, size the server as a Java server and add roughly 0.5 GB for Geyser.
RAM for the setups people ask about most
These come straight from questions in our support chat.
"3-6 friends, vanilla survival." 3 GB is comfortable. Go to 4 GB if you plan big farms or explore a lot with elytra.
"10-15 players with a handful of plugins." 4-6 GB on Paper. Paper's chunk handling uses memory more efficiently than vanilla, so it is the better choice at this size anyway.
"2-3 players, but a modpack with hundreds of mods." Size for the pack, not the players: 10-12 GB, and check the pack page. Fewer players saves surprisingly little here.
"40-50 players with plugins." 8-12 GB on Paper, and lower the view distance to 6-8. At this size the processor becomes the limit before the memory does, see the next section.
"My kid wants a simple server with no mods." 2-3 GB is enough for vanilla with a few friends. You can always upgrade later.
Is more RAM always better?
No. Past what your server needs, extra RAM changes nothing. Minecraft runs most of its game logic on a single main thread, so a busy server with plenty of free memory can still lag when that thread cannot keep up. More CPU threads help with chunk generation and garbage collection, but they do not speed up the main game loop. When a server already has enough RAM and still lags, the cause is almost always entities, redstone, farms or chunk generation, not memory.
The opposite is also true: when a server is short on RAM, nothing else fixes it. You will see the symptoms below, and a bigger plan is the real fix.
"The panel says my RAM is at 95%": is that a problem?
Usually not. A Java server is given your whole plan as its memory limit, and Java holds on to memory it has already used instead of handing it back. So the memory graph on a healthy server climbs close to the top after a while and stays there.
The signs that you are really short on RAM are different:
- the console shows
java.lang.OutOfMemoryErroror the server restarts on its own - lag spikes every few seconds that line up with garbage collection
- chunks loading slowly or players getting stuck in unloaded terrain
If you see those, the Minecraft server lag guide shows how to find the cause with Spark before you spend money on more RAM.
RAM is not the same as storage
RAM is working memory and disk space is where your world and files are saved, and the two are sold separately. A plan with 4 GB of RAM still has its own storage for the world. Storage grows with how much of the map has been explored and how many backups you keep, not with how much RAM you have.
Get more out of the RAM you have
- Run Paper instead of vanilla when you do not need mods. It uses memory more efficiently and adds settings to tune performance.
- Lower
view-distanceto 6-8 on busy servers. This saves the most memory of any change. - Pre-generate the world with a plugin like Chunky so exploring does not have to generate new chunks while players wait.
- Use optimized JVM flags. New DoomHosting Minecraft servers start with Aikar's flags switched on, which tune Java's garbage collector to cut lag spikes. On an older server, switch on Optimized JVM flags (Aikar's) on the Startup tab.

Our recommendation
For friends playing vanilla or with a few plugins, start at 3-4 GB. For a modpack, start at the pack's recommended amount, usually 6-8 GB, and more for the big kitchen-sink packs. If you are unsure, start smaller: you can upgrade your RAM from the control panel at any time, so there is no reason to pay for memory your server does not use yet.
Want a number for your exact setup? Try the Minecraft RAM calculator, or see our Minecraft server hosting plans.




