Android Keystore / Certificate Fingerprints (SHA-1, SHA-256, MD5)

Computes the MD5, SHA-1 and SHA-256 certificate fingerprints that Firebase, Google Sign-In, Play App Signing and assetlinks.json ask for, from a PEM certificate or a JKS or .keystore file you open here.

Use the tool

Why this tool exists

Firebase wants your SHA-1, Google Sign-In wants your SHA-256, and assetlinks.json wants the same value with colons. Normally you get them by running keytool with the right flags and the right password, which is easy to forget. Here you can paste a PEM certificate (keytool -exportcert -rfc), or open a .jks or .keystore file directly. Certificates inside a JKS are not encrypted, so no password is needed to read them. Newer PKCS12 keystores (.p12 or .pfx) are encrypted and are not supported: use keytool -list -v for those. The file is read in your browser and is not uploaded, and only the public certificate is used, never your private key.

How to use it

  1. Paste a PEM certificate, or choose a .jks, .keystore, .crt, .cer, .pem or .der file.
  2. Run the tool to compute the fingerprints.
  3. Copy the SHA-1 or SHA-256 value into the Firebase console, Google Cloud or assetlinks.json.

Frequently asked questions

Do I need the keystore password?

Not for a JKS file, because the certificates in it are not encrypted. The password protects the private key, which this tool never reads.

Why are .p12 and .pfx files not supported?

PKCS12 keystores are encrypted with a password, and this tool does not decrypt them. Use keytool -list -v -keystore file.p12 instead.

Which fingerprint do I need?

Firebase and many older services ask for SHA-1. Google Sign-In, Play App Signing and Digital Asset Links use SHA-256. The tool shows MD5, SHA-1 and SHA-256 so you can pick.

Is my keystore uploaded?

No. The file is read locally in your browser and only the certificate fingerprints are computed. Your private key is never used.