Few things are more annoying than downloading an addon, tapping the file, watching Minecraft launch, and then getting a red Import Failed message a second later. The good news is that this error almost never means the addon is broken. It usually means one of five very specific things went wrong, and each one has a quick fix.
This guide walks through every import error we see in our support messages, what causes it, and what to do about it.
A real .mcaddon or .mcpack file is just a zip archive with a different extension. If your browser saved it as addon.mcaddon.zip or addon.zip, Minecraft will not know what to do with it.
Open your file manager, find the download, and rename it so it ends in exactly .mcaddon (or .mcpack). On Android, some file managers hide extensions, so turn on "show file extensions" in the settings first. Then tap it again.
The reverse also happens: some sites hand out a .zip that contains two folders inside. That is not broken either. Extract it, and you will usually find a behavior pack folder and a resource pack folder you can import one at a time.
Minecraft expects to find manifest.json right at the top of each pack. If the creator zipped the folder around the pack instead of the pack contents, the manifest ends up one level too deep and the game cannot read it.
Extract the file, open the folder, and check whether manifest.json sits directly inside. If you see another folder first, zip the contents of that inner folder instead, then rename the zip to .mcpack. We check our own downloads for this before publishing, but it is the most common problem with random reuploads from elsewhere.
Every pack has a unique ID (a UUID) in its manifest. If you already have an older copy of the same pack installed, Minecraft refuses to import a second one with the same ID and version.
Go to Settings → Storage (older versions call it Storage under General), open Resource Packs and Behavior Packs, and delete the old version of the addon. Then import the new file. Your worlds are not deleted by this; you just need to re-apply the pack to any world that used it.
Each manifest lists a min_engine_version. If your Minecraft is older than what the addon was built for, the import can fail or the pack can show up with a red warning triangle.
Update Minecraft from the Play Store, App Store or Microsoft Store. Most of our addons target the current stable release, and the version requirement is listed on each project page.
Modern versions of Minecraft on Android store packs in the app's own data folder instead of the shared games/com.mojang folder people remember from years ago. Old tutorials that tell you to copy folders by hand into the old location simply do not work anymore, and Android restricts access to the new location.
Skip manual copying. Tap the .mcaddon or .mcpack file directly, or use your file manager's "Open with → Minecraft" option. If nothing happens, try opening the file from the Files by Google app, which hands files to Minecraft reliably.
Safari downloads land in the Files app. Open Files → Downloads, long-press the addon, tap Share, and choose Minecraft from the app row. If Minecraft is not listed, scroll to the end of the row and tap "More".
If a zip tool or the Microsoft Store grabs the file, right-click it, choose Open with, and pick Minecraft. Tick "Always use this app" so you never have to do it again.
A successful import only means the pack is installed. It still has to be activated on a world. That is a separate problem with its own checklist, which we cover in Why Your Minecraft Addon Isn't Working.
Every FleetMc Studio addon is tested before it goes live.
Browse tested addons