Add-ons not working in Minecraft Bedrock almost always comes down to one of a handful of causes, and most take a minute or two to fix. Work through them in this order, since it roughly matches how often each one turns out to be the real problem: activation, pairing, experiments, version match, then platform quirks on Realms and consoles.
Turn on the add-on in your world
Importing a pack does not turn it on. Minecraft Bedrock keeps every pack you import in a library and applies none of them automatically, so an add-on can sit there fully installed and still do nothing until you switch it on. This is by far the most common reason an add-on looks broken. It is worth checking first even for a large, well-known add-on like Modern Furniture, where nothing places or crafts differently until the pack is active.
How do I activate add-ons in Minecraft Bedrock?
- 1.Open Settings, then Global Resources, to apply a pack to every world you create from now on.
- 2.Open one specific world, choose Edit, then Resource Packs or Behavior Packs, to apply a pack to just that world.
- 3.Move the pack from the inactive list into Active using the arrow next to it.
- 4.Save and reopen the world so the change takes effect.
If the add-on has both a resource pack and a behavior pack, both need to move into Active separately. Turning on only one half is common enough that it gets its own section next.
Pair the behavior pack with its resource pack
Plenty of Bedrock add-ons ship as two files, a behavior pack that changes rules, entities, or mechanics, and a resource pack that supplies the models, textures, or sounds those changes need. Activating only one half leaves the other doing nothing. More Body Actions is explicit about this: it ships as two separate .mcpack files, and both need to be applied to the same world at the same time before sitting, crawling, or climbing will work.
- Check the download for more than one file, or a folder split into a behavior pack and a resource pack.
- Activate both halves in the same world, not just the one that sounds relevant.
- If only textures changed or only mechanics changed after activating, the other half is still inactive.
Turn on the experiments the add-on needs
Some add-ons rely on Bedrock features that stay behind an Experiments toggle in world settings, even once the pack itself is fully active. Beta APIs is the one that trips people up most, since it gates any add-on built on Bedrock's scripting system. WorldEdit for Bedrock needs Beta APIs turned on to work at all. Without it, the pack imports and activates cleanly, and every command still silently does nothing.
- Open Edit World, then Experiments, before creating or opening the world.
- Turn on Beta APIs for scripting-based add-ons.
- Turn on Holiday Creator Features for older entity, block, and biome add-ons that predate the newer format.
- Check the add-on's own install notes for the toggle it actually needs. Not every add-on needs one.
Match the add-on version to your game
Every Bedrock pack declares a min_engine_version inside its manifest.json file. If that number is newer than the Minecraft version installed on your device, Bedrock refuses to activate the pack, even though it imports without an error. Update Minecraft Bedrock through your platform's store, or check whether the add-on has an older release that matches your version. WorldEdit for Bedrock, for example, currently targets Bedrock 1.21.130, so an install running an older release will not run it.
This is also why an add-on that worked fine last month can suddenly stop after Minecraft updates itself. The pack has not changed, but the version gap has opened up in the other direction.
Add-ons on a Realm
Add-ons work on Realms, but only when applied correctly. Turn the packs on inside the Realm's own world settings, not just your local copy, and upload from a world where the packs are already active rather than trying to add them afterward. Once a pack is applied to the Realm's world, every player who joins gets it automatically. Nobody else on the Realm needs to install or activate anything themselves.
Better Foliage shows the split well. Its resource pack is purely visual, so a player can turn it on locally without the Realm owner doing anything. Its behavior pack changes actual world content, like falling leaves and plant growth, so that half has to be enabled by whoever owns the Realm before it affects anyone.
Add-ons on Xbox, PlayStation, and Switch
Sideloading a custom add-on is not possible on console. Xbox, PlayStation, and Switch only run add-on content bought or claimed through the in-game Marketplace, and a .mcaddon or .mcpack file downloaded from a creator site has no supported way onto those platforms. If you're troubleshooting on console specifically, the fix usually is not a settings toggle. The content needs to come from the Marketplace instead.
Update an add-on without a stale copy winning
How do I update add-ons in Minecraft Bedrock?
Import the new version the same way you imported the original, then remove the old version from Settings, Global Resources, or from the world's pack list. Bedrock does not always overwrite an existing pack automatically, and when it does not, the outdated copy can keep loading in place of the update, especially when both share the same pack name.
- 1.Download and import the new .mcpack or .mcaddon file.
- 2.Open the pack list and confirm the new version now appears.
- 3.Remove the old version so it cannot load in its place.
- 4.Reopen the world to confirm the updated version is the one running.
Where add-on files live
On Windows, Bedrock stores every imported pack under %appdata%\Minecraft Bedrock\users\shared\games\com.mojang, inside resource_packs, behavior_packs, and, for packs you are actively developing, development_resource_packs and development_behavior_packs. Checking this folder directly is the fastest way to confirm whether an import actually landed.
On mobile, the app sandbox makes that folder hard to reach without extra tools, so we won't guess at a path here. Importing a downloaded .mcpack file directly through the file's share menu is the supported route on phones and tablets, and it lands in the same place the in-game import screen would put it.
Frequently asked questions
Why are my add-ons not showing up in Minecraft Bedrock?
Usually the import worked but activation did not happen. Check Settings, Global Resources for a pack meant for every world, or Edit World, Resource Packs and Behavior Packs for a pack meant for one world. If the add-on has two files, confirm both moved into the active list, not just one.
Why are my mods not working in Minecraft Bedrock?
Bedrock does not support code-level mods the way Java Edition does with Fabric or Forge. What people call mods on Bedrock are add-ons, built from resource packs and behavior packs, so the fix is the same as everywhere else on this page: activate the pack, pair both halves if it has two, and turn on any Experiments the add-on needs.
Why are my mods not working in Minecraft PE?
Minecraft PE is the old name for Bedrock Edition on mobile, and the platform works the same way it does everywhere else Bedrock runs. What downloads as a mod for PE is really a resource pack, a behavior pack, or both. Import it, then activate it in Settings or in the world's Edit menu, since importing alone never turns a pack on.
Why are my add-ons not working in Minecraft?
If you've gone through activation, pairing, experiments, and version match and an add-on still does nothing, the problem may not be the add-on at all. Crashes, freezes, and worlds that won't open point at the game itself rather than a specific pack. The Minecraft Beginner Troubleshooting Checklist covers those causes.
Why is my texture pack not working in Minecraft Bedrock?
A texture pack is what most players call a resource pack. It follows the same activation rules as any other pack: import it, then move it into Active under Settings, Global Resources, or under the world's Edit, Resource Packs menu. If the texture pack is part of a larger add-on, check whether it depends on a paired behavior pack. Missing textures on entities or blocks the behavior pack adds is a pairing problem, not a texture pack bug.
Once activation, pairing, experiments, and version all check out, the fix is almost always found. Browse our full Bedrock add-ons list for source-linked downloads and version notes on everything we cover.
