Modded Minecraft Hosting Requirements: Full Guide

Modded Minecraft Hosting Requirements: Full Guide

Quick answer: modded Minecraft servers need 3 to 10 times more resources than vanilla, depending on the pack. A 50-mod light pack runs fine on 6 GB RAM. A 200-mod kitchen-sink pack like ATM9 or Better MC wants 10 to 16 GB. Java version matters more than people realize: Minecraft 1.20.5 and newer require Java 21, older packs need Java 17 or even Java 8. Single-thread CPU performance matters more than core count. SSD storage is mandatory, not optional. The rest of this guide gets specific.

Modded Minecraft is its own beast. Hosting requirements that work for a 50-player vanilla SMP can be wildly wrong for a 5-player modded server, and the people who buy 4 GB plans for ATM9 then complain about lag are running into exactly that mistake. Here's what actually matters.

Why modded servers need so much more

Three things drive modded hardware needs higher than vanilla:

Tile entities and contraptions everywhere. Every Create pack has dozens of running contraptions. Every tech pack has hundreds of cables, machines, and item conduits ticking constantly. Each of those is work the server does every tick. A 12-player vanilla server might have 2,000 entities. A 6-player modded server commonly hits 30,000.

Custom worldgen is expensive. Mods like Biomes O' Plenty, Terralith, Tectonic, and Oh The Biomes You'll Go generate terrain that's 5 to 10x heavier than vanilla per chunk. Worldgen is single-threaded, so this directly drives CPU pressure.

Forge and NeoForge are heavier loaders. They do more work at runtime than vanilla or Fabric. Mod scanning, registry rebuilds on load, and reflective access to game classes all cost CPU and memory. This shows up most during startup, but it's also a constant background tax.

The result: a modded server that "feels fine" on 4 GB during testing will stutter and crash the first night five players build anything.

RAM by pack size

Use this as a rough guide. Modpack authors usually list a recommended RAM in the launcher description, which is the floor. Add 2 GB on top for the server, because the launcher number assumes a single-player game where the client and server share memory.

A few important rules:

• More RAM is not always better. Past 16 GB on a single Minecraft process, garbage collection pauses get worse, not better. Drop down to 12 GB if you're seeing GC spikes.
• Set Xms and Xmx to the same value. Never let the heap resize at runtime.
• Use Aikar's flags or the Pelican panel defaults. Java's default GC settings are bad for Minecraft and even worse for modded.
• If players keep crashing with "Java heap space", bump RAM up 2 GB at a time, not 4 or 6.

CPU: single-thread is king

Minecraft's main game loop is single-threaded. Every tick, the main thread updates entities, runs redstone, ticks blocks, handles player input, and dispatches network packets. If that thread is slow, the entire server is slow regardless of how many cores you have.

What this means in practice:

• A 4.5 GHz Ryzen 5 7600 outperforms a 3.0 GHz Xeon with 32 cores for Minecraft. Easily.
• More cores help a little, mostly for chunk loading and a few mod async tasks. They don't fix the main-thread bottleneck.
• Architecture matters. A 2024 CPU is meaningfully faster than a 2019 CPU at the same clock speed.
• Avoid hosts that don't disclose their CPU. "8 vCPU" tells you nothing if the underlying chip is from 2017.

For modded specifically, single-thread performance matters even more than for vanilla, because mods pile on per-tick work and that work is also single-threaded.

If a host overprovisions shared CPUs at 4x or 6x of physical (common on cheap VPS plans), your single-thread numbers will swing wildly depending on what other tenants are doing. For modded, you want dedicated or lightly-shared vCPU.

Storage: SSD is not optional

This isn't 2015. HDDs are dead for Minecraft hosting. A modded server with chunk loaders and active worldgen does enough random IO that an HDD bottlenecks you before CPU or RAM does.

What you need:

• NVMe SSD if available. SATA SSD is fine if NVMe isn't an option.
• 20-50 GB disk for a typical modded server. Worlds with custom dimensions (Aether, Twilight Forest, Mining Dimension) grow faster than vanilla.
• Backups stored on separate disks. Managed hosts handle this for you, self-hosters should set up rsync or restic.

If a host is selling HDD storage as a "budget" option for Minecraft, walk away. The math doesn't work for modded.

Java version: match it to your Minecraft version

Wrong Java version is the single most common cause of modded server crashes. Reference:

A few things to know:

• Forge for 1.12.2 absolutely requires Java 8. Newer Java versions crash on startup with weird reflection errors.
• 1.16 and older modded packs often work best on Java 8 even when Java 11 technically loads. Use Java 8 unless the pack specifies otherwise.
• 1.18 forced the jump to Java 17 and broke many older mods, which is part of why 1.16.5 still has a huge active modded community.
• NeoForge for 1.20.4+ wants Java 17. NeoForge for 1.21+ wants Java 21.

On Server Heron, the Pelican panel auto-selects the right Java version when you pick the pack egg. If you self-host, install Temurin (Adoptium) builds for the matching JDK version.

Mod loaders and what they cost you

