The lineage that matters
CraftBukkit proved that servers could expose a plugin API; Spigot took that code, improved it, and became the foundation nearly everything else builds on. Paper, Purpur, and most other forks are Spigot forks.
Because of that, “Spigot plugin” and “Paper plugin” describe the same ecosystem from the developer’s point of view.
What Spigot still provides
Spigot offers stable vanilla-like gameplay, the Bukkit API, and no dependency on later forks. Its documentation and config files remain the reference that Paper extends with paper-global.yml and paper-world-defaults.yml.
On a small, quiet server it performs perfectly well — the differences only become obvious under load.
Why forks overtook it
Paper and its descendants added performance work Spigot never merged, plus configuration for entity and redstone limits, better tooling, and faster releases after each Minecraft version.
The only reason to stay on standalone Spigot is a plugin that explicitly refuses to run on Paper — rare, but real when it applies to you.
FAQ
Common questions
Is Spigot still maintained?
It receives updates for new Minecraft versions, but the bulk of modern development happens in its forks. Most servers that begin on Spigot move to Paper when they want better performance or tooling.
Do Spigot plugins work on Paper?
Yes, effectively all of them, because Paper implements the same API. The reverse is not guaranteed: plugins built against Paper-specific APIs will not run on Spigot.
