How to use
- Drop an APK, APKS, XAPK, APKM, or AAB file onto the upload area, or choose one with the file picker. Files can be up to 300 MiB; inspect one package at a time.
- Inspection starts automatically when you choose or drop a file. Follow the progress; you can cancel while it runs.
- Review the Findings tab, or use Archive to filter APK files in a split bundle.
- Choose Export JSON to download the report, or use the clear control beside the filename to start over.
Example
An APK containing lib/arm64-v8a/libflutter.so is reported as likely built with Flutter. A Kotlin metadata file by itself is listed as a supporting signal, not as proof that the app was written in Kotlin.
About Android app technology detection
Android packages are ZIP archives with manifests, assets, native libraries, and other files. Cross-platform frameworks often include recognizable files in those archives. The detector checks filenames and reports the matching paths so you can judge the evidence for yourself.
It supports regular APKs, ZIP bundles containing split APKs, and Android App Bundles with module manifests. It does not install or run the app, inspect its source code, verify its package identity, or guarantee that a framework signature belongs to the app rather than one of its dependencies. Native Android apps and unsupported frameworks may have no recognizable signatures.
Files are limited to 300 MiB, archives to 200,000 entries, and split bundles to 1,000 APKs. Large nested archives are size-limited during local inspection.
Privacy
All inspection happens on your device in a browser Web Worker. Your app file is never uploaded or stored by ToolsLodge.