How much RAM for a Minecraft server do you actually need?
If you are asking how much RAM for a Minecraft server is enough, the honest answer is less than most people buy for vanilla, and more than they expect for modpacks. A small group of friends on vanilla or Paper Java runs well with a 2–4 GB heap. A plugin server for 20–30 players wants 4–6 GB. Modpacks are where memory goes: a light Fabric or Forge pack needs around 6 GB, and a heavy pack with a few hundred mods can need 8–12 GB. Bedrock Dedicated Server is not Java, so it is sized differently.
Whatever the figure, the machine needs more than the heap. Java and the operating system need room outside -Xmx, so leave 1–1.5 GB spare at minimum.
Quick checklist
- Decide Java or Bedrock first. Java needs a JVM and a heap size; Bedrock does not.
- Count real concurrent players, not the
max-playersslot count. - Check the modpack's own stated server requirement, then add room for players.
- Set
-Xmsand-Xmxto the same value, about 1–1.5 GB below the server's total RAM. - Run Paper (or performance mods on Fabric) rather than the vanilla jar.
- Pre-generate the world with Chunky before players arrive.
- Measure with spark before buying more RAM.
Minecraft server requirements: Java Edition vs Bedrock
Java Edition servers run on the JVM. You choose how much memory Java may use with -Xmx, and you need the right Java version for your game version: 1.20.5 onwards needs Java 21, and 26.1 onwards needs Java 25. The Minecraft Wiki's setup tutorial treats a 2 GB heap as more than enough for a home server of about five players at default settings, and notes that larger servers may need 4 GB. The standard start command looks like this:
java -Xms4G -Xmx4G -jar server.jar --nogui
Bedrock Dedicated Server (BDS) is Mojang's native server for Windows and Linux, with Ubuntu 22.04 or later the officially supported Linux. It has no heap flag; it simply uses what it needs. The wiki lists 4 GB of RAM as the minimum, with more beyond about ten players, and recommends a quad-core CPU at 3 GHz or faster. Bedrock has no Paper or Forge equivalent: add-ons built on Mojang's scripting API take the place of plugins.
What drives Minecraft server RAM
Player count and where they go
Players in one base share loaded chunks. Twenty players exploring in twenty directions load twenty separate areas, which costs far more memory and CPU than twenty in one town.
View-distance and simulation-distance
In Java server.properties, view-distance sets how many chunks are sent to each player and simulation-distance sets how far from players entities and crops are ticked. Both default to 10 and accept 3 to 32. Loaded area grows with the square of the radius, so dropping view-distance from 10 to 8 removes roughly a third of the chunks each player keeps loaded. Bedrock uses view-distance and tick-distance (4 to 12, default 4).
Plugins
Most Paper plugins are small. Dynamic web maps, logging plugins with large in-memory caches and anti-cheat are the usual exceptions.
Modpacks on Forge and Fabric
Every mod adds classes, blocks, recipes and often new world generation. Memory use climbs with mod count before anyone joins, which is why modpack authors state a minimum. Treat that number as the floor.
World pre-generation
Generating new chunks is the heaviest thing a server does. A pre-generated world saves CPU and avoids memory spikes while players explore.
A practical sizing table
These are starting points, not guarantees. Mods, farms and player behaviour vary too much for any table to be exact, so measure and adjust.
| Server type | Players | Heap (-Xmx) | Total server RAM |
|---|---|---|---|
| Vanilla or Paper, small group | 2–10 | 2–3 GB | 4 GB |
| Paper with plugins | 10–30 | 4–6 GB | 8 GB |
| Light modpack (Fabric or Forge, under about 100 mods) | 5–15 | 6 GB | 8 GB |
| Heavy modpack (200+ mods) | 10–30 | 8–12 GB | 16 GB |
| Bedrock Dedicated Server | up to 10 | not applicable | 4 GB or more |
If the same machine runs a website or database as well, add their needs using how much RAM a VPS needs.
How much RAM for a modded Minecraft server, and why more is not always better
Giving Java far more heap than it uses can make things worse. Java's garbage collector clears dead objects from the heap; a bigger heap lets more garbage pile up, and some collections then take longer. You also risk the opposite problem: if -Xmx is set to the server's full RAM, the JVM's own overhead pushes the machine out of memory and the Linux OOM killer stops the server. PaperMC's documentation advises subtracting about 1,000–1,500 MB from the available memory, for example about 6,500 MB on an 8 GB machine.
Aikar's flags for a Paper Minecraft server
Aikar's flags are a set of G1 garbage collector settings that PaperMC recommends to keep collection pauses short. They set -Xms equal to -Xmx and add options such as -XX:+UseG1GC and -XX:MaxGCPauseMillis=200. The full list is long and changes occasionally, so copy the current version from the Aikar's flags page on docs.papermc.io, or use its start script generator, rather than an old forum post. A trimmed example of the shape:
java -Xms6500M -Xmx6500M -XX:+UseG1GC -XX:+ParallelRefProcEnabled \
-XX:MaxGCPauseMillis=200 -XX:+DisableExplicitGC -XX:+AlwaysPreTouch \
-jar paper.jar --nogui
The flags page itself suggests 6–10 GB for the setup it describes. A small Paper server runs on less; the wider point is that past a certain size, extra RAM brings little.
CPU: single-thread speed matters
The game runs 20 ticks a second, and most of each tick happens on one thread. When a tick takes longer than 50 ms, TPS falls below 20 and the game lags, however much RAM is free. A few fast cores therefore beat many slow ones. Much of the lag people blame on memory is really CPU: entity farms, redstone clocks and chunk generation.
Measure with the spark profiler
Paper bundles spark from 1.21 onwards; on Fabric or Forge, install the spark mod. Useful commands:
/spark tps
/spark health
/spark gc
/spark profiler start --timeout 600
/spark health reports TPS, CPU, memory and disk use, and /spark gc shows garbage collection history. If memory sits well below the heap after collections while ticks are slow, more RAM will not help. The profiler report, returned as a link after ten minutes, shows which plugin, mod or entity is using the tick.
Minecraft server lag fix: practical steps
- Run Paper. It is a plugin-compatible replacement for the vanilla Java server with many performance fixes. For Fabric packs, performance mods do a similar job.
- Lower view-distance before simulation-distance. A view-distance of 8 and simulation-distance of 6 is a sensible start on a busy server.
- Limit entity farms. Mob and villager farms are the tick hogs spark most often reveals.
- Restart on a schedule on heavily modded servers, where memory use tends to creep up.
- Pre-generate the world with Chunky. Run it before launch, from the console:
chunky world world
chunky center 0 0
chunky radius 5000
chunky start
chunky progress
Use chunky pause and chunky continue if players need the server mid-run, and set a world border to match so nobody generates new chunks beyond it. The vanilla command takes a diameter, not a radius, so a 5,000-block radius around 0 0 is worldborder center 0 0 then worldborder set 10000.
Latency for Indian players
RAM cannot fix distance. Every block placed and every hit is a round trip, so a server in Singapore or Europe feels slow to players in India however well it is tuned. Host close to most of your players: a server in Mumbai or Delhi NCR keeps ping low in those regions, and players in the south still get a shorter route than going abroad.
Running a Minecraft server on Bigdomainhost
Bigdomainhost Minecraft hosting runs on KVM VPS in data centres in Mumbai (BOM-1) and Delhi NCR (DEL-1). The site lists typical ping of 6–14 ms in those cities and up to about 50 ms in the far south, against 55–70 ms to Singapore; check your own route with the browser latency test. The plans map onto the table above: Starter has 2 vCPU and 4 GB RAM, Survival 4 vCPU and 8 GB, Modded 8 vCPU and 16 GB, and Network 16 vCPU and 32 GB for several worlds behind a proxy.
Java and Bedrock are both supported, with Forge, Fabric, Paper, Spigot and CurseForge or Modrinth packs on full root access. The Pterodactyl panel is pre-installed on request, DDoS filtering is included, and vCPU, RAM and disk can grow in place with one reboot if you outgrow a plan. Each plan is billed in 30-day periods paid in advance. If you prefer setting up over SSH, a plain KVM VPS runs Minecraft just as well, and VDS plans with pinned physical cores suit busy servers that need steady tick times.
To have a server sized before you buy, call +91 75994 50220 during IST hours, WhatsApp the same number at any time, or email support@bigdomainhost.com.
Sources (checked )
- PaperMC Docs: Server properties
- PaperMC Docs: Aikar's flags
- PaperMC Docs: Profiling
- spark: Command usage
- Chunky: Commands