We opened 39,065 Bedrock add-ons. Here is what actually installs.

What "checked" means here

Of the 47,000-odd live Bedrock entries, 39,065 have been fetched and inspected. The remaining 8,301 are waiting in the queue or sit behind a page that hands out the file only to a human. When we say a file was checked, we mean the archive was downloaded, opened, and its manifest read — the same manifest Minecraft itself reads when it decides whether to import a pack.

The half-pack problem is the big one

2,958 add-ons declare a dependency on another pack and then don't include it. This is the single most confusing failure in Bedrock, because nothing looks wrong. The file downloads. Minecraft imports it. The pack appears in your world settings and activates happily. And then in the game, the new mobs have no textures, or the textures exist but the mobs never spawn.

It usually happens because the author uploaded one half of a two-part add-on — the behaviour pack without its resource pack, or the reverse — either by mistake or because the two halves live in separate downloads on their original site and only one link got shared around.

Related and separately counted: 539 packs ship custom entities in a behaviour pack with no matching resource pack anywhere. Those are the invisible mobs. You hear them, arrows hit them, and there is nothing to see.

What is actually inside these packs

We also classify what each archive contains. 32,530 packs have been through this:

A resource-pack-only download is not a defect, by the way. A texture pack or a shader is supposed to be resources and nothing else. That is exactly why we track "incomplete" separately from "resource pack only" — one is a broken add-on, the other is a texture pack doing its job. Conflating the two would flag ten thousand perfectly good downloads.

Beta APIs: the switch nobody mentions

Of 32,099 add-ons we could test for it, 1,529 will not run unless Experiments → Beta APIs is switched on in the world settings. That is under 5% of the catalogue, and it causes a wildly disproportionate share of "I installed it and nothing happened" messages — because the pack activates normally, the game gives no warning, and the scripts inside it simply never load.

These tend to be the ambitious ones: add-ons with custom menus, quest systems, working machines, NPCs that talk. If you downloaded something clever and the world looks untouched, this is the first thing to check. Open the world, hit Edit, scroll past the pack lists to Experiments, turn on Beta APIs, save, and go back in.

Version floors, and why "made for 1.21" is not the whole story

Every pack states a minimum engine version in its manifest. Here is what the catalogue asks for most often:

The floor is a minimum, not a guarantee. A pack that asks for 1.16.0 will usually still load on 1.21 — but a pack asking for 1.21.0 will not work on 1.20, and Minecraft's error message for that is unhelpful enough that most people assume the file is broken. When our panel says "Manifest requires Minecraft 1.21.0 or newer", that is read out of the file itself, not copied from a description.

The other side of this trap: on sites where an author publishes one file per game version, a link shared in a chat six months ago points at a build for a version you no longer run. The file is fine. It is just not for your game.

What players report, and what surprised me

Between 16 June and 2 August 2026 we received 24,171 problem reports covering 6,509 different mods. The breakdown is not what I expected:

I assumed "doesn't work in the game" would dominate, because that is the failure people talk about. It is the smallest of the three. Seven out of ten problems happen before Minecraft is ever involved — during the download, or at the moment the file is handed to the game.

That reframed what we work on. A dead download link is our problem to fix, not yours: we can re-host the file, or find the author's current one. An import that fails is usually a file named with the wrong extension — Minecraft chooses how to open a pack purely from .mcpack versus .mcaddon versus .mcworld, so a pack saved with the wrong one imports as "unknown name" and does nothing. That is also fixable on our side, and it is why our pages tell you the real type when the name disagrees with the contents.

The rest of the tail

Small counts, but each one is a specific broken thing rather than a vague "didn't work":

• 133 packs depend on beta features so old that current Minecraft no longer provides them.
• 85 have a manifest that isn't valid JSON — a stray comma is enough for the game to reject the whole pack.
• 40 silently override the player model, which is why an unrelated add-on can suddenly change how your character looks.
• 15 have a manifest we couldn't read at all, and 15 more aren't valid archives despite the file name.

What to do with all this

If you take one thing away: most add-ons are fine, and most failures are two or three specific, nameable things. When something doesn't work, it is almost never mysterious.

1. Nothing downloaded? Try another network and check your storage. If it still fails, tell us — a dead link is ours to fix.
2. Downloaded, but Minecraft never opened it? Re-open it from the Downloads tab in our app rather than from the file manager, and make sure Minecraft is installed and current.
3. Imported, but the world looks untouched? Check both pack lists are activated, then turn on Experiments → Beta APIs.
4. Mobs with no textures, or textures with no mobs? You have half a pack. Look for the other half, or pick a different upload of the same add-on.

And the step-by-step versions of all of that live in our guides — including installing Bedrock add-ons and what to do when an add-on doesn't show up.

All figures in this article were measured against our own catalogue on 2 August 2026 and will drift as the catalogue grows and more files get checked.