Skip to content

Game servers

How much RAM does a Minecraft server need?

Realistic RAM numbers for vanilla, Paper and modded Minecraft servers, plus the flags and settings that make every gigabyte go further.

RAM is the first number everyone looks at when picking a Minecraft server plan, and it is also the one most often overbought or underbought. The right amount depends on four things: which server software you run, how many mods or plugins you load, how many players are online at once, and how far each player can see. This guide walks through each one with realistic numbers, then covers the settings that let you get more out of the memory you already have.

Want a number for your exact setup? Our free Minecraft server RAM calculator works it out from your server software, mods, players and view distance, and writes the startup command for you.

Quick answer

If you just want a starting point, use this table. These figures assume a modern version (1.20 or newer) and a world that has been pre-generated, which we cover further down.

Server typePlayers onlineSuggested RAM
Vanilla or Paper, friends only1 - 52 - 3 GB
Paper with a handful of plugins5 - 204 - 6 GB
Paper community server with many plugins20 - 506 - 10 GB
Light modpack (under 100 mods)1 - 104 - 6 GB
Medium modpack (100 - 200 mods)1 - 106 - 8 GB
Large kitchen-sink modpack (200+ mods, such as All the Mods)1 - 108 - 12 GB
Large modpack with a bigger group10 - 3012 GB or more

Treat these as ranges, not rules. A tiny vanilla server where everyone builds in one village needs far less than the same player count spread across a huge world, and one badly behaved mod can double memory use on its own.

Why the server software matters

Vanilla

The official server jar from Mojang is the baseline. It works fine for a few friends, but it has no performance tuning and no plugin support. Memory use grows quickly as players explore, because every loaded chunk, entity and block entity (chests, furnaces, hoppers) lives in RAM. For anything beyond a small private world, there is little reason to stay on vanilla.

Paper and Purpur

Paper is a drop-in replacement for the vanilla server that keeps the same gameplay but adds a long list of performance fixes: faster chunk loading, smarter entity handling, configurable limits on things like hoppers and mob spawning, and Bukkit/Spigot plugin support. Purpur builds on Paper and adds extra gameplay options. On the same hardware, Paper usually runs more players with less lag than vanilla, and it is the default choice for community servers.

Plugins add to memory use, but most are small. The heavy ones are those that keep lots of data loaded, such as dynamic web maps, large economy or shop systems, and anti-cheat plugins. If you run 30 or more plugins, budget an extra 1 - 2 GB.

Fabric, Forge and NeoForge modpacks

Mods are where memory requirements really climb. Every mod adds its own blocks, items, recipes and world generation, and all of it is loaded into memory when the server starts. A large modpack can use 4 - 5 GB before a single player joins. On top of that, tech mods with pipes, machines and automated farms keep chunks loaded and ticking around the clock.

Modpack authors often list a recommended server RAM on the pack's page. Use that as your floor, then add 1 - 2 GB for each extra handful of active players. Fabric packs built around performance mods such as Lithium and FerriteCore tend to use noticeably less memory than Forge packs of a similar size.

How player count and exploration affect RAM

Each online player keeps a square of chunks loaded around them. The size of that square is set by the view distance. Players standing close together share chunks, so ten players in one town cost far less than ten players each exploring in a different direction.

The worst case is a group of players flying with elytra into new terrain. The server has to generate fresh chunks, hold them in memory and save them to disk, all at once. This is the most common cause of a server that runs fine most of the time but lags or runs out of memory in bursts.

View distance and simulation distance

Since Minecraft 1.18 there are two separate settings in server.properties:

  • view-distance - how many chunks around each player are sent to their client so they can see them.
  • simulation-distance - how many chunks around each player are actually ticked: mobs move, crops grow, redstone runs.

Simulation distance has the bigger effect on CPU, while view distance has the bigger effect on memory and bandwidth. A sensible setup for most servers is:

view-distance=8
simulation-distance=6

The vanilla default view distance is 10. Dropping it to 8 loads roughly a third fewer chunks per player, which most players will not notice, especially if they use a client mod such as Distant Horizons or Bobby for far-away scenery. For very busy servers, a simulation distance of 4 or 5 is still playable.

On Paper, you can also cap entity counts and tune per-world settings in config/paper-world-defaults.yml, which helps on servers where players build large mob farms.

Pre-generate your world with Chunky

