Diagnose by symptom
The symptom tells you which cause to check first.
・Tap or click does nothing → file association (cause 1)
・"No app supports this file type" → file association, or you're trying Java Edition (cause 1 or 3)
・Minecraft opens but the pack never imports → corrupted download (cause 2), or an old version (cause 4)
・Pack imported but doesn't apply in-world → you need the two-step Global + per-world activation (cause 4)
The rest of this guide walks through each cause and its fix.
Cause 1: the file association doesn't point to Minecraft
.mcpack is a Minecraft Bedrock-only extension. Your OS has to know that this file type opens with Minecraft. If a ZIP utility or file manager grabbed the association, tapping does nothing.
iOS / iPadOS: download via Safari or Mail, then use the share sheet and choose "Minecraft". If that doesn't appear, open the Files app and long-press the .mcpack. Then tap Share and choose Minecraft. If Minecraft still isn't listed, reinstall Minecraft (Bedrock) from the App Store.
Android: download via Chrome or Firefox, and the notification bar usually offers "Tap to open". If not, open a file manager such as Files by Google. Go to Download, tap the .mcpack, and pick Minecraft from the "Open with" dialog. If another app like WinRAR or ZArchiver is set as the default, clear that default in app settings and pick Minecraft again.
Windows: double-click the .mcpack in Explorer, and Minecraft Launcher should open. If it doesn't, right-click it. Choose Open with, then Minecraft Launcher. If Minecraft Launcher isn't listed at all, confirm Minecraft (Bedrock) is installed via the Microsoft Store.Cause 2: the download was interrupted and the file is incomplete
An interrupted download leaves a partial
.mcpack that's smaller than it should be. Minecraft opens the file and reads manifest.json from inside the ZIP. The archive is corrupt, so it fails and stops with an import error.
Check the file size first. A few kilobytes, when the source says several megabytes, points clearly to corruption. On cellular for a large pack, switch to Wi-Fi and re-download. Most browsers can resume an interrupted download if you trigger it again.
Did you export the pack from PackAnvil and it still won't import? Check that your browser's save dialog didn't rewrite the extension to .zip. Keep the extension as .mcpack.Cause 3: you're trying to open it in Java Edition
One distinction matters most:
.mcpack is exclusive to Bedrock Edition (the modern unified Minecraft). Java Edition (the original PC Minecraft) does not read .mcpack files. Java resource packs are .zip and use a completely different internal structure.
Here's how to tell which edition you have:
・The main menu has a "Marketplace" button → Bedrock (.mcpack works)
・It launches straight from the Mojang logo into a window with an English "News" panel → likely Java (.mcpack won't work)
On Windows with both installed, check Task Manager. Minecraft.Windows.exe is Bedrock, and javaw.exe is Java.
You could unzip a Bedrock .mcpack, rewrite the manifest, and reassemble it as a Java .zip. But texture paths differ between editions, so it usually won't render correctly. Just launch the right edition instead.Cause 4: outdated Minecraft, or you missed the per-world activation
Older Minecraft Bedrock builds (pre-1.16 especially) don't recognize newer
manifest.json format_version values. Check for updates in the App Store, Google Play, or Microsoft Store. Run the latest version before trying again.
The other common case: the pack imported fine but never shows up in your world. Bedrock applies resource packs in two steps. Adding a pack to Global Resources does not auto-apply it to every world.
The flow is:
・Settings → Global Resources → enable the pack
・Play → edit the target world → Resource Packs → activate the pack for that world too
Global does not mean active everywhere.When nothing works, rebuilding in PackAnvil is faster than debugging
Old
.mcpack files from third-party sites often won't run on the current Bedrock release. The manifest format is outdated, or texture paths point to files that no longer exist. At that point you can chase every cause above and still get nowhere.
The PackAnvil builder lets you assemble a PvP-focused Bedrock texture pack in your browser in about five minutes. Pick the 16x preset, swap crosshair, HUD, and sword styles to taste, and export. The output always uses the current Bedrock manifest format, so it removes one whole class of failures.
In practice, rebuilding the equivalent in PackAnvil beats working through every possible cause of a broken .mcpack. If a PackAnvil-exported .mcpack still won't open, only two suspects remain: cause 1 (OS file association) and cause 4 (Minecraft version).