Forge · NeoForge · CurseForge · Modrinth · FTBModded Minecraft Server Hosting for Forge & Modpacks
Install a modpack from CurseForge, Modrinth or FTB with the one-click installer, or upload your own Forge server files. Modded servers are hungry for CPU and memory, so every plan runs on AMD Ryzen 9 with NVMe storage, automated backups and DDoS filtering.
- One-click modpack installer: CurseForge, Modrinth and FTB
- Forge server type, or upload any server pack
- NVMe storage for fast chunk saving and world loading
- Automated backups before you update a pack
Included on every Minecraft plan
- AMD Ryzen 9 CPU nodes
- NVMe storage
- 1 Gbps uplink
- DDoS filtering at no extra cost
- Automated backups
- File manager, console and FTP access
- Switch server software from the panel
- Ticket and Discord support
Our active locations are Miami and Dallas in the United States, which suit players across North America and Latin America. Players in Europe can connect, but ping will be higher than on a server hosted in Europe.
Pick the RAM your server needs
Every plan runs on the same Minecraft Java infrastructure, so the only choice is memory. You can start small and upgrade the plan as your server grows.
Install a modpack in minutes
Choose a plan for your pack
Use the RAM table below or the recommended server RAM on the pack’s page.
Open the modpack installer
Search CurseForge, Modrinth or FTB from the panel and pick the pack and version you want.
Install and start
The installer sets up the pack’s server files. Start the server and watch the console until the world is ready.
Invite your players
Players install the same pack and version in their launcher — CurseForge app, Modrinth App, FTB App or Prism Launcher — and join your address.
How much RAM does a modpack need?
Mod count, world generation and how many players explore at once matter more than the Minecraft version. Use these as starting points:
| Pack type | Examples | Suggested RAM | Notes |
|---|---|---|---|
| Light / Vanilla+ | Under ~50 mods, quality-of-life and small tech packs | 4–6 GB | Comfortable for a small group of friends |
| Medium | 50–150 mods, themed adventure or tech packs | 6–8 GB | Add headroom if several players explore new chunks |
| Heavy / kitchen-sink | 200+ mods, All the Mods-style packs | 10 GB or more | Pre-generate the world and keep an eye on chunk loaders |
Pack authors usually publish a recommended server RAM — start there. Allocating far more memory than needed makes garbage-collection pauses longer instead of removing lag; the RAM guide and the RAM calculator explain the trade-offs. If a pack needs more than our largest plan, ask support before ordering.
Forge, NeoForge or Fabric?
Mod loaders are not interchangeable: the server and every player must use the same loader, mod list and versions.
Forge
The long-standing loader behind most classic modpacks, from 1.7.10 and 1.12.2 through 1.20.1. Choose it when your pack or mods list Forge.
NeoForge
A community fork of Forge created in 2023. Many newer packs for 1.20.2 and later target NeoForge; Forge mods and NeoForge mods are not guaranteed to load on each other’s loader, so use the pack’s own server files.
Fabric
A lightweight loader with fast updates and strong performance mods. If your pack is Fabric-based, see Fabric server hosting.
Why modded servers need strong single-core CPU
Machines, pipes, new dimensions and extra world-generation features all run on the server’s main thread. Large tech bases with thousands of block entities and fresh chunk generation are the two most common causes of modded lag.
That is why single-core speed and fast storage matter more than a large core count. Our Minecraft nodes run AMD Ryzen 9 processors and NVMe storage, which helps with both ticking and saving chunks. Install the spark mod to profile lag, and pre-generate your world with Chunky before opening the server to players.
If the server crashes on startup, paste the crash report into the log analyzer: it detects missing mod dependencies, incompatible versions and Java mismatches.
Before you launch or update a modpack
- Remove client-only mods (shader loaders, HUD and rendering mods) from the server’s mods folder — they can crash a dedicated server.
- Keep the server and every player on exactly the same pack version.
- Take a backup before updating: removed mods take their blocks, items and dimensions with them.
- Pre-generate the spawn area with Chunky to avoid exploration lag on day one.
- Match the Java version: 1.12.2 packs need Java 8, 1.18–1.20.4 need Java 17 and 1.20.5+ need Java 21 or newer.
- Check latest.log after the first start for mods that failed to load.
Move an existing modded server
Download your files
Stop the old server and download world, mods, config and, if the pack uses them, defaultconfigs, kubejs and scripts.
Install the same pack and version
Use the modpack installer or upload the pack’s server files so loader and mod versions match your world.
Restore your world and configs
Replace the fresh world with yours through the file manager or FTP, and copy over any configs you edited.
Start and check the console
Look for missing-block warnings, then share the new address. Contact support by ticket or Discord if the server does not start.
Who modded hosting is for
A modpack with friends
A persistent world your group can join any time, without keeping a PC running.
Public modpack communities
Run a popular pack for a wider audience with backups and DDoS filtering included.
Custom packs
Upload your own server pack or mods folder through the file manager or FTP.