Home Tools About

Minecraft Bedrock Pack Structure Checker

Drop your .mcpack or .zip add-on and see whether the folder layout matches what Bedrock expects — before the game silently refuses it.

Ad space

Check your pack

The archive is read entirely on your device — nothing is uploaded.

Results

Drop a pack to see structure results.

      How to use the pack structure checker

      Drop in the pack

      Drag your .zip, .mcpack, or .mcworld onto the box, or click to browse. The ZIP is parsed locally — compressed and uncompressed entries are both supported.

      Read the checks

      Errors mean Bedrock will likely refuse the pack: no manifest.json in the root, a script entry file that does not exist, or entries escaping the root. Warnings are things to clean up, like __MACOSX folders and .DS_Store files. Notes are observations, such as a missing textures folder.

      Fix the layout

      Move manifest.json to the pack root with the exact lowercase name, place script entry files where the manifest points, and remove junk entries before sharing.

      Re-zip and import

      Zip the pack folder's contents (not the folder itself) and rename to .mcpack for resource packs or .mcaddon for combined packs. Import into Minecraft and it should load cleanly.

      Pack structure checker FAQ

      What does the pack structure checker look at?

      It reads the ZIP entries directly: whether manifest.json exists at the pack root and is valid JSON, whether script module entry files exist, whether expected resource or behavior subfolders are present, and whether junk files like __MACOSX or .DS_Store slipped in.

      Is my pack uploaded anywhere?

      No. The archive is parsed entirely in your browser — the file never leaves your device and no server is involved.

      Which file types can I check?

      Any ZIP-based Bedrock pack: .zip, .mcpack, .mcworld, and .mcaddon. An .mcaddon is a container holding other pack archives, so the checker notes that and asks you to check each pack inside separately.

      Why does it say manifest.json is missing?

      Bedrock expects a file named exactly manifest.json in the pack root. If it is nested in a subfolder, has a different name, or differs in case, the game will not load the pack — the checker flags any of those.

      What are stored and deflated entries?

      They are ZIP compression methods: stored (method 0) is uncompressed and deflate (method 8) is compressed. Both are normal. Reading deflate entries uses the DecompressionStream API, available in Chrome 103+, Firefox 113+, and Safari 16.4+.

      What is a junk entry?

      Files like __MACOSX folders, .DS_Store, and Thumbs.db are created by macOS and Windows when zipping folders. They are harmless but bloat the pack and look unprofessional — the checker warns so you can remove them.