Java · data

284,524 Java mods, counted properly

3 August 2026·6 min read·Java

Most writing about Minecraft Java mods describes a handful of famous ones. We can do something different: describe all of them. Our Java catalogue holds 284,524 mods against 47,580 for Bedrock — six times as many — and counting the whole thing tells you things a top-ten list never will, starting with the fact that the Java side is far patchier than it looks.

The loader split

A Java mod is a .jar file, and a .jar does nothing on its own. It needs a mod loader, and it needs the right one. Here is how the catalogue divides:

The first row is the one that surprises people. The largest single group in the Java catalogue is not client mods at all — Spigot entries are server plugins, and installing one into your mods folder does nothing. If you have ever downloaded a promising-looking Java mod and found that the game started normally and nothing changed, this is the most likely reason.

The second thing worth knowing: Forge and NeoForge are not interchangeable, despite the names. NeoForge is a fork, and a mod built for one will generally refuse to load under the other. Same for Fabric and Quilt, although Quilt is deliberately more forgiving in that direction than the reverse.

Coverage is uneven, and we would rather say so

Not every entry in a catalogue this size is equally complete. Ours:

Only one mod in seven carries a proper write-up from its author. That is not us losing the text — it is what the sources hold. A large share of Java mods are published with a title, a version list and a file, and nothing else. The honest thing to do with a number like that is publish it rather than pad the gap with generated filler.

The question that decides everything

If you take one thing away, take this: the loader and the game version have to match the mod, not each other. Almost every "it doesn't work" report we receive on the Java side comes down to one of three mismatches.

• Wrong loader. A Fabric mod under Forge does not load. It also does not usually crash — it simply is not there, which is why people assume the mod is broken rather than misplaced.
• Wrong version. A mod for 1.20.1 under 1.21 will normally refuse to start, and take the whole game down with a crash log naming it. This one at least tells you what happened.
• Server plugin in a client folder. See the Spigot row above. 79,554 opportunities to make this mistake.

None of these are exotic. All three are visible before you download, if the listing tells you the loader and the supported versions — which is exactly why we surface both on every mod page rather than burying them in the description.

Which versions the catalogue actually covers

Version support is the other half of the compatibility question, and the shape of it is not what you would guess from release notes. Counting distinct mods per major line:

Two things stand out. The current line dominates, as expected — but 1.8 sits fourth, above 1.16 and 1.18, for a version released in 2014. That is the PvP and minigame server world, which never moved on and never will; the Spigot plugins from the table above cluster here. If you have ever wondered why a decade-old version still has active development, that is the answer.

The second is 1.12, still carrying 25,113 mods. 1.12.2 was the last stop for a generation of large Forge modpacks, and their dependencies are frozen there. A modpack is a web of mods that must all agree on a version, so the whole web tends to stay put rather than migrate together.

One caveat we would rather state than hide: 24,070 Java mods carry no version information at all — 8.5% of the catalogue. Some sources simply do not publish it. Where we have nothing, we show nothing rather than guessing, which is why some mod pages have a version line and some do not.

Java against Bedrock, briefly

The two halves of Minecraft modding do not resemble each other. Bedrock add-ons are packaged archives that the game imports directly; there is no loader, and the main failure mode is a broken or half-complete pack. Java mods are code that runs inside the game through a loader, and the main failure mode is a mismatch between three moving parts.

That difference shows up in the numbers. On Bedrock we can open every archive and tell you whether it will install, because the answer is in the file. On Java we cannot promise that, because whether a mod works depends on what else you have installed alongside it. Anyone claiming otherwise about a 284,000-mod catalogue has not tried.