App Inventor AIA Project Viewer
Inspect original App Inventor project properties, screens, SCM form definitions, BKY blocks and packaged assets. Browse readable form JSON in aia.json and the original block XML.
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.
AIA-SUMMARY.txt aia.json files/youngandroidproject/project.properties files/src/appinventor/example/Screen1.scm files/src/appinventor/example/Screen1.bky files/assets/kitty.png
Supported variants and limits
AIA already contains project source. This does not reconstruct an AIA from an arbitrary APK, compile an app or execute blocks. Missing screen, block and asset references are reported without network requests.
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.