How much RAM does a Minecraft server need?

A small Paper SMP with 10–20 players and a moderate plugin stack typically needs 4–6 GB of dedicated RAM. Vanilla with 5 players can run on 2 GB. Heavy plugin networks, large explored worlds, or modpacks with 100+ mods often need 8–16 GB or more. RAM must cover the JVM heap, loaded chunks, entity data, plugin caches, and headroom for garbage collection — not just the server jar itself.

How much RAM for 20 players on a Paper server?

For a standard survival SMP with 20 concurrent players, 20–30 plugins (EssentialsX, LuckPerms, WorldGuard, economy plugins), a medium-sized explored world, and view distance 10, plan for 6 GB as a comfortable target. 4 GB works if plugins are lean and view distance is 8, but you will see lag during chunk generation and large player gatherings.

Is 2 GB enough for a Minecraft server?

2 GB is only realistic for a vanilla or very lightly modded server with 1–5 players, a small world, and view distance 6–8. Most Spigot/Paper servers with plugins will hit OutOfMemoryError or constant GC pauses at 2 GB once more than a handful of players explore simultaneously. Hosting providers advertising "2 GB unlimited players" are overselling.

Does Paper use less RAM than Spigot?

Paper uses RAM more efficiently per tick — it reduces entity AI overhead, optimises chunk loading, and has better garbage collection behaviour — but the base heap requirement is similar. Paper often lets you run the same player count on slightly less RAM without lag, or more players on the same RAM. Purpur builds on Paper with similar characteristics.

How does view distance affect RAM usage?

View distance is the radius in chunks around each player that stays loaded. Because chunks are 16×16 blocks and the world is 384 blocks tall (1.18+), each additional chunk radius loads exponentially more block data, lighting, and entity information. Going from view distance 8 to 12 can increase RAM usage by 30–50% with the same player count. Paper's simulation-distance setting lets you decouple mob spawning range from render distance to save RAM.

How much RAM does a modded Minecraft server need?

Modpacks vary wildly. A lightweight Fabric pack with 50–80 mods and 5–10 players often needs 6–8 GB. Popular Forge packs with 150–250 mods (All the Mods, FTB packs) typically need 8–12 GB for small groups and 12–16 GB for 10+ players. Each mod adds classes, block states, and world generation data to the JVM Metaspace and heap. Always check the modpack author's recommended RAM.

What JVM flags should I use for a Minecraft server?

