MineBrushMinecraft Bedrock · File formats
A Bedrock filename can tell you whether Minecraft is being handed a pack, a bundle, or a complete world. It cannot tell you whether the file is trustworthy, current, compatible, or safe for your favorite save.
Quick answer
.mcpackis a zipped resource pack or behavior pack..mcaddonis a ZIP container that can hold.mcpackor.mcworldfiles for distribution..mcworldis a ZIP archive containing the files needed to load a Bedrock or Minecraft Education world.
Those are the current Microsoft-documented roles. The extension helps you choose the expected destination; it does not prove what is actually inside an uninspected download.
Compare the three Bedrock containers
| Extension | Documented role | Expected destination | Do not assume |
|---|---|---|---|
.mcpack |
One zipped resource or behavior pack | Resource Packs or Behavior Packs for a world | That it contains both layers or every dependency |
.mcaddon |
A distribution ZIP containing .mcpack or .mcworld files |
One or more included pack/world components | That every add-on has exactly two packs or one fixed import order |
.mcworld |
A complete Bedrock/Education world archive | A world import rather than a pack toggle | That its bundled content is reusable in another world |
Choose by what you are trying to add
If the creator is sharing one visual or behavior layer, .mcpack matches that job. If several related pieces need to travel together, the creator may use .mcaddon. If the download is a playable build, adventure, template-derived save, or showcase world, .mcworld matches the expected world destination.
Use the creator's release description as the second half of the decision. A suffix without a source page is not enough. Record the exact filename, creator, supported Bedrock version, and whether the creator expects a resource pack, behavior pack, world, or multiple pieces.
Run a safe preflight before opening the file
- Confirm Bedrock Edition. Java resource packs, mods, data packs, and shader files do not become Bedrock packages when renamed.
- Use the creator's original release page. Avoid copies that remove the license, installation note, dependency list, or version history.
- Keep the original filename and extension. Renaming changes the label, not the package structure.
- Check the creator's supported game build. “Bedrock” alone is not an exact compatibility statement.
- List every expected piece. A behavior pack can depend on a resource pack, and a combined package can expose more than one imported entry.
- Copy an important world before activation. Keep the backup outside the active world's normal save path.
Import and activation are separate checkpoints
A package can be recognized without being active in the world you intend to play. Minecraft Help places add-on activation in a world's Resource Packs or Behavior Packs settings, where the player selects an available pack and chooses Activate.
That gives you two questions instead of one:
- Did the expected content become available? Look for a world when the file is
.mcworld; look in the relevant pack lists when the content is a resource or behavior pack. - Is the intended pack active in the intended world? Open that world's settings and check the Resource Packs and Behavior Packs sections separately.
For Realms, official Minecraft Help documents activation in the selected Realm world slot and an upload step after the change. That does not prove every externally acquired package works on every Realm, platform, or device.
Use the failure point to choose the next check
| What happened | Likely layer | Next useful check |
|---|---|---|
| The device does not offer Minecraft as an opener | Platform/file-picker support or wrong extension | Use the creator's device-specific instructions; do not force compatibility by renaming. |
| Minecraft reports an import failure | Incomplete download, invalid structure, unsupported build, or an error page saved as a file | Return to the original source, compare the exact filename and size if the creator publishes them, and download again. |
| Import succeeds but nothing appears in the pack list | Wrong expected destination | Check whether the file was actually a world or whether the bundle exposed another named component. |
| Two packs appear | A combined add-on supplied resource and behavior layers | Check the creator's required pairing and activate the intended layers in the same test world. |
| The pack is visible but its feature is missing | Not activated, wrong order, missing dependency, experiments, or unsupported version | Read the exact release requirements and test the package alone in a copied or disposable world. |
| A world imports but is not in pack settings | Correct .mcworld destination |
Look in the world list; do not expect a complete world to behave like a reusable pack. |
Do not use extension renaming as a converter
A normal ZIP, Java JAR, image, or damaged download does not become a valid Bedrock package because its name ends in .mcpack. The documented extensions describe expected internal structures. If the creator distributes a plain ZIP for manual use, follow that creator's documented route instead of inventing a direct-import package.
Back up for behavior and world changes
Resource packs mainly change presentation, while behavior packs can change game behavior and a .mcworld can contain a complete save. Those broad roles do not predict removal safety for a specific package. Make a world copy before first activation, add one package set at a time, save and reopen the test copy, and keep the last known-good files until the update is proven.
FAQ
Is .mcaddon always better than .mcpack?
No. .mcaddon is useful as a distribution container for related pieces. A single resource or behavior pack may only need .mcpack.
Why did one .mcaddon create several entries?
Microsoft defines .mcaddon as a container that can hold other packages. The creator's release notes should identify which imported pieces belong together.
Can I unzip a .mcworld?
It is ZIP-based internally, but ordinary players should use the supported world-import route. Extract only for a documented creator/development workflow and only after preserving the original file and world backup.
Does a successful import mean the add-on works?
No. Availability, activation, dependency resolution, version support, world load, save persistence, and gameplay are separate checkpoints.
Do consoles support external files?
External import and file-picker access vary by platform and policy. Use the current instructions for that exact device; do not treat a mobile or Windows workflow as a console guarantee.
What this guide does not verify
MineBrush checked Microsoft's current format definitions and Minecraft Help activation steps but did not inspect or run a package. Creator identity, license, archive integrity, manifests, dependencies, experiments, device import, Realms behavior, persistence, performance, and multiplayer remain unknown for every specific file.
Official sources checked
Browse Bedrock add-ons, or use the Bedrock add-on troubleshooting checklist when the package imported but the feature still does not work.
PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.