How to Install Plugins on a Minecraft Server (Spigot, Paper, Purpur)

Installing a plugin is a two-minute job when everything matches — and a two-hour debugging session when the versions don't. This is the complete procedure for Spigot, Paper and Purpur, plus the troubleshooting section you'll want bookmarked for the day a plugin refuses to load.

//Before you start: two requirements

• ▪A plugin-capable server. Plugins do not work on a vanilla server .jar or on Forge/Fabric. You need Spigot, Paper or Purpur (if you're unsure of the difference, see plugin vs mod vs datapack). Paper is the usual recommendation: best performance, biggest ecosystem.
• ▪A plugin built for your Minecraft version. A plugin compiled against the 1.21 API can crash on a 1.16 server and vice versa. Check the supported versions where you downloaded it — or, if you generate the plugin yourself, pin the version at creation time.

//The installation, step by step

1. Get the .jar file. From SpigotMC, Modrinth, Hangar, a developer, or an AI generator like Voxen. If it comes in a .zip, extract it — the server wants the .jar itself.
2. Stop the server. Hot-dropping files works with some plugins and corrupts state with others; a clean stop costs you one minute and zero surprises.
3. Copy the .jar into the plugins/ folder in your server root (next to server.properties). On a hosting panel, use its file manager or SFTP — same folder.
4. Start the server and watch the console for the plugin's enable message.
5. Verify with /plugins in-game or in the console: your plugin should be listed in green. Red means it loaded with errors — see below.
6. Configure and reload. Most plugins generate plugins/<Name>/config.yml on first start. Edit it, then restart. (Prefer restarts over /reload — the reload command is a well-known source of ghost bugs.)

A healthy startup looks like this:

[Server thread/INFO]: [CrateMaster] Loading CrateMaster v1.0.0
[Server thread/INFO]: [CrateMaster] Enabling CrateMaster v1.0.0
[Server thread/INFO]: [CrateMaster] Loaded 4 crates from config.
[Server thread/INFO]: Done (3.812s)! For help, type "help"

//Troubleshooting: the four classic failures

1. "Unsupported API version"

The plugin targets a newer Minecraft than your server runs (e.g. api-version: 1.21 on a 1.20 server). Fix: get a build for your version, update your server, or regenerate the plugin targeting your actual version.

2. UnsupportedClassVersionError

That's Java, not Minecraft: the plugin was compiled with a newer JDK than your server uses. Modern Minecraft (1.20.5+) wants Java 21; if your host lets you pick the Java version, pick the newest.

3. Plugin is red in /plugins, or missing entirely

• ▪Read the console from the first error line, not the last — the root cause is at the top of the stack trace.
• ▪Missing dependency? Some plugins require another plugin (Vault, ProtocolLib…). Install the dependency first.
• ▪Still in a .zip, or double-named plugin.jar.jar? Windows hides extensions by default — check.

4. It loads, but commands don't work

Almost always permissions. Test as OP first: if it works as OP and not otherwise, grant the plugin's permission nodes through your permissions plugin (LuckPerms being the standard choice).