Check whether your plugins match your Minecraft version and platform — and flag known conflicts before you update.
Choose your Minecraft version and server software, then list the plugins you plan to run. We check compatibility and known conflicts.
One plugin name per line, or paste a folder listing (we strip .jar and version numbers).
| Plugin | Status | Details |
|---|
Check your Minecraft plugin list against your game version and platform — Paper, Folia, Spigot, and more — to spot version mismatches and known conflicts before you update or open the server.
A single outdated jar can prevent the server from starting or cause lag and crashes after an update. Plugin pages list support for specific Minecraft versions and platforms; scanning that by hand for thirty jars is tedious and easy to miss.
Paste plugin names or a folder listing, choose your Minecraft version and platform, and get a table of OK, warning, conflict, and unknown results with short notes you can act on.
Folia and regionalized threading break plugins that assume a single world tick. Paper-only APIs fail on plain Spigot. Popular combinations sometimes fight over chat, economy, or protection — the checker flags well-known conflict pairs from a curated list so you can plan replacements.
Export a report for your update checklist or share it with staff before a big version jump. Unknown entries are not failures; they simply are not in the known list yet, so confirm those on the plugin’s download page.
Update or remove anything marked as incompatible first. Resolve conflicts by picking one plugin for that job. Test on a staging copy of the world when you change many jars at once. Keep a backup of the plugins folder before you delete anything.
Pair this with the crash analyzer if the server already fails to boot — the log often names the jar that loaded last.
