How to Install Mods & Plugins on a Minecraft Server
A practical guide to installing Minecraft mods and plugins: plugins vs mods, the /plugins and /mods folders, version matching, and where to download safely.
Installing mods and plugins is the single biggest upgrade you can make to a Minecraft server, but the process trips up a lot of first-time owners. This guide breaks down exactly how it works, whether you run plugins on Paper or mods on Fabric, Forge, or NeoForge.
Plugins vs. Mods: Know the Difference
This is the mistake beginners make most. Plugins run on server software like Paper or Spigot and only affect the server, players join with a normal vanilla client. Mods run on a mod loader like Fabric, Forge, or NeoForge and usually require every player to install the same mods client-side. You can't mix the two: a Paper server can't load Forge mods, and a Forge server can't load Spigot plugins.
Installing Plugins (Paper / Spigot)
- Download the plugin as a
.jarfile from a trusted source (see below). - Upload it to the
/pluginsfolder on your server. - Restart the server. Plugins load on startup, they won't appear if you just drop the file in while running.
- Check the console for a load confirmation, then configure the plugin's generated config file in
/plugins/PluginName/.
Installing Mods (Fabric / Forge / NeoForge)
- Install the matching mod loader on your server first, your host should offer one-click Fabric, Forge, or NeoForge setup.
- Download each mod as a
.jarmatching your loader AND your Minecraft version. - Upload the mods to the
/modsfolder. - Install the same mods on your own client (skip any that are explicitly server-side only).
- Restart the server to load everything.
Where to Get Mods & Plugins
Stick to reputable sources to avoid malware:
- Modrinth — fast, clean, and great for Fabric/NeoForge mods.
- CurseForge — the largest catalog of mods and modpacks.
- SpigotMC / Hangar — the home of Paper and Spigot plugins.
Never download mods from random reupload sites, malicious .jar files are a real risk.
The Golden Rule: Match Your Versions
The number-one cause of crashes is a version mismatch. Every mod and plugin must match your server's Minecraft version, and every mod must match your loader. If a mod is built for 1.21 NeoForge, it will not load on a 1.20 Fabric server. When in doubt, check the file's listed compatibility before uploading.
Handling Dependencies
Many mods and plugins rely on library files that add no content on their own. On the plugin side, Vault, PlaceholderAPI, and ProtocolLib are common dependencies. On the mod side, Fabric API is required by nearly every Fabric mod, and packs like Create pull in Flywheel. If a mod's page lists "requires X," install X too, or the mod simply won't load. A missing dependency is one of the most common reasons a server fails to start.
Troubleshooting
- Server won't start after adding mods? Remove the last mod you added, one bad or mismatched file crashes everything. Read the crash log; it usually names the culprit.
- Plugin not showing up? Confirm it's in
/plugins(not/mods) and that you restarted, not just reloaded. - Client can't connect to a modded server? You're missing the mods, or your versions don't match the server's.
- Missing dependency errors in the log? Install the required library the error names, then restart.
- Random crashes only under load? Profile with a tool like spark, a single heavy mod or unoptimized config is usually the cause.
Skip the FTP Hassle
Manually downloading, uploading, and version-matching every file gets tedious fast. That's why our Minecraft server hosting includes a one-click Mods manager, browse Modrinth and CurseForge, and install mods or plugins directly from the control panel with no FTP client required. It even handles version matching for you.
Ready to build your server the easy way? Head to our game servers page and use Nxeon's one-click mod installer to get modded in minutes.