What's inside this APK?
Drop in an APK to see its permissions, who signed it, which phones it runs on and whether it's ready for 16 KB pages. Nothing gets installed or uploaded.
Drop your .apk
or browse files. Any size works
Read on your device. Nothing is uploaded.
What it checks
Signature
Whether it's signed at all, with which schemes, and whether the certificate is the Android debug key. Unsigned APKs won't install, and v1 alone isn't enough for anything targeting Android 11 or newer.
16 KB page size
Reads the ELF header of every 64-bit native library and checks each one is aligned to 16 KB, plus the zip alignment of uncompressed libraries. Google Play requires this for apps targeting Android 15 and up.
64-bit support
Lists the CPU architectures it ships. An APK with only 32-bit libraries won't install on 64-bit only phones like the Pixel 7 and newer.
Permissions
Every permission it asks for, which ones show the user a prompt, and which ones Google Play makes you justify in a declaration form.
Target API level
The Android version it's built for, against what Google Play currently asks for.
What takes up the space
How much is code, native libraries, resources and assets, so you know where to look when the APK is too big.
Have an App Bundle instead? The AAB inspector runs the same checks the way Play sees them, and the AAB to APK converter turns it into something you can install.
Questions
Do you upload my APK?
No. The file is read inside your browser tab. We open the zip, read the manifest, the signing block and the headers of the native libraries, and show you what's there. Nothing is sent to us, so the size of the APK doesn't matter.
Can it tell me if an APK is safe?
Not on its own. It shows what the app asks for and who signed it, which is a good first look: a calculator that wants your SMS and contacts deserves suspicion. But it doesn't scan the code for malware. For an APK from a stranger, also run it through VirusTotal, and prefer the developer's own download page.
How do I check if an APK is signed with the debug key?
Drop it in. The Signing section names the certificate, and a build signed with Android Studio's debug key shows as Android Debug, with a warning at the top. You can test with it, but Play won't accept it and a release build won't install over it.
How do I find an APK's SHA-256 fingerprint?
It's in the Signing section, in the same AA:BB:CC format that apksigner, Firebase and the Play Console use. It's the fingerprint of the certificate in the v3 or v2 signature, falling back to v1 when those aren't there.
What does "Not ready for 16 KB page sizes" mean?
Newer Android phones use 16 KB memory pages instead of 4 KB. A native library built for 4 KB pages can crash on them, so Google Play now requires 16 KB alignment for apps targeting Android 15 and up. The fix is usually rebuilding with NDK r28 or newer, or updating the SDK that ships the library named in the warning.
Why does the label show the package name instead of the app name?
In a compiled APK the app name is usually a pointer into the resources table, not plain text, and resolving it would mean reading that whole table. The package name is the reliable identifier anyway: it's what Android and Play use.
Can I check an .xapk or .apks file?
Not directly. Those are zips holding several APKs. Rename the file to .zip, unzip it, and drop in the base APK.