How to Install Forge Mods on a Minecraft Server — Step by Step

Forge vs Fabric vs Paper — Quick Recap

Before you start installing mods, make sure you're using the right server software. These three are the most common, and they're not interchangeable:

• Forge — The original mod loader. Most large content mods (Tinkers' Construct, Create, Applied Energistics) are built for Forge. If the modpack you want runs on Forge, your server needs Forge.
• Fabric — A lightweight alternative to Forge. Faster to update after new Minecraft versions, popular for performance mods and some content mods. Fabric mods do not work with Forge and vice versa.
• Paper/Spigot — These run plugins, not mods. Plugins are server-side only (players don't need to install anything). If you want mods that change gameplay, textures, or add new items, you need Forge or Fabric — not Paper.

For a broader overview of modpacks and mod loaders, see our Minecraft modpacks installation guide.

Prerequisites

Before installing anything, confirm these two things:

1. Forge version must match on client and server. If your client is running Forge 1.20.1-47.2.0, your server needs the exact same Forge version for 1.20.1. Even minor version differences can cause connection failures.
2. Enough RAM allocated. Forge modded servers are RAM-hungry. A lightly modded server (10-20 mods) needs at least 4 GB. Heavy modpacks like All The Mods or RLCraft need 6-10 GB. Check your server plan before loading dozens of mods.

Step 1: Download the Forge Server Installer

Go to the official Forge downloads page and select the Minecraft version you want. Download the Installer (not the MDK or the universal JAR). The file will be named something like forge-1.20.1-47.2.0-installer.jar.

Always download Forge from the official site. Third-party mirrors sometimes bundle adware or outdated versions.

Step 2: Run the Installer to Generate Server Files

If you're setting up from scratch on a VPS or local machine, run the installer with the --installServer flag:

java -jar forge-1.20.1-47.2.0-installer.jar --installServer

This creates a libraries/ folder, a launch script, and downloads the necessary Minecraft server files. Accept the EULA by editing eula.txt and changing eula=false to eula=true.

If you're using a managed hosting provider like kranky.io, you can skip this step — Forge is available as a one-click server type during setup.

Step 3: Upload Mod JARs to the mods/ Folder

This is the core step. Download the mod .jar files you want from CurseForge or Modrinth. Make sure each mod is compatible with your exact Minecraft and Forge version.

Upload the .jar files to the mods/ directory in your server root. On kranky.io, you can drag and drop files directly using the built-in file manager in your dashboard — no FTP client required.

Important: Only place mod JARs in the mods/ folder. Don't put them in plugins/, libraries/, or the server root. Forge only scans the mods/ directory.

Step 4: Ensure Clients Have Matching Mods

Unlike plugins, Forge mods typically need to be installed on boththe server and each player's client. There are exceptions — some mods are server-side only (like performance or admin mods) and some are client-side only (like shaders or minimaps). The mod's documentation will specify which side it requires.

The easiest way to keep everyone in sync is to use a modpack launcher like CurseForge App, Prism Launcher, or ATLauncher. Create or select a modpack with the same mods as your server, and share it with your players.

If a player tries to connect with different mods than the server, Forge will show a "Mod Rejection" screen listing exactly which mods are missing or mismatched. This is actually helpful — it tells you exactly what to fix.

Step 5: Start the Server and Verify

Start your server using the Forge launch script (usually run.sh or run.bat, or through your hosting panel). The first launch with mods will take longer than normal as Forge loads and initializes each mod.

Watch the console for errors. A successful boot will show each mod being loaded and end with a "Done" message with the time it took. If a mod fails, the console will usually tell you which mod caused the problem and why.

Once the server is running, connect with your client using the same Forge version and mods. If everything works, you should see the modded content in-game immediately.

Common Issues and Fixes

Version Mismatch

The most common problem. If a mod was built for Forge 1.20.1 and you're running Forge 1.20.4, it will either crash or silently fail. Always check the mod's supported versions on CurseForge or Modrinth before downloading. The Forge version, Minecraft version, and mod version all need to align.

Mod Conflicts

Some mods modify the same game mechanics and conflict with each other. This usually shows up as a crash on startup with a stack trace mentioning both mods. The fix is to remove one of the conflicting mods, or check if there's a compatibility patch available. A binary search approach works well: remove half your mods, test, and narrow down which mod causes the crash.

Not Enough RAM

If your server crashes with an OutOfMemoryError or becomes unresponsive during startup, you need more RAM. Each content mod adds memory overhead — a server with 50+ mods can easily need 6-8 GB. Increase your server's RAM allocation through your hosting panel or by editing the -Xmx flag in your launch script.

Missing Dependencies

Many mods require "library" mods to function. For example, many mods depend on GeckoLib, Architectury, or Balm. If a mod needs a dependency you don't have, Forge will tell you on startup with a message like "Missing or unsupported mandatory dependencies." Install the required library mods and restart.

Config Tweaks

After mods load for the first time, they create config files in the config/directory. You can edit these to adjust mob spawn rates, recipe changes, difficulty settings, and other mod-specific options. Some mods also support in-game config editors — check the mod's documentation.