RAM Requirements for NeoForge 1.21 Modpacks

NeoForge 1.21 and Memory

NeoForge is the community fork of Forge that has become the primary modding platform for Minecraft 1.21 and beyond. Many mod developers have migrated their projects to NeoForge, and new modpacks are increasingly built on this loader. Understanding the ram requirements NeoForge modpacks need helps you provision your server correctly from day one.

NeoForge 1.21 carries a slightly different memory profile compared to legacy Forge. The loader itself is more modular, but the mods it loads still dominate memory usage. Minecraft 1.21 introduced new data pack features and expanded the block registry, which adds baseline overhead regardless of mods installed.

Baseline and Scaling

A bare NeoForge 1.21 server with no mods uses approximately 1.8 GB of heap memory after world generation. Each mod adds variable amounts depending on its complexity. Here are the ram requirements NeoForge modpacks carry by tier:

These figures assume 5 to 10 players. Scale up by roughly 1 GB per additional 10 players. Use our RAM calculator for a personalized recommendation.

NeoForge vs. Legacy Forge Memory

In our testing, the ram requirements NeoForge modpacks show are comparable to Forge for equivalent mod counts. NeoForge's internal refactoring did not significantly change the memory footprint of loaded mods. The biggest variable remains the mods themselves, not the loader. A Create-based pack uses similar RAM on NeoForge 1.21 as it did on Forge 1.20.1, assuming the mod versions are feature-equivalent.

One difference is Java version. NeoForge 1.21 requires Java 21, which has better memory management and garbage collection options than Java 17. This means you can sometimes get away with slightly less RAM or at least experience fewer GC pauses at the same allocation.

Tuning for NeoForge 1.21

Java 21 unlocks Generational ZGC, which is excellent for servers allocating 10 GB or more. The ram requirements NeoForge modpacks impose stay the same, but the GC behavior improves dramatically with ZGC on large heaps. For servers under 10 GB, G1GC with Aikar flags remains the safe default.

• Always set -Xms equal to -Xmx to avoid heap resizing.
• For 12 GB+, try -XX:+UseZGC -XX:+ZGenerational for sub-millisecond pauses.
• Monitor with Spark after the first play session to verify your allocation is correct.
• If heap usage consistently stays below 60% of your allocation, you can safely reduce it.

Common Allocation Mistakes

Blindly copying ram requirements NeoForge modpacks from other versions can lead to over or under-provisioning. A pack that needed 8 GB on 1.20.1 Forge may need slightly more on NeoForge 1.21 due to expanded registries, or slightly less thanks to Java 21 memory optimizations. Always verify with real-world profiling using Spark after at least 30 minutes of gameplay with your expected player count.

Avoid setting the heap above what your host can actually provide without swapping to disk. Swapping is far worse than having a slightly undersized heap because disk-backed memory adds latency measured in milliseconds rather than nanoseconds.

For the complete flag reference, see our JVM flags guide. If you are migrating a pack from Forge 1.20.1 to NeoForge 1.21, our Forge-to-Fabric guide covers cross-loader migration concepts that also apply to NeoForge transitions.

Try our server: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.