How much RAM a Minecraft server needs
As a rule of thumb, a vanilla or Paper server for a few friends needs 2 to 4 GB, a modest mod list 4 to 6 GB, and a large modpack 8 GB or more. This is what the Minecraft server RAM calculator above returns for some common setups at the default view distance of 10.
| Setup | Recommended | Minimum to start |
|---|---|---|
| Vanilla, 5 players | 2 GB | 1 GB |
| Paper, 10 players, 10 plugins | 3 GB | 1.5 GB |
| Paper, 20 players, 30 plugins | 5 GB | 2 GB |
| Fabric, Forge or NeoForge, 5 players, 50 mods | 4 GB | 2.5 GB |
| Fabric, Forge or NeoForge, 10 players, 150 mods | 6 GB | 3.5 GB |
| Large modpack, 5 players | 10 GB | 6 GB |
| Bedrock Dedicated Server, 10 players | 4 GB | 4 GB |
How the estimate works
The model is a rule of thumb of our own. Nobody can read the right number off a formula, because worlds, plugins and mods differ too much. What it does is add up the parts that matter, in a way you can check:
- Baseline. The server itself with one player online at view distance 10.
- Players. Each extra player keeps more of the world loaded.
- View distance. The server loads a square of chunks around every player, (2 × distance + 1)² of them: 441 at a distance of 10, 169 at 6 and 1,089 at 16. The memory counted for players scales with that number.
- Plugins or mods. A flat amount each. Real ones range from tiny to huge, so read it as an average.
- Headroom. A share on top, so Java has room to clean up memory and the world has room to grow.
The total is then rounded up to a plan size hosts sell. These are the numbers behind each option:
| Server | Baseline | Each extra player | Each plugin or mod | Headroom | Where the baseline comes from |
|---|---|---|---|---|---|
| Vanilla Java Edition | 1 GB | 0.1 GB | Not counted | 20% | Minecraft Wiki: 1 GB for 1 to 4 players, 2 GB for 5 to 10, 4 GB above 10 |
| Paper or Purpur with plugins | 1 GB | 0.1 GB | 0.03 GB | 20% | Ours: the vanilla figure, because Paper runs the same game. Paper's own docs recommend 6 to 10 GB |
| Fabric, Forge or NeoForge with mods | 2 GB | 0.15 GB | 0.01 GB | 20% | Ours, set so a few hundred mods land in the 4 to 6 GB FTB quotes for most of its packs |
| Large modpack (hundreds of mods) | 6 GB | 0.5 GB | Not counted | 20% | All the Mods: at least 6 GB for a server. GregTech: New Horizons: 6 GB plus 0.5 GB per extra player in the early game |
| Bedrock Dedicated Server | 4 GB, covers 10 players | 0.1 GB | Not counted | None | Minecraft Wiki: 4 GB minimum, possibly more above 10 players |
The per-player, per-plugin and per-mod amounts and the headroom are ours, except the large modpack's 0.5 GB per player, which is the GregTech: New Horizons figure for the early game (that wiki asks for 1 GB per extra player later on). The baselines lean on published figures, checked as of October 2026: the Minecraft Wiki's server requirements, which assume default settings and a view distance no higher than 10; the Paper documentation; the All the Mods server guide; the GregTech: New Horizons wiki; and the FTB server guide, which says most FTB packs recommend at least 4 to 6 GB.
Bedrock Dedicated Server is handled differently. The 4 GB is a figure for the whole machine, so no headroom goes on top. View distance is left
out because the Bedrock setting works differently: view-distance is only a cap (32 by default), and how far the world keeps
running around players is set by tick-distance (4 by default), according to
Microsoft's reference.
How to use the result on a real server
- Pick a plan at or above the recommended size. The minimum is a floor, not a target: the server starts, then stutters once the world is busy.
- On a Java server, set the heap below the plan size. The
-Xmsand-Xmxflags set how much memory Java may use for the game. Paper's documentation says to keep the two equal and not to hand Java everything your host gives you: its example is 6500 MB on an 8 GB plan. If your host's panel sets the memory for you, leave it alone. Otherwise the start script generator builds the command. - On Bedrock, there is nothing to set. Bedrock Dedicated Server is not a Java program and has no memory flag.
- Judge by how it runs. If the server crashes with
java.lang.OutOfMemoryError, or freezes for seconds at a time as more people join, go up a size. If it stays smooth with everyone online, you have enough.
New to this? The setup guides walk through creating a server step by step, and the other tools cover the files you will edit along the way.
Common mistakes
- Buying RAM to fix lag. If the game runs slowly while memory is not full, the processor is the limit. The Minecraft Wiki asks for a CPU with good single-core performance, and Paper's documentation says more memory does not mean better performance above a certain point.
- Counting everyone who has ever joined. Only players who are online keep chunks loaded. A server with 40 members and 6 online at its busiest is a 6-player server.
- Raising view distance without paying for it. A distance of 16 loads about two and a half times as many chunks per player as 10. If memory is tight, lower it first: it is one line in the file the server.properties generator writes.
- Treating every plugin or mod as equal. One that keeps a lot of data in memory can outweigh many small ones. If your result sits right on the edge of a plan size, take the next one up.
- Ignoring the pack author. For a published modpack, the figure on the pack's own page beats any calculator, including this one.
Sources
The data and rules in this tool were last checked on against:
- Minecraft Wiki: Server requirements (Java Edition)
- Minecraft Wiki: Setting up a Java Edition server
- Minecraft Wiki: server.properties
- Minecraft Wiki: Bedrock Dedicated Server
- Microsoft Learn: Bedrock Dedicated Server properties
- PaperMC docs: Getting started
- PaperMC docs: Aikar's flags
- All the Mods guides: Server setup
- GT New Horizons wiki: Server setup
- FTB docs: Create your own server
- FTB StoneBlock 4: requirements