How to install mods on your Minecraft server

To run mods, your server must use a mod loader (Fabric, Forge or NeoForge). Then you can install mods from the Mods tab in one click, or upload mod .jar files to the mods folder. Every player must install the same mods on their own game too.

Step 1: Pick the right loader

Each mod is made for one loader (sometimes more) and one Minecraft version. A Fabric mod will not load on Forge, and a 1.20.1 mod will not load on 1.21. Before you add anything, decide which loader and version your mods need, and make sure your server matches.

1. In the Game Panel, open your server and click Versions. It shows what is Currently running and the Minecraft version.

2. If you need a loader, click Fabric, Forge or NeoForge (Quilt is under Experimental), click the Minecraft version, then in the Install pop-up tick Accept EULA and click Install. Java is chosen for you.

3. Watch the Console until the install finishes, then click Start once so the server creates its mods folder.

Step 2 (easy way): Install from the Mods tab

1. Click Mods in the sidebar and stay on Browse Mods.

2. Choose a Platform: Modrinth or CurseForge.

3. Set Mod Loader to your loader (Fabric, Forge, NeoForge, Quilt…) and Version to your Minecraft version, so only matching mods show.

4. Search for the mod. Click Details to check it supports servers, then Install.

5. Restart the server and check the Console.

The Manage Mods tab shows the mods already in your mods folder, including ones you uploaded yourself.

Step 2 (manual way): Upload mod files

1. Download the server-compatible .jar from the mod's official CurseForge or Modrinth page. Pick the file for your exact loader and Minecraft version.

2. Open Files and go into the mods folder.

3. Click Upload → Upload Files and pick the .jar files (or use SFTP for many files: How to connect with SFTP).

4. Restart the server and check the Console for errors.

Don't forget dependencies

• Fabric API: almost every Fabric mod needs it. Put the Fabric API .jar (for your Minecraft version) in the mods folder on the server and on every player's game.

• Library mods: many mods also need a library mod, for example a config or API library. The mod page lists "dependencies" or "required" mods. If one is missing, the server stops and the console names it.

Remove client-only mods

Some mods only change what you see on your own screen, so they are made for the game client, not for servers. Common examples are shader and graphics mods such as OptiFine, Iris and Oculus, and many HUD, zoom, menu and minimap-only mods. On a server they do nothing at best, and often stop it from starting. A Forge or NeoForge crash that mentions invalid dist DEDICATED_SERVER is a typical sign.

To fix it, stop the server, delete the client-only mod from the mods folder and start again. Players can keep these mods on their own game. On Modrinth, a mod page shows whether it is needed on the client, the server or both.

Players need the same mods

Anyone joining a modded server needs the same loader, the same Minecraft version and the same content mods (same versions) installed in their launcher. The easiest way to share them is a modpack: see How to install a modpack. If players get a "mod rejections" or missing mods message, see Mod mismatch and missing mods errors.

Frequently asked questions

Still stuck? Open a ticket with your crash report and we'll help with the hosting side.