Minecraft MCADDON Viewer and Extractor

Inspect Bedrock addon containers, including directory-style packs and nested MCPACK archives. Each nested pack retains its manifest and original asset tree.

Drop your .mcaddon file here
Choose file

⚠ Drag-and-drop upload could not load — an ad blocker is most likely blocking it. Please disable your ad blocker and reload the page to upload a file.

Browse metadata, source and assets

Processing runs on our servers. Upload a package to browse its extracted files and readable format report, inspect partial results, download individual files or download the complete result ZIP. Extraction and supplied source viewing are identified separately from bytecode recovery.

minecraft.json
files/behavior.mcpack
recovered/behavior.mcpack/minecraft.json
recovered/behavior.mcpack/files/scripts/main.js

Supported variants and limits

Nested packs share the parent time, byte and entry limits. Packs and scripts are never imported or executed. Referenced dependencies are not downloaded; encrypted Marketplace content is not decrypted.

Shared defaults are five minutes per job, 1 GiB expanded data, 256 MiB per member, 25,000 entries and four nested layers. Metadata reads are bounded to 4 MiB. Each nested compression or container layer shares these limits. Larger or damaged inputs can produce partial results; DECOMPILATION-NOTES.txt and extraction.json explain skipped files and recovery outcomes.

Related inspectors: DEB, RPM, macOS PKG, MCPACK, MCADDON, MCWORLD and MCTEMPLATE, Scratch, App Inventor and Unity packages.

For Unity runtime .assets, .bundle, .assetbundle or .unity3d files, use the Unity runtime asset extractor. For compiled applications, use the Java decompiler or APK decompiler.