Free tool
APK analyzer: package, SDK, permissions and Play readiness
Drop an .apk to see its package name, version code, min and target SDK, permissions, signing key and native libraries, and what Google Play would reject. It runs in your browser, so the file is never uploaded.
What it checks
App details
Package name, app name, icon, version name and code, minimum and target SDK, device type and launch activity.
Signing
v1, v2 and v3 signature schemes, the signer name, and whether the APK is signed with 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 that need a Play Console declaration.
What is inside
Every permission, native ABIs and libraries, and the cross platform stack: Flutter, React Native, Unity, Capacitor, Cordova or .NET.
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. Free without an account.
Questions
- Is my APK uploaded?
- No. The APK 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.
- How do I find the package name and version code of an APK?
- Drop the APK here. The App section shows the package name (application id), version name and version code, read from the binary AndroidManifest.xml, with the app name and icon resolved from resources.arsc.
- How do I check the target SDK of an APK?
- The target SDK is shown with its Android version. Since August 31, 2026 new apps and updates on Google Play must target API 36 (Wear OS and Automotive 35, Android TV 34), and the readiness check flags a lower target.
- Does my APK support 16 KB page sizes?
- The tool reads the ELF headers of the 64-bit native libraries and lists every library whose LOAD segments are not 16 KB aligned. Google Play requires 16 KB support for apps that target Android 15 or higher.
- Is my APK signed with a debug key?
- The Signing section shows the signature schemes and the signer. A build signed with the Android debug key is fine for testers, but Google Play rejects it.
- Can it read an AAB?
- Not yet. An Android App Bundle stores its manifest in a different format, and testers cannot install an .aab directly anyway. Make a universal APK from it with bundletool build-apks --mode=universal, or use the APK your build makes.
More free tools: all tools, app icon generator, UDID finder.