One in six Bedrock packs ships with the wrong file extension
We opened 37,330 Bedrock packs and compared what each filename claims against what is actually inside the archive. 6,282 of them disagree — and that mismatch is behind a good share of the import failures people put down to a corrupted download.
Three extensions, three different things
Minecraft Bedrock decides what to do with a file by its extension, and the three you meet are not interchangeable — they describe genuinely different archive layouts.
| Extension | What is inside | What Minecraft does with it |
|---|---|---|
| .mcpack | One pack. manifest.json sits at the top level of the archive. |
Imports a single pack — behaviour or resource, not both. |
| .mcaddon | Several packs. Sub-folders, each with its own manifest.json. |
Unpacks them all — this is how a behaviour + resource pair arrives together. |
| .mcworld | A world. level.dat and a db/ folder, no manifest at the root. |
Imports as a playable world, not as a pack. |
All three are ordinary ZIP archives underneath. That is precisely why the mistake is so easy to make and so hard to spot: any of them can be renamed to any other and nothing complains until the moment you tap it.
What the mismatch looks like at scale
We read the structure of every Bedrock pack in our catalogue we can open, and record what the archive really is. Comparing that against the filename gives this:
| Filename says | Archive actually is | Packs |
|---|---|---|
| .mcaddon | mcaddon ✅ | 18,788 |
| .mcpack | mcpack ✅ | 7,291 |
| .mcworld | mcworld ✅ | 4,969 |
| .mcpack | mcaddon ❌ | 4,522 |
| .mcaddon | mcpack ❌ | 1,708 |
| .zip | mcaddon ❌ | 52 |
6,282 files out of 37,330 — 16.8% — are named as something they are not. The larger group by far is a multi-pack archive wearing a .mcpack name: 4,522 of them.
Nobody is being careless on purpose. An author zips a folder, renames it to whatever extension they saw on a tutorial, and it works on their own device because their device already has the pack installed from testing. The file reaches everyone else and behaves differently.
Why the wrong name breaks the import
Minecraft reads the extension first and then expects a matching shape inside.
- A multi-pack archive named .mcpack — the game looks for one
manifest.jsonat the root and finds folders instead. Depending on the version you get an import error, a nameless entry in your pack list, or an import that appears to succeed and produces nothing. - A single pack named .mcaddon — the game looks for sub-folders and finds a manifest. This one often works anyway, which is why the 1,708 in that row cause fewer complaints than their count suggests.
- A world named .mcpack — no manifest anywhere. This is the classic case where the import ends with an unnamed or blank entry, because the game has nothing to read a name from.
That last one is worth dwelling on. When people report a pack that imported "with no name", the file is very often a world with a pack extension. It is not damaged, and re-downloading it will never help.
The fix takes ten seconds
Rename the file to match what is actually inside it, then open it again:
- Find the download in your file manager (usually Downloads).
- Open the archive to look, if your file manager can — sub-folders each containing
manifest.jsonmeans .mcaddon; a singlemanifest.jsonat the top means .mcpack;level.datmeans .mcworld. - Rename the extension accordingly and tap the file.
If your file manager will not show you inside, the practical order to try is .mcaddon first — it is the most common true shape — then .mcworld. Renaming is non-destructive; the bytes do not change.
In our own app we detect the real shape and hand the file to Minecraft under the correct extension, so this class of failure never reaches the person downloading. This article exists because the same files circulate everywhere else too.
What this does not fix
Renaming solves a naming problem and nothing else. If the pack imports cleanly under the right extension and still does nothing, you are looking at a different failure — most often the scripting toggle or a build made for another game version. Those are covered separately in Addon broke after a Minecraft update and Your mod isn't broken — it's for another version.
And if the pack never appears in the list at all, start with Addon not showing up or won't import, which covers activation and edition mistakes.
The short version
The extension on a Bedrock pack is a claim, not a fact, and in our catalogue that claim is wrong 16.8% of the time. When an import fails oddly — no name, no error, nothing installed — check the shape of the archive before you assume the file is broken. It usually is not.