First, know what you're installing

Bedrock Edition — the version on Android, iOS, Windows 10/11, and consoles — doesn't use "mods" the way Java does. It uses an official add-on system built from two pieces:

A behavior pack changes what things do — how a mob acts, what an item crafts into, the rules of the world.
A resource pack changes what things look and sound like — textures, models, audio.

Most addons bundle both, so a new creature both shows up correctly and behaves correctly. That two-part design is exactly why installation has a step people miss: importing the file adds the packs to your library, but you still have to switch each pack on in the world. Hold that thought — it's the whole article.

You'll run into three file types. Knowing them saves you from the most common failure:

.mcpack — a single pack (one behavior or one resource pack).
.mcaddon — a bundle of packs, usually a behavior + resource pack together, sometimes several.
.mcworld — a ready-made world with packs already applied. This one lands in your worlds list, not your pack library.

Minecraft picks the import method purely by the file extension. A .mcpack is expected to hold a manifest at its root; a .mcaddon is expected to hold packs in sub-folders. If a file is named with the wrong one, the game either shows "unknown" on import or refuses it entirely. More on fixing that below.

The install, step by step (Android)

This is the flow for a normal .mcpack or .mcaddon. It's the same whether you grabbed the file from my app or anywhere else.

1. Download the addon file

Tap download and let the file finish. On Android it usually lands in your Downloads folder. If your browser warns about the file type, that's normal for .mcpack/.mcaddon — allow it. If you use my Bedrock catalog or the app, the download is already the correct file with the correct extension, which removes the single biggest cause of import failures before it happens.

2. Open the file so Minecraft imports it

Tap the downloaded file. Android hands it to Minecraft (it's registered to open these types), Minecraft launches, and you'll see a short "Importing…" message. When it's done you're dropped back into the game. If tapping the file opens a file manager or a "no app can open this" message instead, open it manually: in most file managers, long-press the file → Open with → Minecraft. In my app, hitting Open after download triggers the import directly, so you can skip the file manager entirely.

Importing was successful if the pack now shows in your library. Check under Settings → Storage, or you'll see it in the next step when you go to add it to a world. Import does not mean the addon is active yet.

3. Activate the packs in your world — the step everyone misses

This is where it clicks (or doesn't). Importing only put the packs in your library. Now you attach them to the world you want to play:

From the main menu, tap Play.
Tap the pencil / edit icon next to an existing world (or start Create New World).
In the left menu, scroll to Behavior Packs. Tap it, find your addon, tap it, and press Activate.
Then open Resource Packs and do the same — tap the pack, press Activate.
Press Play (or Create) to load the world.

That's the whole trick. A full addon has two packs, and you have to switch on both — the behavior pack for the logic and the resource pack for the visuals. Activate only the resource pack and your new mob looks right but does nothing. Activate only the behavior pack and it works but shows up as a missing-texture cube. If Minecraft prompts you to apply the resource pack when you enable the behavior pack, say yes — that's it linking the pair for you.

Packs apply per world, not globally. Turning an addon on in one world doesn't turn it on in the others. If you make a fresh world tomorrow and the addon "disappears," it's still in your library — you just haven't activated it in that new world yet.

Script addons: turn on Experiments / Beta APIs

A growing number of addons use Minecraft's scripting system for smarter behavior — custom UIs, new mechanics, things vanilla behavior packs can't do alone. Those need one extra toggle, and skipping it is the second-most-common reason an addon "does nothing."

When you edit or create the world, open the Experiments section (under the world settings, near the bottom of the left menu).
Enable the toggles the addon asks for. The pack's description usually names them — commonly the scripting/Beta APIs option, and sometimes others like Holiday Creator Features or custom biomes.
Load the world. Minecraft warns that experimental worlds may not be upgradable later — that's expected for script content.

If the addon page says nothing about experiments, you probably don't need them. Turn them on only when a pack requires it, because experimental worlds carry that upgrade caveat.

"It installed but does nothing" — how to fix it

By far the most frequent problem, and it's almost never a broken file. Walk this in order:

Is the behavior pack actually activated? Re-open the world's edit screen → Behavior Packs. If it's sitting under "available" instead of "active," that's your answer. Tap it → Activate.
Is the resource pack activated too? Same screen, Resource Packs tab. Both halves must be on for a full addon.
Did you enable the right Experiments? Script addons quietly do nothing without their toggle. Re-check the description for what it needs.
Is your Minecraft version new enough? This is the sneaky one. An addon built for a newer release can fail silently on an older app. If a pack requires a higher minimum engine version than your game, it may import but never run. Update Minecraft from the Play Store and try again.
Did you actually make a new world after activating? Some content (structures, mobs that spawn naturally) only appears in newly generated chunks. Explore fresh terrain or start a new world to see it.

Version mismatch is invisible. Minecraft rarely throws a clear "this addon is too new" error — it just imports and then the content never shows. If everything is activated and it still does nothing, update the game first before assuming the file is bad.

"It won't import at all" — the wrong-extension trap

If tapping the file gives you "unknown pack," an "invalid" error, or nothing happens, the usual culprit is the file extension not matching the file's structure:

A single pack renamed to .mcaddon when it should be .mcpack (its manifest is at the root, so the game expected a single pack).
A multi-pack bundle renamed to .mcpack when it should be .mcaddon (the packs live in sub-folders, so a single-pack import chokes).
A file that's really a plain .zip — Minecraft won't open it until it's renamed to the correct pack extension.

Reuploaded and repacked files are where this goes wrong most, because someone zipped it up by hand and guessed the extension. Renaming can fix it if you know which type it truly is — but honestly, the cleaner fix is to grab the file from a source that names it correctly in the first place. That mismatch is exactly the kind of thing I fix on the catalog side so the download you get already imports cleanly.

Full troubleshooting checklist

When an addon fights you, run down this list — it catches the vast majority of cases:

File finished downloading (not a partial/interrupted download).
Extension matches the content: .mcpack single, .mcaddon bundle, .mcworld world.
Opened with Minecraft, and you saw the import confirmation.
Behavior pack activated in the target world.
Resource pack activated in the same world.
Required Experiments / Beta APIs toggled on (script addons only).
Minecraft updated to a version the addon supports.
It's a Bedrock file — not a Java .jar, which will never import here.

Still stuck after all that? My step-by-step install Bedrock addons guide has the same flow with screenshots of the exact menus, and the addon not showing up fix digs into the trickier "it's active but invisible" cases. For maps specifically, see installing Bedrock maps.

The one-tap way to skip the file wrangling

Most import headaches come from bad downloads — partial files, wrong extensions, hand-repacked zips from random reupload sites. That's the part I built the MC Bedrock Mods app to remove. It pulls addons, maps, skins and texture packs from established community libraries, hands you the correct file with the correct extension, and lets you open it straight into Minecraft. You still activate the packs in your world — no app can do that step for you, because it lives inside Minecraft — but everything up to that point becomes a single tap.

Get clean, correctly-packed addons in one tap

Free on Google Play. Download, open, and let Minecraft import — then just activate in your world.

Get MC Bedrock Mods

If you'd rather start from a set of packs already chosen to play well together, my curated Setups bundle addons that fit — a themed pick where you don't have to guess what conflicts. And if you're still deciding what kind of content is even worth installing, the best Bedrock addons by category is a good next read.