How to use it
- Get your fingerprint. Run keytool -list -v -keystore your.jks, or copy it from Play Console → App integrity.
- Paste it. Paste the SHA-1 or SHA-256 value in any format.
- Copy the format you need. Copy colon hex, plain hex, Base64 or Base64URL.
One fingerprint, many formats
A certificate fingerprint is a fixed number of bytes — 20 for SHA-1, 32 for SHA-256. Tools just print those bytes differently:
| Where | Asks for |
|---|---|
| keytool, Play Console, Firebase | Colon-separated uppercase hex |
| Facebook Login (Android key hashes) | Base64 of the SHA-1 bytes (28 characters) |
| assetlinks.json | Colon hex SHA-256 — see the assetlinks.json generator |
| Some APIs and configs | Plain hex or Base64URL |
Use the right key's fingerprint
For apps installed from Google Play, users get an APK signed with Google's app signing key, so register that key's fingerprints with Facebook, Firebase and App Links — not only your upload key. For APKs you share directly, use the key you sign with. More in Android app signing explained.
Everything happens on your device. Nothing you type or upload here is sent to a server.
Make your APK now — free
No Android Studio, no code, no watermark. Pick what you are starting from:
Frequently asked questions
How do I get a Facebook key hash from a SHA-1?
Paste the SHA-1 fingerprint here; the Base64 output is the key hash Facebook asks for.
Is it safe to share my fingerprint?
Yes. Fingerprints are derived from your public certificate and are meant to be shared. Never share the keystore file or its passwords.
Why does Facebook say my key hash doesn't match?
You probably registered the upload or debug key's hash. Add the hash of the key that signed the installed app — for Play installs, the app signing key.