This article walks through using the plugin store in the panel.

Open the store

Go to the Plugins section in the side menu; it works only with plugin-family software (Paper, Purpur, Spigot, CraftBukkit). On mod loaders (Fabric, Quilt, Forge, NeoForge) the same row reads Mods and opens the mod store. On Vanilla it is greyed out, and hovering it suggests switching to Paper in the Software section — see the software comparison.

Search and filter

The store is fed by three sources: SpigotMC, Modrinth and PaperMC Hangar. A search runs against one source at a time — the one picked in the source box, which opens on SpigotMC. Hangar is Paper-centric, so it is offered only on Paper and Purpur. Sort by most downloaded, newest or recently updated; an empty search box returns the most downloaded.

Each result shows its supported version range as a badge. Content that doesn't match your server's version gets an incompatibility badge and its Install button is disabled, so you can't install the wrong release by accident. Results are paginated; numbers and arrows below move you through them.

Install

Press Install and the panel resolves the right release file, downloads it into the correct folder, and the server machine verifies it is genuinely a jar. The change needs one restart; a banner at the top reminds you.

Some plugins are distributed from their own site or a code repository. The panel tries to resolve the file automatically, then searches the same plugin by name in the other stores; if that fails, it asks you to upload the jar from the Files section.

The installed list and disabling

Everything you install is collected on the Installed tab with its file name and size. You can disable a plugin instead of deleting it, then re-enable it; disabled entries have a struck-through name. Plugins the system installs itself, such as the cross-play bridge, stay out of this list — they are managed from their own switch.

This is the most useful tool when hunting a problem: if the server broke after an install, switch it off and test without deleting. Don't disable several at once — you won't know which was responsible. Disabling and deleting both need a restart.

How many plugins can I install?

There is no hard cap. A recommended number is shown based on your package; go over it and the panel just notes that performance may be affected, leaving the decision to you. On larger packages no recommendation appears at all.

The number alone isn't decisive: one badly written plugin can cost more than ten light ones — see plugin count and performance.

If the install fails, check these in order

  1. Version mismatch. The "not tested with your server's version" message means the plugin's range doesn't cover your server; it names the tested range too. Find a newer release on another source, or move your server's version into range.
  2. The resource is paid. If it says the resource is distributed as premium, we can't download it for you; if you bought it, upload the jar from the Files section.
  3. The store isn't answering. The message appears when the site hosting the content can't be reached. Try again in a few minutes, or pick another store from the source box.
  4. No space left. An "insufficient storage" warning means the server's disk quota is full. Clear out old world folders and files you no longer need.
  5. Too many attempts in a row. Try many installs in a short window and the panel makes you wait a few minutes.
  6. Install succeeded but the plugin isn't there. Make sure you restarted, then search the plugin's name on the Console screen: the startup log usually names the cause — a missing dependency or the wrong Java version.

Common mistakes

  • Expecting results without a restart. Installing, disabling and deleting take effect only after the server is started again.
  • Installing five plugins at once. If the server then refuses to start, finding the culprit costs hours; install two at a time and boot in between.
  • Leaving two versions of the same plugin in the folder. A newer release usually has a different file name, so the old jar isn't replaced; leave it there and the server errors out at startup.
  • Confusing mods with plugins. A mod jar does nothing in the plugin folder; for the mod side see installing mods and modpacks.
  • Assuming deletion also removes the settings. Removing deletes only the jar; the configuration folder stays, so reinstalling brings the old settings back. For a clean start, delete that folder too.

Which option to pick when

  • Can't find it? Switch sources. SpigotMC is the default and the widest pool; Modrinth gives the tidiest version metadata; Hangar carries maintained Paper-side projects.
  • Mod or plugin? Mod loaders only unlock from 8 GB upwards; on the 2 and 4 GB packages you install plugins, not mods — the feature you want often exists as a plugin too.
  • Phone and tablet players joining? Stay on plugin-family software: the cross-play bridge is a plugin and needs Minecraft 1.20.5 or newer plus at least 4 GB.
  • Server got heavy? Measure before deleting. Disable two at a time from the Installed list and watch the TPS gauge on Overview; find the culprit by the difference, not by guessing.

For choosing plugins, configuration files, permissions management and common problems, move on to the full plugin guide.