Big Minecraft modpacks: when 12 or 16 GB makes sense (2026)

Updated 4 November 2026

Most modpacks run well on 6 or 8 GB. 12 or 16 GB makes sense for the big kitchen-sink packs, such as All the Mods (ATM9, ATM10) and large Create packs, once you have more than about 10 players, a world that people explore far and wide, or many running factories at the same time. At ServerSpark, Minecraft 12 GB costs €13.79 per month paid per quarter and Minecraft 16 GB €15.79. This guide shows how to tell whether you really need that much memory, or whether CPU or world generation is the real problem.

When 12 or 16 GB is the right size

Prices include 21% VAT. The 12 GB plan has 120 GB NVMe storage and the 16 GB plan 160 GB, both with 3 backup slots, 1 extra port and Fabric, Forge or NeoForge. You can start on a lower plan and upgrade later; your world stays.

Why big packs need more memory

• Mod count. Every mod loads its own blocks, items, recipes and code at start. A pack with several hundred mods uses a few GB before a single player joins.
• Loaded chunks. Each player keeps an area around them loaded. In packs with new dimensions and structures, players spread out, so the number of loaded chunks grows with every player.
• Factories. Create contraptions, trains, AE2 and Mekanism setups and chunk loaders keep chunks and block entities active, even when their owner is offline.
• Exploration. Generating new chunks is the heaviest work a modded server does. It costs CPU and memory at the same time.

How to judge your RAM (instead of guessing)

The memory graph in the panel shows the whole Java process, which is always higher than what the world actually uses. Java also uses free memory lazily, so a server that sits near its limit is not automatically short on RAM. Look at the heap instead:

1. Install spark (in SparkPanel under Mods, search for "spark"; it exists for Fabric, Forge and NeoForge). Many big packs already include it.
2. With players online, run /spark health. It shows TPS, MSPT (milliseconds per tick), CPU and memory.
3. Run /spark gc to see the garbage collections. If memory falls back to well under your limit after each collection, you have enough RAM.
4. Signs you are really short: memory stays near the limit after collections, collections come every few seconds, the server freezes for a second at a time, or it crashes with OutOfMemoryError.

If MSPT is above 50 while memory has room to spare, more RAM will not help: the problem is CPU time, usually from world generation or one busy machine. Too much memory doesn't fix lag and can make each garbage collection take longer.

Pre-generate the world with Chunky

Pre-generating is the single biggest fix for lag in big packs. Chunky creates the world in advance, so players load ready-made chunks instead of the server generating them during play.

1. Install Chunky for your loader under Mods and restart.
2. In the console: chunky radius 3000 (a 6000 × 6000 block area around spawn), then chunky start.
3. Let it run when nobody plays, for example overnight. chunky pause and chunky continue stop and resume it.
4. Do the Nether and modded dimensions too: chunky world minecraft:the_nether before chunky start.
5. Set a world border at the same size, so players stay in the generated area.

Pre-generated chunks take disk space. A radius of 3000 in a big pack can take several GB per dimension; the 120 GB and 160 GB of NVMe on these plans leave plenty of room, also for backups.

Find the cause of lag with the spark profiler

1. When the server lags, run /spark profiler start.
2. Wait 2 to 5 minutes while the lag is happening, then run /spark profiler stop.
3. Open the link spark gives you. Expand the Server thread and follow the biggest percentages down: they point to the mod, block entity or entity type that costs the most time.
4. Only interested in the spikes? Use /spark profiler start --only-ticks-over 50.

Typical findings in big packs: one huge farm full of mobs, a Create contraption that never stops, a chunk loader in a busy area, or items piling up on the ground. Fix that one thing first. More tips are in Fix Minecraft server lag.

Settings that help on every big pack

• view-distance 8 and simulation-distance 6 in server.properties. Players still see far with client-side mods such as Distant Horizons, while the server simulates less.
• Performance mods if the pack doesn't have them yet: ModernFix and FerriteCore (less memory), and on Fabric also Lithium. Check that each one fits your loader and Minecraft version.
• Limit chunk loaders per player with the pack's own config, or FTB Chunks claims.
• Restart once a day with a schedule in SparkPanel (Schedules), for example at night.
• Back up before updating the pack. A modpack update can change or remove blocks. Make a backup under Backups first.

Set up a big modpack server

1. Order Minecraft 12 GB or 16 GB on Minecraft server hosting. Choose Germany (Falkenstein or Nuremberg) or Finland (Helsinki) as location, whichever is closest to most of your players.
2. In SparkPanel, install the pack from Modrinth under Settings → Server software → Modrinth modpack. The steps are in Make a Minecraft modpack server. A pack from CurseForge, like All the Mods? Email us the link and we set it up for free.
3. Start the server once, add Chunky and pre-generate before your players join.
4. Every player installs the same pack in the same version, for example with the Modrinth App or the CurseForge app.

Running Create? See Create mod server. Not sure about the right size for a lighter pack? See How much RAM does a Minecraft server need?

Frequently asked questions