Minecraft Bedrock "Import Failed" and "Duplicate Pack" Errors: Causes and Fixes

You tap an add-on, Minecraft opens, and instead of "Successfully imported" you get a red error. It looks scary, but there are only a handful of reasons it happens, and each one has a simple fix. Here is how we track them down when someone reports a broken download.

"Duplicate pack detected"

Every pack has a hidden ID (a UUID) and a version number inside its manifest.json file. If you import a pack whose ID and version match a pack you already have, Minecraft refuses it, because as far as the game knows it is the same thing.

This usually means one of two things:

• You already installed this exact add-on earlier. In that case you don't need to do anything: it is already in your library. Just activate it in your world.
• The creator changed the add-on but forgot to raise the version number. The game still sees the old copy as identical.

How to fix it

1. Open Minecraft and go to Settings > Storage.
2. Look under Resource Packs and Behavior Packs for the add-on's name.
3. Select the old copy and delete it. Do this for both packs if the add-on has two.
4. Import the file again.

Worlds that used the old pack will pick up the new one automatically, because it has the same ID.

If you build add-ons in GodCraft, you shouldn't run into this with your own work. The app keeps the same pack ID for an add-on and raises its version every time you export, so installing a newer build simply updates the old one.

"Import Failed" (or "Unable to import")

This one is less specific, so work through these causes in order. In our experience the first two cover most cases.

1. The download is incomplete or corrupted

A file that stopped downloading halfway can't be unpacked. Check the size: an add-on of a few kilobytes when the page says several megabytes is a clear sign. Delete it and download again, ideally on a stable Wi-Fi connection.

2. The file is really a .zip with extra folders inside

Minecraft expects the pack files (manifest.json, pack_icon.png and the pack folders) at the top level of each pack. Some creators zip a folder that contains another folder, and the game can't find the manifest. If you are on a computer, you can open the archive and check: each pack folder should have manifest.json directly inside it. If it is buried one level deeper, zip the inner folder instead and rename the result to .mcpack.

3. The manifest has an error

A missing comma or a typo in manifest.json is enough to fail the whole import. You can't fix this from a phone easily; the honest answer is to tell the creator in the comments. If it's your own pack, run the JSON through any validator and look for the line it complains about.

4. The file is the wrong kind

Skin packs, worlds and world templates import fine on their own, but if someone renamed a world to .mcpack (or the other way round), Minecraft will reject it. Check the description of the download for what it actually is.

5. Not enough storage

On phones that are nearly full, the game can't unpack the add-on. Free up some space and try again. Big texture packs at 128x or higher resolution can need a few hundred megabytes while importing.

It imported, but the world won't load it

A few related messages show up only when you try to activate the pack:

• The pack needs a newer version of Minecraft. The add-on was built for a newer game version than yours. Update Minecraft from your app store. On GodCraft, every post lists the Minecraft versions it works on, so check that before downloading.
• Missing dependency. The behavior pack expects its matching resource pack (or the reverse). Make sure you imported the full .mcaddon and not just one of its packs.
• The world needs experiments. Some add-ons rely on features that are still experimental. The add-on's description should say which toggle to turn on.

How to see what is actually wrong

Minecraft has a built-in log that explains most pack errors in plain words, it's just hidden by default.

1. Go to Settings and open the Creator section.
2. Turn on Enable Content Log GUI.
3. Load the world with the add-on. Errors now appear on screen, usually naming the exact file and line.

Even if the log text looks technical, copying it into a comment on the add-on's page helps the creator fix it quickly. It's the single most useful thing you can send them.

Quick checklist

• File ends in .mcaddon or .mcpack, not .zip.
• Download size looks right.
• Old copy deleted from Settings > Storage if you see "Duplicate pack".
• Minecraft is up to date.
• Both packs activated in the world.

If you go through all of that and it still fails, leave a comment on the post with your device, your Minecraft version and the exact error text. That gives the creator everything needed to reproduce it.