To add a plugin to a Minecraft server, drop the plugin's .jar file into the plugins folder in your server's root directory and restart the server. The real work is not the installation — it is picking the right file: your server software, Minecraft version and Java version all have to line up. This guide covers where to download plugins safely, how to install and update them, which command will quietly break your server, and exactly what to look for in the log when something fails.
Confusing these three is the most common mistake new server owners make, and it leads directly to "my server won't start".
If you run a public server, you almost always want plugins — they demand nothing from your players and keep the barrier to joining at zero.
The plugin ecosystem is built as a chain. Bukkit defined the original plugin API; Spigot built on Bukkit and added performance improvements; Paper built on Spigot with far more aggressive optimisation and an extended API.
The practical consequence: a plugin written for Bukkit runs on Spigot and Paper, a Spigot plugin runs on Paper, but a plugin using Paper-only API will not run on Spigot. This is why most server owners today simply run Paper — it is faster and supports the full range of plugins.
Vanilla server software does not support plugins at all. If you are running vanilla, you need to switch to Paper first. Setting up from scratch? Follow the steps in our guide on how to set up a Minecraft server.
This currently causes more failures than anything else, because the requirement recently moved. Minecraft switched to year-based version numbering, and Paper's official requirements are now:
Try to run 26.1 or 26.2 on Java 21 and the server will refuse to start, throwing UnsupportedClassVersionError in the console. Check what you have installed with java -version.
Version matching applies to plugins too: a plugin compiled for 1.21 may not run on 26.2. Plugins that touch items, mobs, packets or world data in particular must be updated after a version drop. Because Paper's 26.2 builds ship with Adventure 5 and removed previously deprecated API, some plugins that worked fine on 26.1 will break on 26.2.
Choosing a source is a security decision. Paper's own documentation is blunt about it: plugins are given full and unrestricted access not only to your server but to the machine it runs on. A .jar from an untrusted source can take over the entire box.
Trusted sources:
What to avoid: sites offering paid plugins for free, download links routed through link-shorteners or ad gateways, and pages serving an .exe or installer instead of a .jar. Some plugins ship as .zip — extract the archive and use the .jar inside.
Installation is five steps:
On the plugin page, pick the file that supports your server's Minecraft version. "Latest release" is not automatically the right release for you.
Run stop in the console. Changing files on a running server causes corruption.
Copy the .jar into the plugins folder in your server root. One important detail: subdirectories are not scanned. Put the file in something like plugins/EssentialsX/ and it will never load.
On first start the plugin creates its own configuration folder automatically.
Run /plugins in the console or in game. If the plugin's name appears in green, it loaded; if it is red, something failed and you need to read logs/latest.log.
Rather than deleting the old .jar and dropping in a new one, use Paper's update folder: place the new build in plugins/update/ and restart. Paper swaps the old file for the new one automatically, which eliminates the classic problem of two versions of the same plugin sitting in the folder at once.
Do not use /reload. It reloads plugins without shutting them down cleanly, leaving open database connections, orphaned scheduled tasks and memory leaks behind. The symptoms usually do not appear immediately — they show up hours later as unexplained TPS drops and crashes. The correct action is always a full server restart.
For version upgrades the order is: back up first, then update plugins, then update the server software. Paper's own documentation calls backing up "the most important step, and yet the most frequently skipped". And note that once a world has been upgraded to a newer version, you cannot downgrade it — which makes a copy of the world folder non-negotiable before upgrading.
On first run a plugin creates plugins/PluginName/ containing a config.yml. The file is YAML, and it has two rules: indent with spaces, never tab characters, and always leave a space after a colon. Break either rule and the plugin will fail to load.
After editing the configuration, most plugins provide their own reload command (something like /pluginname reload). That is not the same as the server-wide /reload and it is safe to use.
On permissions you need to make an early decision: most plugins work through permission nodes, and managing those requires a permissions plugin. LuckPerms is the de facto standard — you define groups, assign players to them, and manage every plugin's permissions from one place. Accumulating plugins without a permissions system in place creates a mess that is painful to untangle later.
Every troubleshooting session starts with logs/latest.log. The error that scrolled past in the console is sitting in that file.
Turkey (Türkçe)
Worldwide (English)
UnsupportedClassVersionError points straight at Java. 26.1 and later need Java 25.plugins? Subdirectories are not scanned.Plugin accumulation is the biggest enemy of performance. For a solid start, these categories are enough:
Add each new plugin one at a time and watch the server for a while after each. Install five at once and hit a problem, and finding the culprit will cost you hours.
Plugins consume RAM and CPU; land protection and block logging in particular generate noticeable load through database operations. Because Minecraft is sensitive to single-thread performance, processor clock speed matters more than core count.
Nubitro Minecraft servers run in Istanbul, Turkey with NVMe M.2 SSD storage and 1 Gbps unmetered traffic. Plans start with Starter at 2 cores / 4 GB RAM / 50 GB NVMe and scale through Silver (4 CPU / 8 GB), Gold (6 CPU / 16 GB) and Premium (6 CPU / 32 GB RAM with 100 GB NVMe).
For a Turkish player base, the Istanbul location is a direct latency advantage — one you cannot recover through plugin tuning. You can review current plans on our Minecraft server hosting page. If you want full control rather than a ready-made plan, our guide on the difference between VDS and VPS clarifies which infrastructure fits you.
No. Plugins run server-side only; players connect with a stock Minecraft client. The thing that requires client-side installation is a mod, not a plugin.
Stop the server, delete the .jar from the plugins folder, and restart. The plugin's configuration folder stays behind; delete it too for a clean removal. Be careful though — if the plugin stores data (land claims, economy balances), deleting the folder destroys it permanently.
Load matters, not count. Thirty lightweight plugins can cause fewer problems than five badly written ones. The right approach is to measure with a profiler and see which plugin is eating tick time.
Yes. Paper is compatible with the Spigot API and runs Spigot plugins. The reverse is not true: a plugin using Paper-only API will not run on Spigot.
Some might. Plugins working with items, mobs, packets or world data have to be updated after version drops. Check that each plugin supports the new version before upgrading, and always take a backup.
Outside a test environment, no. It does not shut plugins down cleanly, producing memory leaks and scheduled-task conflicts whose symptoms typically surface hours later. On a live server, always do a full restart.
.jar goes directly into plugins — subdirectories are not scanned./plugins; a green name means it loaded.plugins/update/ folder when updating./reload; always do a full restart.logs/latest.log.