Calculator

Configure Your Server

All defaults match a typical 20-player Paper server. Adjust to your reality.

Server Type

Player Slots

View Distance (chunks)

Plugins / Mods Count

>> Recommended Configuration

JVM Heap (-Xmx)

6 GB

Total VPS RAM

8 GB

vCPU Cores

2 vCPU

Storage

30 GB

>> Aikar's JVM Flags (copy-paste ready)

These flags are the community standard for Paper/Spigot servers. They tune G1GC for Minecraft's allocation pattern and prevent lag spikes from garbage collection.

Loading...

Best Hostinger Plan Match

Hostinger KVM 2

2 vCPU · 8 GB RAM · 100 GB NVMe · 8 TB bandwidth

€8.49 / month

Get This Plan →

Methodology

How the Calculation Works

Minecraft Java RAM usage is driven by four factors in roughly this order of impact: loaded chunks, mod/plugin count, view distance, and player count. We model each:

heap = base_heap
     + (view_distance_mult × 0.25 GB)
     + (plugin_mult × 0.5 GB)
     + (players × per_player_overhead)

total_vps_ram = heap + 1.5 GB (OS + Java overhead)

Why we always add OS overhead: A common rookie mistake is to set -Xmx8G on an 8 GB VPS. The OS, systemd, and Java itself need about 1-2 GB outside the heap. Without that buffer, Java allocates up to 8 GB, hits the cgroup limit, and gets OOM-killed.

Why Aikar's flags? Aikar (lead dev of PaperMC) tuned G1GC specifically for Minecraft's allocation pattern. His flags reduce GC pause times from 500 ms spikes to consistent 20 ms. Source: official PaperMC documentation.

A note on -Xms: We set -Xms equal to -Xmx. For server workloads this prevents costly heap resizes and lets G1GC tune region sizes correctly from the first tick.

FAQ

Common Questions

Can I give Minecraft more RAM than it needs?

Technically yes, but it's counterproductive. A 16 GB heap has longer garbage collection pauses than an 8 GB heap because G1GC has more memory to scan. For vanilla or Paper, 6-10 GB is the sweet spot regardless of player count.

Why does the calculator recommend 8 GB VPS for a 6 GB heap?

Because the Java heap is not the only thing using memory. You also need RAM for the JVM itself (metaspace, code cache), the OS, monitoring tools, and your panel if you run one. Budget 1.5 GB of non-heap memory on top of your -Xmx.

Does view distance actually matter that much?

Yes. View distance of 10 loads a 21x21 chunk area per player (441 chunks). View distance of 16 loads 33x33 (1,089 chunks) — roughly 2.5x the RAM and CPU load. For servers above 10 players, stick to view-distance 8 or 10 and use Paper's simulation-distance setting to keep visuals long-range while reducing tick cost.

Forge vs Paper — which uses less RAM?

Paper, by a wide margin — roughly 2-3x more efficient than vanilla Forge. A 50-slot Paper server runs comfortably in 8 GB; the same slots on Forge with 40 mods realistically needs 12-16 GB. If your mods have a Fabric port, consider switching — Fabric's performance sits between Paper and Forge.

What Java version should I use?

Java 21 for Minecraft 1.20.5 and newer (required). Java 17 for 1.17 through 1.20.4. Use a modern JVM like Eclipse Temurin, Amazon Corretto, or Zulu. On Ubuntu: sudo apt install temurin-21-jre after adding the Adoptium repository.

Do these numbers apply to Minecraft Bedrock?

No. Bedrock is written in C++ and uses dramatically less RAM — roughly 1 GB for a 20-slot server. See our Bedrock dedicated server guide for Bedrock-specific sizing.

// Related Tools & Guides

Tool

Universal VPS Sizer

Same calculator, but for all 12 games we cover (Rust, ARK, CS2, FiveM, etc).

Interactive

Guide

Minecraft Java Performance Guide

Deep-dive into Paper config, spark profiling, entity clearing, and chunk pre-generation.

24 min read

Guide

