Installing a ready-made modpack is far faster than downloading mods one by one.

Check the threshold first

Mod and modpack installs unlock from the 8 GB Pro package upward. On 2 and 4 GB you can install plugins but not mods — the panel doesn't offer the mod loaders (Fabric, Quilt, Forge, NeoForge) there.

Look at the memory the pack recommends: above 8 GB it may not run smoothly at this scale — trim the mod list or pick a smaller pack.

Count the disk too: the Pro package comes with 30 GB. Before starting, the pack's total size is checked against your remaining space; without room it never begins.

Pick and install the pack

When your server runs a mod loader, the left menu section is called Mods and carries a Modpacks tab. Packs come from the Modrinth catalogue; find one and press Install Pack.

The install runs in the background: the server is stopped safely, the pack is applied, and it starts again if it was running. If another job is in progress (a backup, a restore, a software change), the install won't start — wait for it to finish.

The install resets the mods folder: packs assume a clean one, and a mixed list produces conflicts. The pack's own configuration files are unpacked over same-named files, and mods that only run on the player's side never reach the server — so the server-side list looks shorter than yours.

When the pack wants different software

Matching is strict: the server must run exactly the loader and Minecraft version the pack was written for. A Fabric pack will not install on a Quilt server, and a pack asking for 1.20.1 will not open on 1.20.4.

On a mismatch the panel states what the pack needs and offers the Adjust Software & Install button; approve it and the software is adapted first, then the pack goes on.

Two protections run during that switch. If the software type changes (Paper to Fabric, say), your world, plugins and settings move into that software's profile and come back unchanged if you switch back. If a version downgrade is needed within the same software, the world and the version-bound config and mod files are set aside under a backup name — nothing is deleted, they stay in the Files section. A manual backup before installing is still the cheapest insurance.

Your friends need the same pack

On modded servers everyone must install the same mod set and versions locally. A mismatched list throws an error on connect and the player can't get in.

The pack's name and version are shown in the panel; sharing that with the group is enough.

After installing

  • Restart the server once — the panel shows a banner reminding you.
  • The first boot can be long — large packs load a great many definitions on first start; progress shows in the console.
  • Phones can't join — the Bedrock bridge works only on the plugin family and switches itself off on a server that moves to a mod loader.
  • An empty server sleeps — with idle sleep on, 15 minutes without players sends it to sleep; if your friends arrive late, turn it off under Settings.
  • If the server got heavy — lower view distance and revisit player numbers; tech packs generate many times the work of a plain server.

Troubleshooting

If the install started but nothing came of it, check in order:

  1. Console — every step is written there; a failed install names its reason in one line.
  2. Space — on a "not enough storage" line, clear old worlds and unneeded files, then retry.
  3. Version — are the loader and version in Software exactly what the pack asks for?
  4. A pending job — a backup or a restore blocks the install.
  5. Repeated attempts — installs fired back to back are held off for a while; wait, then try again.
  6. Crash on boot — the last lines in Logs name the mod it stopped on; disable it from Mods and start again.

Common mistakes

  • Leaving hand-uploaded mods in place — the install resets the mod folder; copy your own additions aside first and put them back after.
  • Editing configuration before installing — the pack's files overwrite yours; fine-tune afterwards.
  • Upgrading the version on your own — a pack written for an older version will not start on a newer one.
  • Filling the disk to the brim — after an upload the disk may be at most 80% full; the rest is unpacking headroom.

Which one to choose

  • If everyone should join with plain Minecraft, use a plugin setup instead: nothing is installed on the player's computer.
  • The pack picks the loader — Fabric, Quilt, Forge or NeoForge is decided by the pack, not by you; to move, follow the software change steps.
  • Servers under a proxy network can't move to a mod loader; network setups run on plugin-capable software.
  • Big tech pack or a curated set — with a larger group a hand-picked set runs smoother on the same memory; the performance article shows how to measure it.

For loader choice, manual uploads, dependencies and common problems, see the full mods and modpacks guide. How much memory a modded server needs is covered on the how much RAM you need page.