The community-standard Aikar G1GC flags (included in this calculator's output) tune the G1 garbage collector for Minecraft's allocation patterns. Set -Xms and -Xmx to the same value on a dedicated VPS to avoid heap resize pauses. Example: java -Xms6G -Xmx6G [Aikar flags] -jar paper.jar nogui. Never allocate 100% of your VPS RAM to -Xmx — leave 1–2 GB for the operating system and any proxy or map software running on the same machine.

Should -Xms and -Xmx be the same?

On a dedicated machine running only Minecraft, yes — matching -Xms and -Xmx prevents the JVM from resizing the heap at runtime, which causes noticeable lag spikes. On a shared host where RAM is billed per allocation, some admins set -Xms lower than -Xmx to reduce idle cost, accepting occasional resize pauses when player count spikes.

Why does my server use more RAM than -Xmx?

-Xmx only limits the Java heap. The JVM also uses Metaspace (class metadata — significant with many plugins or mods), thread stacks, direct memory (Netty networking buffers), and off-heap native memory. Total process RSS in htop or your host panel will exceed -Xmx by 500 MB–2 GB depending on plugin count. That is normal — plan VPS RAM as heap + 1–2 GB overhead.

Do I need more RAM if I run BungeeCord or Velocity on the same VPS?

Yes. A proxy JVM typically needs 512 MB–1 GB on its own, plus whatever each backend server requires. Running proxy + one backend on a 4 GB VPS is tight; 6–8 GB is safer for a small network. Best practice is a separate VPS for the proxy when running multiple backend servers.

Tools · Hosting

Minecraft Server RAM Calculator

How much RAM does your server actually need? Adjust player count, Minecraft version, plugin load, world size, view distance, and mod count — every value updates the estimate instantly, with a memory breakdown, JVM startup flags, and a hosting tier guide so you know which plan to buy.

Paper · Spigot · Purpur · Fabric · Forge · BedrockIncludes Aikar G1GC JVM flags — copy & paste ready

Quick presets

Server configuration

Server software

Minecraft version era

Newer versions use more RAM per chunk due to taller worlds and richer block data.

Max online players — 20

150100200

Plugin / feature load

EssentialsX, LuckPerms, Vault, WorldGuard, etc. all add heap usage.

World size (explored area)

Check your world folder size in the server directory.

Dimensions / worlds

View distance (chunks)

Each extra chunk radius loads exponentially more terrain into memory.

BungeeCord / Velocity proxy on same machineDynmap or BlueMap web mapVoice chat (Simple Voice Chat, etc.)

Recommended RAM allocation

Minimum

6 GB

4642 MB — tight, expect GC pauses

Recommended

8 GB

6826 MB — stable for daily play

Comfortable

8 GB

7918 MB — headroom for spikes

Estimates include ~10% version-era adjustment for 1.21+. Actual usage varies with redstone, entity farms, and plugin quality.

Memory breakdown

Server software (JVM + jar)1200 MB (24%)

Online players (20 × per-player)2100 MB (42%)

Plugin / mod framework overhead512 MB (10%)

World data & chunk cache512 MB (10%)

Extra dimensions / worlds384 MB (8%)

View distance (10 chunks)256 MB (5%)

Subtotal (before version adjustment)4964 MB

After version-era multiplier (×1.1)5460 MB

Suggested JVM flags (Paper)

java -Xms8G -Xmx8G -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:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -jar server.jar nogui

-Xms8G — initial heap (match -Xmx on dedicated servers to avoid resize pauses)

-Xmx8G — maximum heap (leave 1–2 GB for OS + other processes on the VPS)

G1GC flags tuned for Minecraft server workloads (Aikar flags). Paper and Purpur benefit most; adjust for modded if you hit Metaspace limits.

Typical hosting tiers for this config

Tier	RAM	Fits your config?
2 GB plan	2048 MB	✗ Too small for this config
4 GB plan	4096 MB	✗ Too small for this config
6 GB plan	6144 MB	△ Minimum — may lag under load
8 GB plan	8192 MB	✓ Comfortable headroom
12 GB plan	12288 MB	✓ Comfortable headroom
16 GB plan	16384 MB	✓ Comfortable headroom
24 GB plan	24576 MB	✓ Comfortable headroom
32 GB plan	32768 MB	✓ Comfortable headroom

What actually consumes RAM on a Minecraft server

The server jar itself is only a few hundred megabytes on disk — but once running, the JVM heap holds far more. Understanding where memory goes helps you right-size hosting instead of guessing "4 GB should be enough."

Loaded chunks

Each loaded chunk stores block IDs, block states, lighting arrays, biomes, heightmaps, and entity lists. Since 1.18, chunks span 384 blocks vertically (24 sub-chunks), roughly 50% taller than pre-1.18 worlds. View distance multiplies chunk count per player: at distance 10, each player keeps roughly 441 chunks loaded (21×21). Ten players exploring different areas can mean thousands of simultaneous chunks in memory.

Entities and tile entities

Every mob, item, minecart, armor stand, and dropped item is an entity object in the heap. Mob farms, item sorters, and villager trading halls are the silent RAM killers on SMP servers — a single loaded chunk with 200 items on the ground costs more than an empty chunk. Paper's entity-per-chunk-save-limit and hopper optimisations help, but they do not eliminate the cost.

Plugins and their caches

Every plugin loads classes into Metaspace and often maintains in-memory caches: economy balances, permission nodes, region data (WorldGuard), player statistics, quest progress, and more. A server with 40 plugins can easily add 500 MB–1 GB beyond what vanilla would use. Plugins that scan the entire world on startup (Dynmap pre-rendering, CoreProtect indexing) cause temporary RAM spikes that can trigger OOM kills if headroom is tight.

Mods and modpack overhead

Forge and Fabric modpacks load thousands of block types, custom entities, and worldgen structures into memory at startup. A 200-mod Forge pack can consume 3–4 GB before a single player joins. Metaspace (where Java stores class metadata) is separate from the heap and is not capped by -Xmx — modded servers hitting "Metaspace" errors need -XX:MaxMetaspaceSize tuning in addition to heap sizing.

Typical RAM requirements by server type

Server type	Players	Software	Typical RAM
Vanilla with friends	2–5	Vanilla / Paper	2–3 GB
Small SMP	10–20	Paper + 15–25 plugins	4–6 GB
Medium SMP / Towny	30–50	Paper + 30–50 plugins	8–12 GB
Minigame network hub	50–100	Paper + proxy	12–16 GB per backend
Skyblock / OneBlock	20–40	Paper + multi-world	6–10 GB
Light modpack	5–10	Fabric / Forge ~80 mods	6–8 GB
Heavy modpack (ATM, FTB)	5–15	Forge 200+ mods	10–16 GB
Bedrock Dedicated Server	5–20	BDS	1–3 GB

These are starting points. Use the calculator above with your exact plugin list and world folder size for a tighter estimate.

How to reduce RAM usage without upgrading hosting

Lower view distance

Dropping from 12 to 8 in server.properties is the single biggest RAM win. On Paper, set simulation-distance separately so mob farms still work.

Pre-generate your world

Use Chunky or WorldBorder fill to pre-generate terrain. Random exploration forces chunk generation on demand, which spikes both CPU and RAM simultaneously.

Audit your plugins

Run /plugins and remove anything unused. Plugins like Dynmap, CoreProtect with large databases, and multi-world managers are common RAM hogs.

Limit entity counts

Paper's paper-world-defaults.yml lets you cap mobs per chunk, disable phantom spawning, and reduce item despawn timers — all of which lower live entity count in memory.

Use Paper or Purpur, not Spigot

Paper includes hundreds of optimisations over Spigot for the same workload. Purpur adds more tunables. Both are drop-in replacements — swap the jar and keep your plugins.

Restart on a schedule

Memory leaks in plugins accumulate over days. A daily restart via cron or a plugin like AutoRestart clears leaked objects. Pair with Spark profiling to find the worst offenders.

Understanding -Xms, -Xmx, and Aikar flags

The calculator generates a full startup command using the Aikar G1GC flags — the de facto standard for Minecraft servers since 2019. Here is what the important parts mean:

Flag	Purpose
-Xms6G	Initial heap size — JVM allocates this at startup
-Xmx8G	Maximum heap — hard cap; server crashes with OOM if exceeded
-XX:+UseG1GC	Use G1 garbage collector — best for large heaps and low pause times
-XX:MaxGCPauseMillis=200	Target max GC pause — keeps tick lag from garbage collection under 200 ms
-XX:+AlwaysPreTouch	Pre-fault heap pages at startup — avoids pause on first access
-XX:G1HeapRegionSize=8M	Region size for G1 — 8M is optimal for Minecraft heaps 4G+

Always leave headroom on the VPS beyond -Xmx. If your VPS has 8 GB total, do not set -Xmx8G — the OS, SSH, and any monitoring agent need breathing room. A safe rule: heap = VPS RAM − 1.5 GB when Minecraft is the only major process.

Frequently asked questions

How much RAM for 10 players?

A Paper SMP with 10 players, 15–20 plugins, view distance 10, and a medium world needs 4 GB minimum, 6 GB recommended. Vanilla with the same player count can run on 2–3 GB if the world is small and view distance is 8.

How much RAM for 50 players?

Plan for 8–12 GB on a single Paper backend with moderate plugins. Networks splitting players across multiple backend servers (via Velocity/BungeeCord) can use 6–8 GB per backend with 15–25 players each instead of one monolithic 16 GB machine.

Does Minecraft 1.21 need more RAM than 1.16?

Yes, roughly 10–15% more for the same configuration. Taller worlds (384 vs 256 blocks), denser cave generation, richer block state palettes, and more complex entity behaviour all increase per-chunk memory. The calculator applies a version-era multiplier automatically.

Why does Task Manager show more RAM than I allocated?

-Xmx caps only the Java heap. Metaspace, thread stacks, Netty direct buffers, and JNI native memory sit outside the heap. A server with -Xmx6G often shows 7–8 GB RSS in the process list — that is expected, not a leak.

Can I run a server on shared hosting with 1 GB?

Realistically, no — not for Java Edition with plugins. Some budget hosts sell 1 GB plans, but they either enforce strict player caps (1–2), throttle CPU so aggressively that TPS drops below 15, or crash during chunk generation. Bedrock Dedicated Server is the exception — it can run on 1 GB for a handful of players.

Where can I find servers to compare hosting needs?

Browse active servers on the Minecraft server list to see what player counts and gamemodes successful servers run. Check Minecraft service status if connection issues are unrelated to your RAM sizing.