The best modpack server hosting isn't just "regular" Minecraft hosting with a bigger number on the box. A modded pack loads the server differently: it needs lots of real RAM, a fast single CPU core and a quick disk for world generation. Below we break down exactly what matters, how much RAM popular packs ask for, and which plan to pick so ATM10 or Create don't turn into a slideshow.
Why modpacks are heavier than a vanilla server
A vanilla Paper server happily holds a dozen players on 4 GB. A pack with 300-500 mods is a completely different story. Every mod adds blocks, items, mobs, structure generation, recipes and background calculations. All of that has to live in memory and get recalculated every tick. The server still has to keep up 20 ticks per second (TPS), meaning a single tick must finish in under 50 ms (that's your MSPT - milliseconds per tick). Once MSPT creeps past 50, TPS drops below 20, and players feel it as lag, rubber-banding and mobs that stutter behind.
Modded load has three main resource hogs:
- RAM. Hundreds of mods keep their data, world entities and caches in memory. You simply need more of it, otherwise the JVM chokes on garbage collection.
- A single CPU core. Minecraft's main game thread is single-threaded. Create contraptions, Mekanism pipelines, mob crowds and AE2 automation are all calculated on one core. What matters here isn't core count but clock speed and IPC.
- The disk. Modded world generation is heavy: new biomes, ores, structures. When a player flies off into unexplored chunks, the server writes and reads from disk in bursts. A slow drive tanks TPS in exactly that moment.
"I'll grab a plan with 16 cores and it'll fly." It won't. Minecraft can't spread a single game tick across 16 cores. A server with one fast 5 GHz core will outrun a machine with a heap of slow ones. Want to go deeper? Read up on why your server lags and how to fix it.
What matters in the best modpack server hosting
When you're choosing modpack hosting, look past the marketing buzzwords and focus on the concrete stuff. Here's a checklist of what actually moves your TPS.
1. Real DDR5 memory with no overselling
"8 GB" on a plan should mean eight gigabytes that belong to you alone. Plenty of cheap hosts oversell their RAM: they sell more memory on a physical server than it has, and at peak hours your world competes for it with the neighbors. On Elysium the memory is real DDR5 with no overselling - guaranteed yours. That's critical specifically for mods, where a RAM shortage instantly turns into freeze-up garbage-collection pauses.
2. A strong single core (Ryzen 9, 5.0+ GHz boost)
We'll say it again because it's the single biggest factor: a modded server needs high single-thread performance. We run AMD Ryzen 9 chips boosting to 5.0+ GHz - these are exactly the CPUs that give the best game tick in Minecraft. One of these handles a heavy pack more confidently than a "server" CPU with a swarm of 2.5 GHz cores.
3. NVMe Gen4 for world generation and saves
NVMe Gen4 drives with read speeds around 7 GB/s put the chunk-loading and world-saving question to rest. When players scatter across the map and the server generates new areas, a fast drive keeps TPS from dipping. On a plain SATA SSD or network storage, that moment is often the exact source of micro-lag in modpacks.
4. One-click modpack install
Deploying a pack by hand is a niche hobby: download the pack, match the Forge/NeoForge version, install the right Java, drop files over SFTP. In the Pterodactyl panel on Elysium it comes down to picking a pack from CurseForge or FTB and clicking one button - the loader and Java pull themselves in. If you want to understand the whole process, there's a step-by-step guide on how to install a modpack.
5. Auto-backups and sane support
A modded world is hours and days of progress: bases, factories, leveling. A mod crash or a botched update can kill your save. So you need automatic backups (on Elysium they're free and run on a schedule) and live support that helps when a pack won't start. For us that's 24/7 on Telegram and Discord. How to roll back to a working version is covered in the guide on server backups and rollback.
How much RAM popular packs need
The most common question: "how much memory should I get?" There's no universal number - it all depends on the pack's weight and the player count. The ballparks below come from real-world practice and the packs' official requirements. A deep dive with formulas is in the article on how much RAM your server needs.
| Pack / type | Loader | Comfortable RAM (up to ~5 players) | For a group (8-15) |
|---|---|---|---|
| Create packs (machinery) | Forge / Fabric | 6-8 GB | 8-10 GB |
| Better MC (adventure) | Fabric / NeoForge | 8-10 GB | 10-12 GB |
| Mid-weight Forge/NeoForge pack | Forge / NeoForge | 8-10 GB | 10-12 GB |
| All the Mods 10 (ATM10) | NeoForge | 10-12 GB | 12-16 GB |
Handing the JVM 24-32 GB for a single world is almost always harmful. The bigger the heap, the longer the garbage-collection pauses, and one such pause feels like a sharp lag spike. For the vast majority of packs, the common-sense ceiling is 16 GB. And to make those gigabytes run smoothly, the right JVM tuning helps: a breakdown of Aikar's flags and optimization.
Which loader your pack uses
By 2026 the lay of the land looks like this: NeoForge has become the standard for 1.20.5+ and 1.21+ - ATM10, Better MC 5 and nearly every new pack are built on it. Forge stays around for older packs, and Fabric is the pick for light, optimized and technical packs. Elysium supports all three plus Vanilla, Paper, Purpur, Spigot and the BungeeCord/Velocity proxies, so your pack choice won't box you in. If you're deciding what to build your project on, take a look at the comparison: Forge or Fabric.
Don't forget the Java version
Modern packs on 1.20.5+ and 1.21 require Java 21 - on old Java 17 they simply won't start. Older packs (1.16-1.18), on the other hand, run on Java 8 or 17. This is a common cause of "the server won't launch" for newcomers. On Elysium the right Java version is selected for the pack automatically during the one-click install, so you won't have to match anything by hand.
How to tell your server is short on resources
Before upgrading your plan, it's worth confirming the bottleneck is really the hardware and not a buggy mod. A few simple checks right in-game and in the console:
- The
/tpscommand (or the Spark profiler, if it's installed) shows your current TPS. A steady 20 means all's well. Dips to 15 and below are a sign the server isn't keeping up. - The garbage-collection log. Lines like
Can't keep up! Is the server overloaded?in the console almost always mean a RAM shortage or a weak core under the current load. - Behavior under players. If everything's smooth solo but lag kicks in with friends, the bottleneck is usually the single CPU core and memory - and that's where a higher plan helps.
If TPS drops even with no players and the mods aren't to blame, it's almost certainly time to add memory or move to a host with a faster core. A detailed breakdown of the symptoms is in the guide on why your server lags and how to fix it.
Elysium plans for modpacks
Now to the practical side: which plan for which pack. The lineup is ordered by memory, and for mods the higher tiers matter - that's where you get both the RAM and the headroom under load.
| Plan | RAM | Good for |
|---|---|---|
| Common | 4 GB | Vanilla, Paper, light plugins. Too little for mods. |
| Pulse | 6 GB | Light Fabric packs, small Create packs for a couple of friends. |
| Nexus | 8 GB | A starting point for mid-weight Forge/NeoForge packs and a smaller group. |
| Apex | 12 GB | Heavy packs and ATM10 for a small group. |
| Titan | 16 GB | ATM10 and big packs for 10+ players, lots of machinery. |
| Vector / Eclipse | 20-32 GB | Large modded projects, server networks behind a proxy. |
In short: Nexus (8 GB) is a sensible entry point into modpacks - mid-weight packs will run on it. Apex (12 GB) is the sweet spot for heavy packs like ATM10 with a group of friends. Reach for Titan (16 GB) when you've got lots of players, dozens of active machines in the world and a huge area loading in. Prices start from €4.99/mo (the site switches between ₽/€/$), and it's easy to compare tiers on the plans page.
You can spin the server up in Moscow, Frankfurt, Amsterdam or Helsinki - pick the location closest to your players for the lowest ping. Every site sits behind L3-L7 DDoS protection. The list and ping figures are on the locations page.
General criteria for choosing a host
Beyond the "hardware" for mods, there are baseline things that matter for any server: uptime, DDoS protection, a convenient panel, SFTP and database access, transparent pricing, and the ability to upgrade without a reinstall. We've gathered them in a separate piece - if you're choosing a host from scratch, read the guide on how to choose Minecraft hosting, where all the pitfalls are laid out.
A word on migration. If you already have a modded server on another host, you don't have to set it up from scratch. On Vector and higher the migration is free: we move your world, mods, plugins and configs, then stay on hand for 48 hours until everything runs stably. Details are on the free migration page.
In short: how to build a modded server in a couple of minutes
Follow the simple route: gauge the pack's weight and your player count → pick a plan from the table above (for mods that's usually Nexus, Apex or Titan) → in the configurator choose the core/loader and the modpack from CurseForge or FTB → pick the nearest location. The install runs in one click, backups turn on automatically, and support stays on call 24/7.