How to Install a Minecraft Modpack on Your Server (2026)

Installing a modpack on a server is nothing like installing one in the launcher. The client pack and the server pack are different downloads, the mod list has to match exactly, and one missing library will drop every player at the connect screen. Here's the process that works every time in 2026.

1. Pick the pack and check its server support

Not every pack ships a server build. On CurseForge, look for a "Server Pack" file under the Files tab; on Modrinth, check the pack's environment tags for server support. Client-only packs (shader/resource-heavy visual packs) can't be hosted — they run entirely on your machine. If you're still deciding, our tier-ranked best modpacks of 2026 lists server RAM for each pack.

2. Size the RAM before you install

The single biggest cause of "the modpack crashed on startup" is under-allocated memory. Rough 2026 guidance:

• Light packs (under 80 mods): 4 GB
• Mid packs (80–200 mods): 6–8 GB
• Kitchen-sink packs (300+ mods, ATM10, Vault Hunters): 10–12 GB
• Add roughly 1 GB per 8 concurrent players beyond the pack baseline.

More detail in our Minecraft RAM sizing guide. On SurfNode you can start small and upgrade the RAM tier later without rebuilding the world.

3. Install through the panel (the easy route)

On a managed host with Pterodactyl, this is a two-minute job:

1. Open your server in the panel and stop it.
2. Go to Settings → Reinstall Server, choose the modpack egg (CurseForge / Modrinth / FTB).
3. Paste the pack ID or slug and the version you want.
4. Set the RAM allocation and Java version the pack requires (most 1.21 packs need Java 21).
5. Start the server and watch the console — first boot generates chunks and can take 3–5 minutes.

Every pack in this article is installable this way on SurfNode modded Minecraft hosting.

4. Manual install (if your host has no pack installer)

1. Download the server pack ZIP from CurseForge or Modrinth.
2. Upload it to the server root via SFTP and unzip in place.
3. Run the pack's installer script (or point the startup command at the Forge/NeoForge/Fabric launcher jar the pack ships).
4. Accept the EULA in eula.txt.
5. Edit the startup memory flags to match your plan's RAM.

5. Match the client to the server

Players must run the same pack version, not just the same pack. A 1.21.1 client cannot join a 1.21.4 server, and a pack updated mid-season will lock everyone out until they update too. Pin the version in your Discord and announce updates before you apply them.

6. Tune before you invite everyone

• Drop view-distance to 8 and simulation-distance to 6 for heavy packs.
• Pre-generate 3–5k blocks of world with Chunky to avoid generation lag on day one.
• Install Spark and profile the first hour — one badly behaved mod is usually responsible for most tick time.
• Turn on automatic daily backups before anyone builds anything they care about.

Full tuning walkthrough: how to reduce Minecraft server lag.

Common failures and fixes

• Instant crash, exit code 1: wrong Java version. 1.20.1 packs want Java 17, 1.21+ wants Java 21.
• Server starts then dies silently: out of memory. Move up a RAM tier.
• Clients get "mod mismatch": client and server pack versions differ.
• World won't load after a pack update: restore the pre-update backup, then update in a test instance first.

Ready to deploy

Grab a plan with enough headroom for your pack and install it in the panel: UK Minecraft hosting from £1.99/mo, US Minecraft hosting from $2.69/mo, or purpose-built modded Minecraft plans. Instant setup, no setup fees, cancel anytime.