ADD-ONS
Install, create, and manage Bedrock Edition add-ons and behavior packs.
4 guides in this category
What Are Bedrock Edition Add-ons?
Introduction to the Bedrock Edition add-on system, including behavior packs, resource packs, and the scripting API.
How to Install Add-ons on Bedrock Edition
Step-by-step instructions for installing add-ons, behavior packs, and resource packs on every Bedrock platform.
Best Bedrock Edition Add-ons Worth Installing
A curated list of high-quality Bedrock Edition add-ons across categories including gameplay, visual enhancements, and quality of life improvements.
Bedrock Behavior Packs: Creating Your First Pack
Learn how to create a behavior pack for Bedrock Edition from scratch, including manifest setup, entity modifications, and custom recipes.
What an add-on is made of
Bedrock cannot load Java mods. Add-ons change the game through three official parts instead.
- Resource pack
- Textures, models, sounds and other assets.
- Behavior pack
- Data files that define how entities, items, recipes and loot tables behave.
- Scripts
- JavaScript that reacts to game events. Every script module a pack uses has to be listed as a dependency in its
manifest.json.
Installing one without surprises
A .mcaddon file bundles the packs of an add-on together. Open it and the game imports each pack into the right folder inside com.mojang. The packs still have to be switched on for a world before they do anything.
Some add-ons need experimental toggles. On Bedrock that disables achievements for the world, and an experiment cannot be turned off again once the world has been created with it, so try those add-ons on a copy first.
Add-ons in the Marketplace come from members of the Minecraft Partner Program and are approved by the Minecraft Content Team, or are made together with Mojang Studios as official DLC.
Building and testing your own
Packs you are still working on belong in development_behavior_packs and development_resource_packs inside com.mojang. Microsoft's own workflow copies them there, or links those folders to your project, so there is nothing to import after every change.
Not everything reloads while the world is open. /reload picks up scripts completely and block, entity and item definitions in part, but new textures, models and sounds only show after you leave the world and load it again. Raise the version number in manifest.json with every release and write down breaking changes, because worlds made with an older version of your add-on may not work with the new one.
What Bedrock add-ons are goes deeper into each part, installing add-ons has steps for every platform, the best Bedrock add-ons is a place to start, and your first behavior pack is for making your own.