If you searched “mods for Minecraft Pocket Edition,” you’re not chasing an old app. Pocket Edition was folded into Bedrock Edition during 2017’s Better Together update, and every phone, console, and Windows copy of Minecraft you can buy today runs on that same Bedrock engine. Add-ons are the mod system for all of it — one format, every device, no separate “Pocket Edition mods” to hunt down.
Unlike Java Edition, Bedrock never got Forge or Fabric. Add-ons are the only mod path it has, and they work the same way whether you’re grabbing one for free or buying it through the Marketplace. By the end of this guide you’ll have an add-on active in your world, know the one workaround that actually gets custom content onto a console, and know exactly why a pack that “successfully imported” can still do nothing at all.
Verified against the current retail Minecraft: Bedrock Edition build (1.21.80) and Microsoft’s official Add-On documentation as of August 2026. Menu wording may shift with future updates — the underlying steps won’t.
Quick Start: Get an Add-On Working in 6 Steps
- Download a
.mcaddonor.mcpackfile from a trusted source — not a random “Minecraft mod” app from an app store. - On Windows or Android, just open the downloaded file. On iOS, tap it and choose Open in Minecraft.
- Wait for the “Successfully imported” toast — that only means the pack is in your library, not that it’s turned on.
- Open the world you want to use it in and tap Edit (the pencil icon).
- Go to Behavior Packs > Available, tap the pack, then Activate.
- Repeat in Resource Packs > Available, then back out and re-enter the world.
On console? Skip straight to the console section below — sideloading a file isn’t an option there, and the steps above won’t apply until you’ve routed around that.
What an Add-On Actually Is (and Why Half of It Sometimes Doesn’t Work)
An add-on isn’t one file doing one job. It’s two separate packs bundled together, and Minecraft treats them as two separate switches. The Resource Pack handles everything you see and hear — textures, models, animations, particle effects, sound. The Behavior Pack handles everything the game does — how an entity fights, what it drops, what recipes exist, what custom functions run.
A reskinned zombie add-on needs its Resource Pack active to look different and its Behavior Pack active to actually hit harder or drop different loot. Activate only one and you get a mod that looks right but behaves like vanilla, or the reverse — new behavior with the old texture. That mismatch is the single most common “the mod isn’t working” report, and it isn’t a bug. It’s a pack you only half-turned on.
Some creators bundle both packs into one .mcaddon file; others ship two separate .mcpack files. If you downloaded two files, both need to be imported and activated — there’s no combined switch that does it for you.
Installing on Windows, Android, and iOS
Windows is the simplest of the three: download the file, and if it saved as a .zip, rename the extension to .mcaddon or .mcpack. Double-click it and Windows opens it directly in Minecraft, importing it automatically. Power users can also drop pack folders straight into the com.mojang folder under %appdata%\Minecraft Bedrock\users\shared\games\com.mojang, but the double-click method is faster for a single add-on.
Android exposes its file system directly, so open Settings > Storage > Explore (or any file manager app), find the file in your Downloads folder, and tap it to open in Minecraft.
iOS works differently, and it’s worth knowing why: Apple’s sandboxing model doesn’t give apps a raw file browser the way Android does. Instead, you tap the downloaded file — in Safari’s Downloads, an email attachment, or the Files app — and choose Open in Minecraft from the share sheet. It’s an app-to-app handoff rather than a file import, which is why the iOS steps look nothing like the Android ones even though the result is identical: the pack lands in your library either way.
Activating the Pack Inside Your World
Importing only stocks the pack in your library — it still has to be switched on per world. Open the world’s settings (the pencil icon), go to the Behavior Packs tab, find the pack under Available, tap it, and hit Activate. Do the exact same thing under the Resource Packs tab. Back out and re-enter the world so both fully load.
Given the two-switch structure from the previous section, skipping either tab is exactly how you end up with the half-working mod described above — new textures with vanilla behavior, or the reverse.
Console Players: What Xbox, PlayStation, and Switch Can Actually Do
If you’re on Xbox, PlayStation, or Switch, sideloading a .mcaddon file the way PC and mobile players do isn’t possible. Microsoft’s own Add-On installation documentation doesn’t list a direct console install path at all — only a Realms-based workaround. Consoles lock down their file systems, so there’s no Downloads folder to tap a file from in the first place.
Marketplace content is the exception. It ships and installs natively on every current Bedrock console — Xbox One and Series X|S, PS4 and PS5, and Switch. On PlayStation it’s branded the “Store” and uses tokens instead of Minecoins, but the mechanism is the same: buy it, and it’s active with no extra setup.
For a free, custom add-on that isn’t on the Marketplace, the only documented path onto a console runs through Realms:
- On a Windows PC or mobile device with an active Realms subscription, import the
.mcaddonand activate both packs in a world exactly as described above. - Open that world’s Realm settings and upload it (Replace World), pushing the add-on-enabled world to your Realm.
- Sign into the same Microsoft account on your console, launch Minecraft, and join that Realm. The add-ons travel with the world itself rather than being installed on the console separately.
| Player type | Best move |
|---|---|
| New player | Stay on Marketplace — zero setup, works on every device including console. |
| Casual player | Already paying for Realms anyway? Use the relay once; future add-on worlds just need a re-upload. |
| Hardcore / optimiser | Build and test the full add-on stack on PC first, then push the finished world to Realms in one batch instead of re-uploading after every tweak. |
| Completionist | Combine both — Marketplace for console-exclusive content, the Realms relay for community add-ons Marketplace doesn’t carry. |
Marketplace vs. Free Third-Party Add-Ons, by Device
Marketplace is the safer default if you’re not on PC or Android. Free sideloaded add-ons are the better deal everywhere else, as long as you’re pulling them from a moderated community source rather than a random app.
| Marketplace | Free third-party (.mcaddon) | |
|---|---|---|
| Cost | Minecoins (tokens on PlayStation) | Free |
| Platforms | Every Bedrock platform, including all consoles | PC and mobile directly; console needs the Realms relay above |
| Review process | Vetted by Mojang’s Content Team before listing | Unmoderated — quality and safety depend on the source |
| Best for | Console players, anyone who wants zero setup | PC/mobile players chasing free, frequently-updated content |
| Avoid if | You want free content and you’re already on PC or mobile | You’re on console with no Realms subscription |
Not every listing calling itself “Mods for Minecraft PE” is a real add-on, either. Several apps carrying that exact name on the Play Store are repackaged aggregators — they wrap someone else’s .mcaddon files behind ads and broad permissions rather than offering original content. Stick to add-ons hosted on community sites the game’s own creators openly link to, or the in-game Marketplace, and treat a standalone “Minecraft mod” app as a yellow flag rather than a shortcut.
Fixing “It Won’t Turn On”: The Beta APIs Mechanism
If a pack shows Activated in both tabs but still does nothing, the cause is almost always a missing experiment toggle, not a bad install.
Add-ons built with Minecraft’s Script API reference “-beta” versions of API modules — and Mojang’s own description of the Beta APIs toggle is literally “use ‘-beta’ versions of API modules in Add-On packs.” If a creator’s description mentions Script API, GameTest, or @minecraft/server, that toggle has to be on before the behavior pack’s code runs at all, regardless of how correctly you imported and activated it. Turn it on under World Settings > Experiments, confirm “Turn on Experiments anyway,” and re-enter the world.
One trade-off worth knowing before you flip it: activating any experiment on an existing world automatically spins off a separate copy tagged “Copy of [name],” and once a world carries the Experimental tag, Mojang’s own documentation states it can’t be reverted back to non-experimental. Your original save stays untouched, but if you’re not sure the add-on is a keeper, test it on that copy rather than your main survival world.
Conclusion
Bedrock’s add-on system trades the wide-open PC-mod scene for something narrower but universal: the same .mcaddon works whether you’re on a laptop or a Switch, once you route console through Marketplace or the Realms relay. Start with Marketplace if you’re on console or don’t want to touch settings. Sideload if you’re on PC or Android and want to try what the wider community is building. Either way, activate both packs, and check the Beta APIs toggle before assuming an add-on is broken. For the platform this all runs fastest on, see our Best Minecraft Bedrock PC Settings guide, and once add-ons are working, our Best Minecraft Mods 2026 roundup is the next stop. Java players wanting the general install process instead should see How to Install Minecraft Mods.
FAQ
Is Minecraft Pocket Edition different from Bedrock Edition?
No. Pocket Edition was renamed during the 2017 Better Together update, and every mobile, console, and Windows build today runs on the same Bedrock engine. “Pocket Edition” is old branding still baked into how people search, not a separate app or a separate mod system.
Can I install regular Minecraft mods (Forge/Fabric) on Bedrock or Pocket Edition?
No, and this is the most common mismatch we see. Forge and Fabric only run on Java Edition. Bedrock’s only mod system is Add-Ons (.mcaddon/.mcpack) — a Forge .jar file will not open in the Bedrock app on any platform.
Why did my add-on import successfully but do nothing in my world?
Importing only puts the pack in your library. It still needs to be activated separately in both the Behavior Packs and Resource Packs tabs of that specific world, and script-based add-ons additionally need the Beta APIs experiment toggled on. A “successfully imported” toast confirms the file is valid, not that it’s turned on.
Is it worth paying for Marketplace add-ons if free sideloaded ones exist?
It depends on your platform, not on quality — Marketplace content isn’t inherently better than a well-made free add-on, but it’s the only option that works natively on console. If you’re on PC or mobile, go straight to free sideloaded add-ons; if you’re on console and don’t already pay for Realms, Marketplace is your default.
Sources
- Getting Started with Minecraft Add-Ons — Microsoft Learn
- Add-Ons Explained — Bedrock Wiki
- Marketplace — Minecraft Wiki
- Experimental Features in Minecraft: Bedrock Edition — Microsoft Learn
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.