What it shows

Open an Android app file and see who signed it:

  • App: the app name, the package name (such as com.example.app), the version name and version code, the minimum Android version the app runs on and the SDK version it targets.
  • Signing: which signature schemes the APK uses, and every signing certificate with its SHA-256 and SHA-1 fingerprints, subject, issuer, validity dates, serial number, public key and signature algorithm. A certificate that several schemes share is listed once.
  • Permissions: the permissions the app asks for in its manifest.

Besides plain .apk files it opens the containers apps are often shared in: .apks (bundletool), .xapk and .apkm. It reads the base APK inside them and says which file that was.

Where the SHA-256 fingerprint is needed

The SHA-256 fingerprint of the signing certificate identifies who signed an app, and the same key has to sign every update.

  • Android developer verification: Google is rolling out a requirement that apps on certified Android devices come from verified developers, country by country. Developers register each app with its package name and the SHA-256 fingerprint of its signing certificate, and this tool shows both from the APK itself.
  • Google APIs and Firebase: Google Sign-In, Maps keys restricted to an Android app, and Firebase ask for the SHA-1 or SHA-256 fingerprint of the key that signs the app.
  • Checking a download: compare the fingerprint of an APK from another source with the one the developer publishes, or with the version you already have installed. Different fingerprints mean a different signer.

An app that Google Play signs (Play App Signing) is signed with a key Google holds for the developer, so APKs from Play show that key, not the developer's upload key.

Signature schemes in short

  • v1 (JAR signing): signature files in the META-INF folder, the original scheme. Apps that run on Android 7.0 and newer only can leave it out.
  • v2: a signature over the whole file in the APK Signing Block, checked since Android 7.0.
  • v3: like v2, with key rotation since Android 9: an app can move to a new signing key, and the old one is listed in its key history. The tool shows such older certificates as "Earlier key".
  • v3.1: lets a rotated key apply only from Android 13, so older devices keep seeing the earlier key.

Good to know

  • The tool reads the certificates but doesn't verify the signatures or check whether the file was changed after signing. Use apksigner verify --print-certs from the Android SDK for that.
  • App names come from the app's resources. When those use an encoding the tool can't read reliably, the app name stays empty rather than showing a wrong one.
  • Android App Bundles (.aab) can't be installed directly and aren't read; build an APK from one with bundletool.
  • Everything happens in your browser. The file isn't uploaded anywhere.