Diagnose by symptom
The symptom tells you which cause to investigate first.
・Tap or click does nothing at all → file association issue (cause 1)
・"No app supports this file type" error → association issue or you're trying Java Edition (cause 1 or 3)
・Minecraft opens but the pack never imports → corrupted download (cause 2) or 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 the article walks through each cause and its fix.
Cause 1: 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 has hijacked the association, tapping does nothing.
iOS / iPadOS: download via Safari or Mail and use the share sheet → "Minecraft". If that doesn't appear, open the Files app, long-press the downloaded .mcpack, then Share → Minecraft. If Minecraft still isn't listed, reinstall Minecraft (Bedrock) from the App Store.
Android: when you download via Chrome or Firefox the notification bar usually offers "Tap to open". If not, open a file manager (Files by Google), navigate to Download, tap the .mcpack, then choose Minecraft from the "Open with" dialog. If a different app (WinRAR, ZArchiver) is set as the default, clear the default in app settings and pick Minecraft again.
Windows: double-click the .mcpack in Explorer — Minecraft Launcher should open. If it doesn't, right-click → Open with → Minecraft Launcher. If Minecraft Launcher isn't listed at all, confirm Minecraft (Bedrock) is installed via the Microsoft Store.Cause 2: download was interrupted, file is incomplete
An interrupted download leaves you with a partial
.mcpack that's smaller than it should be. Minecraft opens the file, reads manifest.json from inside the ZIP, fails because the archive is corrupt, and bails out with an import error.
Check the file size. A few kilobytes when the source says several megabytes is a clear sign of corruption. On cellular networks for large packs, switch to Wi-Fi and re-download. Most browsers can resume an interrupted download if you trigger it again.
If you exported the pack from PackAnvil and it still won't import, double-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
Critical distinction:
.mcpack is exclusive to Bedrock Edition (the modern unified Minecraft). Java Edition (the original PC Minecraft) does not read .mcpack files at all — Java resource packs are .zip and use a completely different internal structure.
How to tell which edition you have:
・Main menu has a "Marketplace" button → Bedrock (.mcpack works)
・Launches straight from the Mojang logo into a window with an English "News" panel → likely Java (.mcpack won't work)
On Windows where you have both installed, check Task Manager: Minecraft.Windows.exe is Bedrock, javaw.exe is Java.
You could in theory 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. Easier to just launch the right edition.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 / Microsoft Store and run the latest version before trying again.
The other common case: the pack imported fine but doesn't actually show up in your world. Bedrock applies resource packs in two steps. Adding a pack to Global Resources doesn't auto-apply it to every world. The flow is: Settings → Global Resources → enable the pack → then in Play → edit the target world → Resource Packs → activate the pack for that world too. Global ≠ active everywhere.When all else fails, rebuilding in PackAnvil is faster than debugging
Old
.mcpack files from third-party sites often won't run on the current Bedrock release. Outdated manifest format, texture paths that don't exist in the current version — 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 / sword styles to match what you want, and export. The output always uses the current Bedrock manifest format, so you eliminate one entire class of failures.
In practice: rather than work through every possible cause of a broken .mcpack, rebuilding the equivalent in PackAnvil is faster. If a PackAnvil-exported .mcpack still won't open, the remaining suspects narrow to cause 1 (OS file association) and cause 4 (Minecraft version).