Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Games & Saves›.mcpack
THE FILE FIELD GUIDE
.mcpack

Minecraft Pack

Games & Saves

MCPACK is a ZIP-structured Bedrock resource/behavior pack. Successful import does not necessarily activate it in a world: enable it in the matching world settings and check dependencies/game versions. It differs from Java packs and does not represent a complete world.

What it is used for
Distributing resource/behavior packs
What the file contains
Binary data
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

Import a pack into Bedrock

Distinguish resource and behavior packs.

  1. Inspect provider, game version and dependencies.
  2. Import a copy into supported Bedrock Edition.
  3. Inspect type/name in the pack lists.
Activate for a world

Import alone may not activate the pack.

  1. Prepare a copy of the world.
  2. Activate required resource/behavior packs.
  3. Verify rendering, behavior and dependencies.
Inspect identity problems

Inspect the manifest on a copy.

  1. Inspect archive layout and manifest.json with appropriate tools.
  2. Compare identity, version and dependencies with documentation.
  3. Use a supported corrected release and retest a world copy.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Imported but unchanged: check activation in the intended world and pack type.
  • Import error: inspect manifest, extra archive nesting, UUIDs and dependencies.
  • Partial behavior: check game version, companion packs and feature requirements.
  • Duplicate update ignored: inspect identity/version.
  • Another pack takes priority: inspect load order/overlapping assets.
  • Inactive after reload: inspect saved world activation.

Edit and repackage a pack

  1. Preserve pack/world originals and edit a copy with appropriate tools.
  2. Repackage according to specifications and test import, activation/dependencies in a copied world.
  3. Package as documented and verify on a copied world.

Renaming arbitrary ZIP is insufficient; Java conversion requires compatible contents/specifications.

Identity and updates

Inspect identity, update requirements and dependencies separately from display name.

Example: test activation through save/reload on a copied world.

Source for these steps：Microsoft / Mojang · Minecraft File Extensions / Microsoft / Mojang · Installing Add-Ons in Minecraft: Bedrock Edition / Microsoft / Mojang · manifest.json for Behavior/Resource/Skin Packs and World Templates

Checks after activation

Test rendering, behavior, dependencies and load priority, including save/reload.

Source for these steps：Microsoft / Mojang · Minecraft File Extensions / Microsoft / Mojang · Installing Add-Ons in Minecraft: Bedrock Edition / Microsoft / Mojang · manifest.json for Behavior/Resource/Skin Packs and World Templates

Related-format differences

Related-format differences
Format / methodRoleWhat to verify
MCPACKIndividual packType/identity/dependencies
MCWORLDWorld saveTest a copy
MCADDONDistribution bundleContained packs

Handling and security

Use trusted providers and test packs with scripts/behavior changes in copied worlds.

Questions and answers

Does import alone change appearance?

Check world activation and dependencies too.

Is this a world backup?

No; it is an individual pack.

Same as a Java resource pack?

No; their specifications differ.

Can a pack change an existing world?

Behavior changes may affect it; test a backed-up copy.

Will changing the UUID fix it?

It can break dependencies/update identity; inspect the cause and use the supported release.

Format facts: name, steward and MIME type
Formal name
Minecraft Bedrock resource / behavior pack archive
Steward / specification
Microsoft / Mojang
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources