How Much RAM Should I Allocate to Modded Minecraft?

Too little RAM and the server crashes; too much and garbage-collection pauses cause lag spikes. Here is how much RAM for modded Minecraft server setups by pack size, plus the client side and the JVM flags that help.

Quick picks

#HostFromBest for
1 GodLike Host See site Modpacks with one-click installs and auto-updates
2 BisectHosting See site 2,300+ one-click modpacks, 21 locations
3 BloomHost $12.00/mo Heavy packs on dedicated Ryzen cores
4 PebbleHost $1.00/mo Cheap RAM for big packs (upload yourself on Budget)

Server RAM by modpack

Pack type Example Players Server RAM
Light (under 100 mods) Small Fabric packs 2–10 4–6 GB
Medium Create-focused packs 2–10 6–8 GB
Pokémon packs Pixelmon, Cobblemon packs 5–20 6–8 GB
Old, hardcore RLCraft (1.12.2) 2–10 4–6 GB
Kitchen sink All the Mods 10 2–10 8–12 GB
Big pack + community ATM10, 20+ players 20+ 12–16 GB

These are starting points. Watch the memory graph for a week and add RAM only if the server runs out.

How much RAM does a modded minecraft server need: the short answer

Start from the pack’s own recommendation (on its CurseForge page), add 1–2 GB per 10 extra players, and stop at about 12–16 GB for a single server.

JVM flags that cut lag

Use Java 21 for modern packs and the widely used Aikar flags with G1GC. Set -Xms and -Xmx to the same value, for example -Xms8G -Xmx8G, so the heap doesn’t resize mid-game. Most panels set sensible flags for you.

RAM won’t fix a slow CPU

If TPS drops while RAM sits at 60%, the bottleneck is the CPU or a laggy mod. Run /spark profiler to find it before buying more memory.

03 FAQ

Q1Can too much RAM cause lag?

Yes. A very large heap makes garbage collection pauses longer. Above about 12 to 16 GB for one server, more RAM rarely helps and can hurt.

Q2How much RAM should the client have?

For players, 6 to 8 GB allocated in the launcher covers most big packs; light packs run on 4 GB. Don't allocate more than about half of your PC's total RAM.

Q3Why does my server use all its RAM?

Java grabs memory up to the limit you set and frees it lazily, so high usage alone isn't a problem. Watch for frequent crashes or long freezes instead.