How to Install Plugins on a Paper Minecraft Server

To install a plugin on a Paper Minecraft server, download the compatible .jar, stop the server, upload the file directly to the plugins folder, and start the server again. Then check the console and run /plugins to confirm that it loaded.

The process is simple, but version mismatches, missing dependencies, or duplicate JARs can prevent a plugin—or the entire server—from starting correctly.

Before installing a plugin

Check these four things first:

1. The server runs Paper. A Vanilla server cannot load plugins. Spigot and Bukkit plugins are often compatible, but this guide is specifically for Paper.
2. The plugin supports your Minecraft version. Read the download page and release notes. Do not assume an old plugin will work on a new server version.
3. The download comes from a trusted source. Prefer the project’s official site, Hangar, Modrinth, or SpigotMC. Avoid unofficial reupload sites.
4. You have a backup. Save the world and configuration before changing important plugins. Use our Minecraft server backup checklist if you need a safe starting point.

If you are still choosing what to add, start with our essential Minecraft server plugins. A small, useful stack is easier to maintain than twenty plugins installed at once.

How to install Paper plugins step by step

1. Download the correct file

Download the plugin release that lists support for your Minecraft and Paper version. The server normally needs a file ending in .jar.

If the download is a .zip, read the project instructions before uploading it. The archive may contain documentation or several platform files, and you may need to extract the correct JAR.

Check for required dependencies as well. Some plugins need Vault, ProtocolLib, or another plugin before they can load.

2. Stop the server

Stop the server from the panel and wait for the console to confirm shutdown. Do not replace files while Paper is saving the world.

A full stop reduces the risk of incomplete files and prevents the old plugin version from remaining loaded in memory.

3. Upload the JAR to plugins

Open the server file manager, enter the plugins folder, and upload the .jar there. Keep it directly inside that folder rather than placing it in a subdirectory.

The path should look like this:

/plugins/PluginName.jar

If the plugins folder does not exist, start Paper once and stop it again. Paper creates its working folders during the first startup.

4. Start the server again

Start the server and watch the console. During startup, Paper discovers the JARs, checks dependencies, and enables valid plugins.

Use a full restart. /reload is not a safe way to replace plugin JARs on a running server and can leave tasks, commands, or configuration in an inconsistent state.

5. Verify that the plugin is enabled

After startup finishes, run:

/plugins

You can also enter plugins in the console. An enabled plugin normally appears in green; a disabled or failed plugin may appear in red.

Do not rely on the list alone. Check the startup console or logs/latest.log for WARN and ERROR messages that mention the plugin. The log usually identifies a missing dependency, invalid JAR, or unsupported version.

Configure and test the plugin

Many plugins create their own directory after the first successful start:

/plugins/PluginName/

This directory commonly contains config.yml, message files, and plugin data. Stop the server before major edits, preserve YAML indentation, and keep a copy of the original configuration.

After configuring it:

1. restart the server;
2. check the console;
3. test commands with an account that is not OP;
4. confirm normal players only receive the permissions they need.

Use our basic LuckPerms guide to organize groups and command permissions.

Common plugin installation problems

Problem	Likely cause	What to do
Plugin does not appear	JAR is in a subfolder, still zipped, or is not a plugin	Put the .jar directly in plugins and restart
Plugin appears in red	Missing dependency or incompatible version	Read logs/latest.log and the plugin download page
Server will not start	Wrong JAR, broken dependency, or conflict	Remove the newest plugin, start again, and inspect the full error
“Ambiguous plugin name” warning	Two versions of the same plugin are present	Keep one JAR and restart
Command exists but players cannot use it	Permission nodes are missing	Grant the correct nodes through LuckPerms
No plugins folder	Server is not running Paper or has never started	Verify the server software and start Paper once

Install and test one plugin at a time. If you change five JARs before restarting, it becomes much harder to identify which change caused the problem.

How to update or remove a plugin

To update a plugin:

1. create a backup;
2. stop the server;
3. remove the old JAR;
4. upload the compatible new release;
5. make sure two copies are not present;
6. start the server and inspect the console.

You normally keep the plugin’s data directory, but always read the release notes in case an update changes the configuration format.

To remove a plugin, stop the server, delete its JAR, and start again. Keep its data directory until you are certain you will not need the old configuration.

Plugins and mods are different

Paper loads plugins built for the Paper, Bukkit, or Spigot APIs. Fabric, Forge, and NeoForge mods use different loaders and do not work by placing them in plugins.

Choose modded server software when you want to run a modpack, and check whether players must install the same mods. Choose Paper when you want server-side commands, permissions, protection, and admin tools without changing every player’s client.

Final checklist

• Paper is selected as the server software.
• The JAR is from a trusted source and supports your version.
• You checked the required dependencies.
• A recent backup exists.
• The file is directly inside plugins.
• You performed a full restart instead of /reload.
• /plugins and logs/latest.log confirm successful loading.
• Commands and permissions were tested with a normal account.

On Mineando, you can manage the server files and console from the panel. Install one plugin, verify it, and add the next only after the base is stable. That habit prevents most hard-to-diagnose plugin problems.

The primary technical reference for this process is the Paper plugin documentation.