Free tool
AAB inspector: read an Android App Bundle
Drop an .aab to see its modules, package name, version code, min and target SDK, permissions, upload key fingerprints and what Google Play would reject. It runs in your browser, so the bundle is never uploaded.
What it checks
Modules
Every module in the bundle: the base module, feature modules and asset packs, with how each is delivered (install time, fast follow or on demand).
App details
Package name, app name, icon, version name and code, minimum and target SDK, device type, launch activity and native ABIs, read from the protobuf manifest of the base module.
Upload key
The certificate the bundle is signed with (your upload key), with SHA-1, SHA-256 and MD5 fingerprints and a warning when it is the Android debug key.
Google Play readiness
Target API 36, debuggable and test only builds, debug key, 64-bit native code, 16 KB page size alignment, and permissions explained in plain words with the ones that need a Play Console declaration.
Build looks good? Get it to testers
Upload the same file to AppForShare and send testers one install link or QR code, for iPhone and Android alike. An .aab needs a free account and becomes one APK your testers install.
Questions
- Is my AAB uploaded?
- No. The bundle is read in your browser with JavaScript, so it never leaves your device and there is no size limit. Only if you click "Share this build with testers" is it uploaded to AppForShare, which needs a free account for an .aab.
- Why can my AAB not be opened like an APK?
- An Android App Bundle stores its manifest and resource table as protocol buffers made by aapt2 (base/manifest/AndroidManifest.xml and base/resources.pb), not as the binary XML inside an APK. This tool reads that format, so you do not need bundletool to see what is inside.
- Which certificate does an AAB show?
- Your upload key: Gradle signs the bundle with a JAR signature (META-INF). With Play App Signing, Google Play signs the APKs it delivers with the app signing key it keeps, so Firebase and Google sign-in need that key's SHA-1 from Play Console too.
- Can testers install an .aab?
- No, phones install APKs. Upload the .aab to AppForShare with a free account and testers get one APK made from it with bundletool, signed with a test key made for your account (or your own key on Pro and Team). Or build a universal APK yourself with bundletool build-apks --mode=universal.
- Does it check the target API level and 16 KB pages?
- Yes. It runs the same Google Play rules as the APK analyzer on the base module: target API 36 since August 31, 2026, debuggable builds, the debug key, 64-bit native code and 16 KB page size alignment of the 64-bit native libraries.
More free tools: all tools, app icon generator, ExportOptions.plist generator, UDID finder.