World generation is one of the most expensive things a Minecraft server does. Generating the world ahead of time, before players arrive, removes most of the lag spikes caused by exploration. The standard tool for this is Chunky, available as a plugin for Paper and as a mod for Fabric, Forge and NeoForge.

Once installed, run these commands from the server console:

chunky world world
chunky center 0 0
chunky radius 5000
chunky start

This generates a 10,000 by 10,000 block square around spawn. Repeat with chunky world world_nether and a smaller radius, since one block in the Nether equals eight in the Overworld. You can check progress with chunky progress and pause with chunky pause.

Pair the pre-generated area with a world border so players cannot wander outside it:

worldborder center 0 0
worldborder set 10000

Pre-generation is CPU heavy, so run it when nobody is playing. It also uses disk space: a 5,000 block radius in a modern version typically takes several gigabytes, so keep an eye on your storage.

Set the memory flags correctly

Leave headroom below your plan's limit

The -Xmx value tells Java the maximum heap size, but Java uses more memory than just the heap. Metaspace, thread stacks, the garbage collector and native libraries all sit on top. If you set -Xmx equal to your plan's full RAM, the server will try to use more than it has. Leave about 10 - 15 percent, or at least 1 GB, for this overhead. On an 8 GB plan, a heap of around 7 GB is a good target.

Aikar's flags

Aikar's flags are a well-known set of Java garbage collection settings tuned for Minecraft. They make garbage collection pauses shorter and more predictable, which reduces the small, regular stutters that players feel as lag. They are recommended by the Paper team and work on modded servers too. For a heap under 12 GB:

java -Xms7G -Xmx7G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseIntervalMillis=5000 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true -jar server.jar --nogui

For a heap of 12 GB or more, change these values:

-XX:G1NewSizePercent=40
-XX:G1MaxNewSizePercent=50
-XX:G1HeapRegionSize=16M
-XX:G1ReservePercent=15
-XX:InitiatingHeapOccupancyPercent=20

Two points worth knowing. First, setting -Xms and -Xmx to the same value is intentional: it stops Java from repeatedly growing and shrinking the heap. Second, more RAM is not always better. Giving a small server 16 GB can make garbage collection pauses longer, because there is more memory to sweep each time. Size the heap for what the server actually uses, plus some room to grow.

How to tell if you need more RAM

Lag is not always a memory problem. Before upgrading, find out what is actually slow. The spark profiler (a plugin for Paper and a mod for Fabric and Forge) is the easiest way:

spark health
spark gc
spark profiler start
spark profiler stop
  • spark health shows TPS (ticks per second, 20 is perfect), MSPT (milliseconds per tick, under 50 is good) and memory use.
  • spark gc shows how often garbage collection runs and how long it pauses. Frequent long pauses with memory near the limit mean you need more RAM.
  • spark profiler records what the server spends its time on, so you can spot a single heavy mod, plugin or farm.

If memory sits comfortably below the limit but TPS is low, the bottleneck is the CPU, not the RAM. Minecraft's main game loop runs mostly on one thread, so single-core speed matters a lot. In that case, lowering simulation distance, limiting entities, or moving to faster hardware will help more than extra memory.

Signs you have too little RAM

  • The server crashes with java.lang.OutOfMemoryError in the console.
  • Lag spikes line up with players exploring new areas.
  • spark shows memory constantly near the maximum, with garbage collection running every few seconds.
  • Startup fails or takes several minutes on a modpack.

Picking a plan at Zettako

Our Minecraft server hosting comes in two tiers. Budget plans suit small vanilla and Paper servers for friends. Premium plans run on faster processors with DDR5 memory, which is the better fit for modpacks and busy community servers where single-core speed matters. Every server includes DDoS protection, one-click updates, mod support through the control panel and a free subdomain.

Memory limits on our servers are enforced proactively rather than by abruptly killing the process, so a server that reaches its limit fails predictably instead of vanishing mid-game. Even so, the flags above will help you stay well clear of that point.

To size a plan for your own server, run your numbers through the RAM calculator, which marks the smallest plan that fits. If you are unsure, start one size smaller than you think you need, pre-generate your world, apply the settings in this guide and watch spark for a week. Upgrading later is easy, and you will have real numbers to base the decision on. Our support team is also happy to look at a spark report and recommend a plan.

Ready to start your Minecraft server?

Pick a Budget or Premium plan and your server deploys automatically. Not sure about the size? Open a ticket and we will help you choose.

Starting at £5.95GBP/mo