Minecraft Add-on Validator: Check .mcaddon & .mcpack
Updated 29 Sep 2026
Find out why your Bedrock add-on won't import or work. Drop a .mcaddon, .mcpack or .mcworld and get a plain-English list of what to fix. Free, no upload.
An add-on that "doesn't work" in Minecraft Bedrock usually has a small mistake the game never tells you about. A missing comma breaks a whole JSON file. A texture path points at a file that isn't in the pack. Two packs share one UUID, the manifest has no min_engine_version, or pack_icon.png isn't square.
This validator runs Mojang's own add-on checks, the same rules behind Minecraft Creator Tools, right in your browser. Drop in a .mcaddon, .mcpack, .mcworld or .zip and it opens every pack inside: the manifest, the entity, item and block files, textures, sounds and language files. You get a short answer ("Looks good" or "3 problems to fix") and a list sorted into errors, warnings and tips. Each item says what's wrong in plain words, how to fix it, and which file (and for JSON typos, which line) it's in. Passed checks stay hidden. "Copy report" puts the whole list on your clipboard so you can paste it into a Discord help channel. Your file never leaves your device.
How to use
- Tap Choose file (or drop the file on the box) and pick your .mcaddon, .mcpack, .mcworld or .zip.
- Wait a few seconds while it reads the packs and runs the checks.
- Fix everything under Errors first; those can stop the add-on from importing or working.
- Look at Warnings; tips are optional clean-ups.
- Fix the files, zip them again and check the new file, or tap Copy report to ask for help.