Plugins are what turn a plain Bukkit, Spigot, or Paper server into something with economy systems, land protection, custom commands, and everything else vanilla Minecraft does not offer. The install process is the same basic shape across almost every plugin, once you know where to look.
Plugins need a Bukkit-API server
Plugins only run on server software built on the Bukkit API: Spigot, Paper, Purpur, and similar forks. They do not work on vanilla, and they are a completely different system from Forge, NeoForge, or Fabric mods, a plugin and a mod are not interchangeable even if they sound similar.
Step 1: Find the plugin on a trustworthy source
Two platforms cover the large majority of the plugin ecosystem today: Hangar, PaperMC's own official plugin repository, and Modrinth, a modern cross-platform host. SpigotMC remains widely used too, particularly for older or Spigot-specific plugins. Stick to these rather than random third-party download sites.
Step 2: Check the plugin's supported versions
Every plugin page lists which Minecraft versions it supports. Unlike mods, plugins are often more forgiving across nearby versions since the Bukkit API changes less aggressively, but check anyway, especially for plugins that have not been updated recently.
Step 3: Drop the jar into the plugins folder
Every Bukkit-based server creates a plugins folder in its root directory once it has run at least once. Place the plugin's .jar file directly inside it, no subfolders needed.
Step 4: Restart the server
Most plugins load on server start rather than hot-reloading, so a full restart (not just a /reload command, which can cause its own issues) is the safest way to activate a newly added plugin. Watch the console output for the plugin's name appearing in the "Enabling" log lines.
Step 5: Check for a config file
Plugins that need configuration generate a folder under plugins/<PluginName>/ on their first run, usually containing a config.yml. Edit that, then restart again for the changes to take effect.
If a plugin doesn't load
Check the console for an error naming the specific problem, most commonly a missing dependency (like Vault for economy-related plugins) or an unsupported server version. The plugin's own page usually lists its dependencies explicitly.
Managing plugins without SSH
Tick Hosting's panel includes a file manager built for exactly this, upload, replace, or remove plugin jars directly from the dashboard, no FTP client required. Available on every plan, including the free tier, from Tick Hosting's plans page.