Do I need to restart the server after installing a plugin?

Yes. Plugins are loaded at startup, so a full server restart is required. Avoid using /reload -- it sometimes works but can cause memory leaks and weird behavior, especially with complex plugins.

Can I install plugins on a Bedrock Edition server?

No. Bukkit plugins are Java Edition only. Bedrock servers use a separate addon and behavior pack system that works completely differently.

Why is my plugin showing in red in /plugins?

A red plugin failed to load. Check your server console for the error message right after startup -- it will usually say exactly why. The most common reasons are a version mismatch or a missing dependency plugin.

Can I install Forge or Fabric mods on a Spigot/Paper server?

No, they are separate systems. Bukkit plugins go in the plugins folder on Bukkit-based servers. Forge and Fabric mods go in a mods folder on their respective server types. You cannot mix them unless you are using a hybrid server like Mohist, which comes with its own tradeoffs.

Where do I find plugins to download?

SpigotMC.org, Modrinth, and Hangar (PaperMC's official plugin repository) are the most common places. Always download from the original source page rather than third-party mirrors, and check that the plugin version matches your server version before downloading.

How to Install Spigot / Bukkit Plugins on a Server

Installing a plugin on a Spigot or Bukkit server is mostly just copying a file and restarting — but there are a few ways to get it wrong, and they are all easy to avoid. This guide covers the whole process from download to confirmation.

What You Need Before You Start

A Bukkit-compatible server — Spigot, Paper, Purpur, CraftBukkit, or any fork that supports Bukkit plugins. Vanilla servers do not support plugins at all.
The plugin .jar file — downloaded from a source you trust, like SpigotMC.org, Modrinth, or Hangar. Make sure the plugin version matches your server version (1.21.x plugin for a 1.21.x server, etc.).
Access to your server files — via FTP/SFTP, an SFTP client like FileZilla, or the file manager in your hosting control panel.
Ability to restart the server — a full stop/start, not /reload.

This guide does not cover client-side mods. If you want to install Forge mods, see our guide on how to install mods with Minecraft Forge. For Fabric mods, check the Fabric loader install guide.

How to Install a Plugin

Stop the server. You can install the file while the server is running, but restarting is required anyway — stopping first is cleaner and avoids any file-lock issues.
Connect to your server files. Open your FTP client, SFTP client, or hosting panel file manager and log in to the server.
Navigate to the plugins folder. It sits at the root of your server directory, right next to server.jar and server.properties. If the folder does not exist yet, your server needs to be run at least once to generate it.
Upload the plugin .jar. Drag and drop the file, or use your client’s upload button. Upload the .jar file directly — do not put it inside a subfolder, and do not extract it.
Start the server. A full restart is the right move. The server reads the plugins folder on startup and loads everything it finds there.
Confirm the plugin loaded. Once the server is up, run /plugins in the console or in-game. You should see the plugin name listed in green. If it shows in red, it failed to load.

If the Plugin Has a Config

Many plugins generate a config file in plugins/PluginName/config.yml on first run. Restart once to generate it, then edit the config, then restart again for your changes to take effect.

Common Mistakes and Troubleshooting

Plugin shows in red in `/plugins`

This usually means the plugin could not load. Check the server console output for an error message — it will almost always tell you exactly what went wrong. Common causes:

The plugin requires a newer or older server version than what you are running.
The plugin depends on another plugin that is not installed. The error will name the missing dependency.
The .jar file is corrupted. Re-download it.

Plugin does not appear in `/plugins` at all

The file probably did not end up in the right place. Double-check that the .jar is directly inside the plugins folder, not nested inside a subfolder. Also confirm the file extension is .jar and not .jar.zip or something your browser renamed during download.

Do not use `/reload`

Many server admins reach for /reload to avoid a full restart. It works sometimes, but it is known to cause memory leaks and plugin conflicts, especially with plugins that register listeners or schedulers. Always do a full stop/start when installing or updating plugins.

Wrong server software

Bukkit plugins are not Forge or Fabric mods. If you are running a Forge, Fabric, NeoForge, or Quilt server, you need mods — not plugins. The two systems are separate and not interchangeable. There are hybrid server implementations like Arclight or Mohist that try to support both, but they are out of scope here.

Version mismatch

A plugin built for 1.20.4 will often refuse to load on a 1.21.1 server, or load but throw errors. Always check the plugin’s supported versions on its download page before installing.

Which Versions and Editions This Applies To

This method works exclusively on Java Edition servers running Bukkit-compatible software: CraftBukkit, Spigot, Paper, Purpur, Pufferfish, and their forks. If you are not sure what your server is running, look at the jar file name in your server folder — it will usually say “paper,” “spigot,” or similar.

This does not apply to:

Bedrock Edition servers (these use a completely different addon system)
Vanilla Java servers (no plugin support at all)
Forge, Fabric, NeoForge, or Quilt servers (these use mods, not plugins)
Realms (you cannot install custom plugins on Realms)