Fix Resource Pack Errors in Minecraft Bedrock Edition

If Resource Pack Errors in Minecraft Bedrock Edition leave a pack missing or refusing to activate, leaves blocks unchanged, or crashes Minecraft Bedrock Edition, start by protecting the world and isolating the pack. Back up or copy the affected world, turn off optional add-ons, test the resource pack by itself, then check its folder structure, manifest, and load order. These steps help distinguish a damaged download from an add-on conflict without deleting worlds or changing files you do not own.

The menu names can vary a little by device and release. The core checks below apply to Bedrock on Windows, mobile, and consoles, while manual file editing is intended for packs you created or are authorized to modify.

Identify the resource pack problem

Four fixes for Minecraft Bedrock resource pack errors

1. Back up the world and isolate conflicting add-ons

Several packs can change the same texture, sound, or other asset. A conflict can make a pack look broken even when its files are intact. Minecraft Support recommends backing up the world and disabling add-ons one at a time when troubleshooting.

1. Close the affected world and make a copy or backup using the option available on your device.
2. Open that world's settings and find Add-Ons or Resource Packs. Deactivate optional packs, especially any recently installed or updated pack.
3. Launch the copied world with only the pack you are checking. If it works, re-enable the other packs one at a time, testing after each change.
4. If the issue affects several worlds, also check Settings > Global Resources on platforms that provide that menu. A globally active pack may affect more than one world.

If the crash stops when one pack is disabled, leave that pack off and check for an updated version from its creator. Do not clear Minecraft's app data or delete the entire game folder as an early troubleshooting step; those actions can remove local content. See Minecraft Support's add-on troubleshooting steps.

2. Re-import the pack and check its folder structure

A partial download or an extra folder layer can keep Bedrock from finding the pack manifest. If the creator provides a .mcpack file, use the import or open-with flow supported by your device. If the creator provides a folder, check that manifest.json is directly inside the pack's root folder, beside folders such as textures or sounds.

A common mistake is ending up with a structure like MyPack/MyPack/manifest.json. The outer folder is not the pack root in that case. Open the inner folder and confirm it contains the manifest and the pack's content. Also check that Windows has not silently saved the manifest as manifest.json.txt; turn on file-name extensions to see the full name.

For a custom pack on Windows, Microsoft's current creator documentation describes the development_resource_packs folder under the Bedrock com.mojang directory. That location is for development packs; installed content and paths on other platforms differ. Follow the current official resource-pack setup guide instead of assuming one old folder path works on every device. If a re-download is needed, get the file again from the Marketplace or the pack creator's official source.

3. Validate the manifest for packs you own

The manifest tells Bedrock what the pack is and what it contains. A resource-pack manifest should use format_version 2; this value is not the Minecraft game version. Do not change it to 18 or 21 to match a game release. The separate min_engine_version field describes the oldest game version the pack targets, while individual content files can have their own format versions.

• Confirm the file is named exactly manifest.json and parses as JSON: braces and brackets must match, commas must be in the right places, and JSON comments or trailing commas must be removed.
• Check that the header and resource module each have a UUID, and that the two UUIDs are different. Each new pack needs its own unique identifiers.
• Make sure the module type is resources, and that the version fields follow the required numeric-array format shown in the official example.
• Set min_engine_version to a version your content actually supports. Do not copy a number from an unrelated tutorial; consult Microsoft's current platform guidance when targeting a specific release.

These checks apply to editable packs. Marketplace packs are managed content, so do not try to rewrite their manifests. For field definitions and a complete example, use Microsoft's resource-pack tutorial, manifest reference, and latest platform version guidance.

4. Correct pack order and read the Content Log

If a pack appears active but its textures do not show, move it higher in the active resource-pack list and test again. Bedrock applies packs in an order; another pack loaded later can replace an asset with the same path and filename. Check that the texture is in the expected folder, that its filename matches the reference, and that the file is a real supported image rather than a renamed file.

For creator-made packs, enable the Content Log in Minecraft's Creator settings if it is available on your platform. Reproduce the problem and look for the first error mentioning a file path, JSON parse issue, or missing asset. Fix that specific file, restart or reload the world, and test again. Microsoft's add-on troubleshooting guide explains how to use the log and check syntax and file locations.

If the same pack works in a new local test world but not in a Realm or server, ask the owner which resources are required and whether the server supplies its own pack. A server-managed resource pack may not be editable from your device.

Prevent the same resource pack error from returning

• Keep a backup of important worlds before changing their active packs.
• Install one pack at a time and test it in a copied or new world before combining it with other packs.
• Keep a clean copy of the original download so you can restore it after testing edits.
• Check the creator's compatibility notes and update Minecraft through the official store for your platform.
• Use the Marketplace or the creator's official download page, and avoid repackaged files with unknown changes.
• When two packs edit the same asset, choose which one should take priority rather than assuming both changes will appear.

Frequently asked questions

Does “invalid pack format” mean I need format version 21?

No. For the pack manifest, the current creator guidance specifies format_version 2. A game version such as 1.21.x and format versions inside individual content files are separate versioning systems.

Why is my resource pack active but nothing looks different?

Another pack may be overriding the same asset, or the file path or filename may not match. Move the intended pack higher in the active list, then check the asset path and exact name.

Can I delete the pack folder to fix a world?

Do not start by deleting folders or app data. Back up the world, deactivate the pack in the world's settings, and test again. If you need to remove a custom pack, use the game's controls or the platform's documented file workflow so you do not remove unrelated saved content.