Guides · Growth

How to get more downloads for your Minecraft plugin on SpigotMC

How to get more downloads on SpigotMC: tag lines, the first screen, GIFs that load, updates, reviews, Modrinth and Hangar, and measuring what works.

Updated 9 October 2026 · by Skilled · 6 min read

Most plugins don't fail because they're bad. They fail because a server owner scrolled past them in four seconds. Getting more downloads is mostly about those four seconds: what the listing says before anyone clicks, what the first screen of the page shows, and whether the plugin looks alive.

This guide goes through it in the order a server owner sees it. Everything here works for free and paid resources alike.

Start with the problem, not the name

On SpigotMC's resource list, a server owner sees three things: your icon, your title and your tag line. The tag line is the sentence that sells the click, and most plugins waste it on "A simple plugin that adds…".

Write it as the problem it solves, with the words people search for:

A few rules that hold up:

• Put the platforms and versions in it if they're a selling point ("1.8 to 1.21", "Folia support"). Server owners filter mentally by version before anything else.
• Use the words a server owner would type into search: "economy", "shops", "minigame", "anticheat". SpigotMC's search and Google both read the title and tag line.
• Keep the title short and memorable. If your plugin's name doesn't say what it does, the tag line has to.

The icon matters more than it should. A clean, readable icon at small size (a single shape, strong contrast, no tiny text) gets more clicks than a screenshot squeezed into a square.

The first screen decides

Once someone opens your page, the part above the fold has to answer three questions: what does it do, does it work on my server, and does it look good?

What works:

1. A banner or a hero image that shows the plugin in action, not just its logo.
2. One paragraph saying what it does and for whom, in plain words.
3. Compatibility in bold: server software, Minecraft versions, dependencies (or "no dependencies"). Owners running Paper 1.21 want to know in one glance that they're covered.
4. A GIF or short video of the core feature.

What doesn't: a wall of BBCode-coloured text, a changelog at the top, or a list of 40 commands before anyone knows why they'd want the plugin. Commands and permissions belong further down, or in the Documentation tab.

If you want a structure to copy, we wrote a free SpigotMC resource page template with the BBCode ready.

Make your images and GIFs actually load

SpigotMC doesn't host the images in your description. You link them from somewhere like Imgur, and SpigotMC serves them through its own image proxy. Two things go wrong often:

• Big GIFs don't show. In our experience the proxy stops serving GIFs above roughly 3 MB: the visitor sees a broken image right where your best feature should be. Keep GIFs short (5 to 8 seconds), small (around 600 px wide) and under that size. Convert longer clips to a YouTube video and embed it instead.
• Huge PNGs load slowly. Export screenshots as optimised PNG or JPEG. A description made of a few tall "poster" images, one per section, looks polished and loads fast if each one stays well under a megabyte.

Also: SpigotMC strips 4-byte emojis from descriptions, so 🚀 and friends simply vanish. Use plain symbols like ★ or ✔, or none.

Look alive: updates, replies and reviews

A plugin with a last update two years ago reads as abandoned, even if it works perfectly. Server owners know that a dead plugin breaks on the next Minecraft version.

• Update with every Minecraft release, even when it's only "Tested on 1.21.x, no changes needed". Updated resources show up again in SpigotMC's "latest updates", and the date on your page stays recent.
• Write useful update notes. "Fixed bugs" tells nobody anything. "Fixed shops losing items on restart with MySQL" tells a server owner you care about their data.
• Answer the discussion tab and reviews. A reply under a one-star review ("fixed in 2.3.1, thanks for the report") often turns the review around, and everyone reading it sees a maintained plugin.
• Ask for reviews at the right moment. Not on every join, not in a nagging broadcast. A good moment is after an admin has used the plugin for a few days: a single, polite message to admins with a link to the review page works far better than begging in the description.

Be where server owners look

SpigotMC is the biggest, but it's not the only place people find plugins:

• Modrinth has a growing share of Paper and Purpur users, a clean search with filters by loader and version, and a gallery. Its short summary works like SpigotMC's tag line: write it the same way.
• Hangar is PaperMC's own repository, and some Paper users start there.
• Your own Discord turns downloads into a community: support in one place, update announcements, and people who'll tell you what to build next.
• YouTube showcases still drive installs. Many small channels review plugins; a 3-minute video often brings more downloads than a month of forum posts.

Cross-listing is cheap: the same jar, the same images, a description adapted to each site's format.

Measure the whole path, not just downloads

Downloads are the only number SpigotMC gives you, and it's the least useful one. It doesn't tell you how many people saw your page and left, or how many downloads ended up running on a server, or how many servers kept the plugin a week later.

The path that matters looks like this:

listing views → downloads → servers that install it → servers still running it after a week

Each step tells you something different:

SpigotMC doesn't show authors how many people view their page, but you can measure it with a tracking image in your description. PluginAnalytics does exactly this: an invisible pixel or a live badge on your SpigotMC and Modrinth pages counts views, downloads are read from both sites, and the SDK in your plugin counts the servers that install it and keep it. You see the whole funnel in one chart, and you see whether the new GIF you added last Tuesday changed anything.

Whatever you use, change one thing at a time and give it a week. That's how you find out what actually brings downloads, instead of guessing.

A quick checklist

• Tag line names the problem and the platforms, in words people search for.
• The first screen shows the plugin in action, says what it does and lists compatibility in bold.
• GIFs under about 3 MB, images optimised, no 4-byte emojis.
• An update for every Minecraft version, with update notes that say something.
• Replies to reviews and questions within a few days.
• Listed on Modrinth and Hangar too.
• Views, downloads, installs and retention measured, one change at a time.

More guides