How Much RAM Does Your Modded Minecraft Server Need?

Most modded Minecraft crashes and "won't start" errors aren't corrupted files. They're RAM. Light packs run on 4-6 GB, mid-size packs need 6-8 GB, and heavy packs with 300+ mods need 8-12 GB. If your server won't boot or dies within minutes of loading chunks, check your pack's mod count against these numbers before touching anything else.

Symptoms

• Server never finishes booting, stays "Offline" after Start
• Console shows the server hitting a memory ceiling before crashing
• Players get rolled back in position/inventory every few minutes
• Memory usage sits near 100% of the plan limit even with few players online
• Player Manager or a specific mod fails to load and RAM climbs fast afterward

Why this happens

Modpacks load hundreds of mod classes, block/item registries, and world generation logic into memory at startup, before a single player even joins. A pack advertised as needing "4 GB minimum" can actually peak higher once you add players and loaded chunks. Support has seen packs with 349 mods need 8-10 GB, and packs with 379+ mods push past that. Separately, a high Server Properties view distance (32 is a common default some players crank up) forces the server to fully load and tick thousands of extra chunks per player. This alone will spike RAM to the plan limit and crash the server, even on plans with plenty of headroom.

How to fix it

1. Check the modpack's listed RAM requirement (CurseForge/Modrinth pages usually state minimum and recommended). Treat "minimum" as a floor, not a target.
2. Open Server Properties and set view-distance and simulation-distance to 10-18 (12 is a safe default). Never leave these at 32.
3. Watch the live memory counter at the top of the server page after a restart: if it's near the limit with few players online, you need more RAM, not more optimization.
4. If you're unsure of the right size, temporarily raise RAM, restart, and check peak usage in the top-bar counters during normal play: this tells you the real number for your pack.
5. Confirm you're on one mod loader only. Check Server Type: mixing Fabric and Forge mods causes crashes independent of RAM.
6. Once you know your number, upgrade RAM from your billing/plan settings, then hit Restart to apply it.
7. Add a daily restart via Schedules to clear accumulated memory and chunk cache: this reduces crash frequency even on a correctly-sized plan.

If you're running a pack with 300+ mods, don't guess, undersized RAM on heavy packs causes crashes that look identical to mod conflicts. Rule out RAM first.

Still stuck?

If you've right-sized RAM and lowered view distance but the server still won't start, check the Console for the actual error and read our crash log guide. Dependency errors after a modpack install are covered in Fix "Missing Dependency" and Mod Conflict Errors. For install steps themselves, see How to Install a Modpack with the 1-Click Installer or How to Upload and Install a Custom Modpack. If none of that resolves it, open a ticket with your mod list and Console output, support can confirm the real RAM ceiling your pack needs.