Find out if an APK file is the original one, signed by its developer. We verify the signature and compare the certificate with the official files in our catalog.

APK signature check online
Click to upload an APK file or a split APK archive
APK, XAPK, APKS, APKM or ZIP with split APKs
Maximum file size: 1 GB
The file is deleted right after the check
Uploading the file…

How to check the signature yourself

APK signature check FAQ

What is an APK signature?

Every Android app is signed by its developer. The certificate stays the same for all versions of the app, so it shows who built the file. A rebuilt or modded APK cannot keep the original signature.

Why is my file “Modified”?

The file is signed correctly, but with a different certificate than the official files of this app. Someone rebuilt and re-signed it, so its contents may be changed.

How can I check the signature myself?

Run apksigner verify --print-certs file.apk and compare the SHA-256 (or SHA1) fingerprint of the certificate with the result above. For APKS, XAPK and APKM files, unpack the archive first and check the APK files inside, starting with base.apk.

Do you keep my file?

No. The file is deleted right after the check.

Can I check XAPK, APKS and APKM files?

Yes. Upload the archive as it is: we check the signature of every APK inside and make sure that all of them are signed with the same certificate as the base APK.
How we verify files

A valid digital signature only means that the file has not been changed since it was signed. Whether the certificate belongs to the developer is shown by comparing it with a reference. That is why we do both checks for every file in the catalog.

What we check

  1. Signature. Whether the APK signature is valid under every scheme the file is signed with (v1, v2, v3, v3.1).
  2. Certificate. The SHA-256 and SHA-1 fingerprints, the certificate owner and, if the developer has changed the key, the previous keys from the rotation record.
  3. Reference. The certificate the developer uses to sign this app in the app store. If the developer changed the key and confirmed the change with a rotation record, the new certificate also counts as the developer's certificate.
  4. Developer's website. If the developer's website listed in their app store profile (or added by us manually after checking) publishes Android Digital Asset Links (/.well-known/assetlinks.json), we check that it names exactly this package and this certificate fingerprint.

What the statuses under the download button mean

  • Signature verified: the file's certificate matches the developer's certificate for this app in the app store, including a new certificate confirmed with a rotation record.
  • Matches earlier versions: there is no reference from the app store to compare with yet, but the certificate matches earlier versions of this app in the catalog.
  • Signing key changed: the app store version is signed with a new key without a rotation record, so the link to the old key is not confirmed.
  • Signature not compared: there is no reference certificate for this app yet.
  • Signature does not match / File does not match: the file is signed with a key that earlier versions do not use, or it differs from the version the app store serves.

If the developer publishes the same certificate on their website, the file panel shows the Developer’s site row with a link to assetlinks.json. This confirmation is independent of the app store.

Rechecks

We recheck developer websites with Digital Asset Links about once a week. If the certificate disappears from the website or the website is unavailable several times in a row, we remove the confirmation.

What the check does not do

The signature check concerns only the certificate the file was signed with. It does not assess how the app works, what data it collects or what permissions it requests. Before installing, read the app's description and permissions.