Quick differences for resource planning:

• Forge: heaviest. Slow startup (1-3 minutes for a big pack), highest baseline RAM. Use it because that's where the big packs are.
• NeoForge: forked from Forge, slightly faster startup and modestly lower RAM. Most new packs target NeoForge.
• Fabric: lightest. Faster startup, lower baseline. Performance mods land on Fabric first.
• Quilt: a Fabric fork, similar resource profile.

If you're picking your own pack and care about server cost, Fabric saves real money on RAM and CPU compared to Forge at the same mod count. The Paper vs Vanilla vs Fabric vs Forge breakdown goes deeper on this.

Real modpack requirements

Specific recommendations for popular packs as of 2026. Numbers are server-side for 5-10 players. Add roughly 1 GB per 5 additional players.

For any pack not on this list, find it on CurseForge or FTB, read the recommended RAM in the description, and add 2 GB. That's your server target.

Performance mods to install server-side

Once your pack is running, install these on the server for free TPS:

For Fabric or Quilt:

• Lithium (game logic optimizations)
• Starlight (lighting engine rewrite)
• C2ME (concurrent chunk management)
• FerriteCore (lower memory usage)
• LazyDFU (skip slow datafixer at startup)

For Forge or NeoForge:

• Canary (Lithium port for Forge, where available for your version)
• Saturn (memory optimizations)
• FerriteCore (works on Forge too)
• AI Improvements (mob AI optimization)
• Connectivity (network optimizations)

Server-side performance mods are loader-specific and version-specific. A 1.20.1 mod will not load on 1.21. Always match to your exact Minecraft version, not just the major version.

Hosting checklist

Before you buy a plan or spin up a server:

1. Identify the exact pack and version. Don't guess at RAM.
2. Match Java to the MC version (use the table above).
3. Pick a plan with at least 1-2 GB above the pack's recommended.
4. Confirm SSD or NVMe storage. Skip HDD plans.
5. Check the host's CPU. Single-thread performance matters more than core count.
6. Pre-generate the world with Chunky after installing.
7. Install the server-side performance mods for your loader.
8. Schedule a daily restart. Modded servers leak memory over days; a daily restart resets that.

Common errors and what they mean

java.lang.OutOfMemoryError: Java heap space
Not enough RAM. Bump up 2 GB at a time.

java.lang.UnsupportedClassVersionError
Wrong Java version. The pack was compiled for a newer Java than you're running. Check the table above.

Class file has wrong version 60.0, should be 52.0
Same root cause: Java 8 trying to run Java 16+ code, or vice versa. Match Java to MC version.

Caught exception from Forge... NoClassDefFoundError
Missing dependency mod. Check the pack manifest. Often happens when a player joins with a different mod set than the server has.

Failed to write chunk data
Disk is full or the world file is corrupted. Free space first, then check for region-file corruption.

Server hangs on startup
Forge with a 200-mod pack can legitimately take 2-3 minutes to start. Wait. If it's still hanging after 5 minutes, the last loaded mod in the log is your culprit; search that mod's issue tracker.

FAQ

Can I run a modded server on 2 GB RAM?
Only if the pack is very light (under 30 mods, mostly QoL changes). Anything bigger will start fine, then crash within an hour once chunks start loading.

Why does Forge use so much more RAM than the mods I added?
Forge's class loader, registry system, and mod scanner use roughly 1-2 GB on their own, before any mod does anything. Fabric uses around 500 MB for the equivalent. Big packs are dominated by the mods themselves, but small packs show the loader overhead clearly.

Do I need a different host for modded vs vanilla?
Functionally the same, but you need a higher RAM tier. A 2 GB vanilla plan won't run a meaningful modded server. Buy the tier that matches your pack.

Will more CPU cores help?
A little. The single-thread bottleneck is still the main constraint. More cores help slightly for chunk loading and a few mods that do async work, but doubling cores won't double performance.

Why is my modded server laggy with just 3 players online?
Usually one of two things: a specific mod doing heavy per-tick work (use Spark to find it), or chunk-loaders running in chunks where no player is present. Run a Spark profile and check the flame graph.

Can I switch packs without losing my world?
Mostly no. Even small mod changes can corrupt chunks, delete items no longer registered, or break terrain. Always back up before changing the mod list, and assume data loss when switching packs entirely.

Should I host modded servers in the same region as players?
Yes, for the same reason as vanilla. Modded TPS does nothing for a player with 200ms ping. Pick a host near your community.

Bottom line

Modded hosting is harder to size than vanilla because the variance between packs is huge. A 30-mod light pack and a 250-mod kitchen-sink pack run on completely different hardware tiers, even though both are "modded Minecraft."

The rough rule: take the pack's recommended RAM, add 2 GB, pick a host with strong single-thread CPU and SSD storage, install the right Java version, add server-side performance mods. That's a working modded server.

If you want to skip the sizing question entirely, Server Heron's modded plans auto-pick the Java version, install performance mods on first boot, and let you swap packs from the panel without rebuilding the server. Pick the pack, set the RAM, done.