Modpack Server Setup

Forge, NeoForge, and Fabric modpack installation on a Linux VPS — no panel needed.

40 min read

Review

Shockbyte Review 2026

Budget Minecraft-specific managed host with Multicraft panel and one-click modpacks.

Review

Methodology

How the Calculation Works

Minecraft Java RAM usage is driven by four factors in roughly this order of impact: loaded chunks, mod/plugin count, view distance, and player count. We model each:

heap = base_heap
     + (view_distance_mult × 0.25 GB)
     + (plugin_mult × 0.5 GB)
     + (players × per_player_overhead)

total_vps_ram = heap + 1.5 GB (OS + Java overhead)

Why we always add OS overhead: A common rookie mistake is to set -Xmx8G on an 8 GB VPS. The OS, systemd, and Java itself need ~1-2 GB outside the heap. Without that buffer, Java allocates up to 8 GB, hits the cgroup limit, and gets OOM-killed. Our "Total VPS RAM" number already accounts for this.

Why Aikar's flags? Aikar (lead dev of PaperMC) tuned G1GC specifically for Minecraft's allocation pattern — short-lived chunk objects, medium-lived entities, long-lived world data. His flags reduce GC pause times from ~500 ms spikes to consistent ~20 ms. They're the de-facto standard for any Paper/Spigot/Purpur server. Source: official PaperMC documentation.

A note on -Xms: We set -Xms equal to -Xmx. This is deliberate. For server workloads (not desktop apps), pre-allocating the full heap at startup prevents costly heap resizes later and lets G1GC tune its region sizes correctly from the first tick.

FAQ

Common Questions

Can I give Minecraft more RAM than it needs?

Technically yes, but it's counterproductive. A 16 GB heap has longer garbage collection pauses than an 8 GB heap because G1GC has more memory to scan. For vanilla or Paper, 6-10 GB is the sweet spot regardless of player count. If you need more memory for a modpack, more heap helps. If you're running vanilla with 4 friends, -Xmx12G will actually feel worse than -Xmx6G.

Why does the calculator recommend 8 GB VPS for a 6 GB heap?

Because the Java heap is not the only thing using memory. You also need RAM for: the JVM itself (metaspace, code cache), the OS (kernel, systemd, cron, SSH), any monitoring tools (netdata, htop), and your panel if you're running one (Pterodactyl, Crafty). Budget 1.5 GB of non-heap memory. An 8 GB VPS with 6 GB of Java heap leaves 2 GB for everything else — comfortable.

Does view distance actually matter that much?

Yes. View distance of 10 means every player loads a 21x21 area of chunks (441 chunks). View distance of 16 means 33x33 (1,089 chunks). Each chunk holds entities, tile entities, and block data — roughly 2.5x the RAM and 2.5x the CPU load. For any server above 10 players, we recommend view-distance 8 or 10. Set simulation-distance lower than view-distance in Paper's config to keep visuals long-range while reducing tick load.

Forge vs Paper — which uses less RAM?

Paper, by a wide margin — roughly 2-3x more efficient than vanilla Forge. Paper is based on Spigot and has years of server-side optimizations: async chunk loading, lazy entity loading, reduced tick cost. A 50-slot Paper server runs comfortably in 8 GB. The same 50 slots on Forge + 40 mods realistically needs 12-16 GB. If your mods have a Fabric port, consider switching — Fabric's performance is between Paper and Forge.

What Java version should I use?

Java 21 for Minecraft 1.20.5 and newer — required. Java 17 for 1.17–1.20.4. Use a modern JVM like Eclipse Temurin, Amazon Corretto, or Zulu — avoid Oracle JDK for commercial compliance reasons. On Ubuntu: sudo apt install temurin-21-jre after adding the Adoptium repository.

Do these numbers apply to Minecraft Bedrock?

No. Bedrock is written in C++ and uses dramatically less RAM — roughly 1 GB for a 20-slot server. See our Bedrock dedicated server guide for Bedrock-specific sizing. The per-slot cost is about one-fifth of Java.