Android keystore SHA-1 and SHA-256 helper
Paste the text printed by keytool -list -v or ./gradlew signingReport and this helper lists each key's SHA-1 and SHA-256, says where each one is used, and converts between colon hex, plain hex and base64. It never asks for a keystore file or a password.
Updated
Keys found
2
2 entries in the paste, identical keys merged
Fingerprints and where to use them
# Key 1: debug (debug key) SHA-1 A1:B2:C3:D4:E5:F6:07:18:29:3A:4B:5C:6D:7E:8F:90:A1:B2:C3:D4 SHA-256 11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:F0:01:12:23:34:45:56:67:78:89:9A:AB:BC:CD:DE:EF:F1:02 SHA-256 (plain) 112233445566778899aabbccddeef00112233445566778899aabbccddeeff102 # Key 2: release (local release or upload key) SHA-1 0F:1E:2D:3C:4B:5A:69:78:87:96:A5:B4:C3:D2:E1:F0:0A:1B:2C:3D SHA-256 9F:8E:7D:6C:5B:4A:39:28:17:06:F5:E4:D3:C2:B1:A0:90:81:72:63:54:45:36:27:18:09:FA:EB:DC:CD:BE:AF SHA-256 (plain) 9f8e7d6c5b4a39281706f5e4d3c2b1a090817263544536271809faebdccdbeaf # Where each one goes Firebase, Google Sign-In, Google API keys (OAuth client, key restriction): SHA-1 (Google's client-auth page asks for it). Adding the SHA-256 too is harmless in the Firebase console. assetlinks.json (Android App Links): SHA-256 only, colon-hex uppercase. Play App Signing: these are your local keys. Store installs use Google's app signing key; copy its SHA-1 and SHA-256 from Play Console > Release > Setup > App signing for production.
- Key 1
- debug (debug key)Valid until Friday, 15 May 2054
- SHA-1
- A1:B2:C3:D4:E5:F6:07:18:29:3A:4B:5C:6D:7E:8F:90:A1:B2:C3:D4
- SHA-256
- 11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:F0:01:12:23:34:45:56:67:78:89:9A:AB:BC:CD:DE:EF:F1:02
- Key 2
- release (local release or upload key)Valid until Monday, 3 March 2053
- SHA-1
- 0F:1E:2D:3C:4B:5A:69:78:87:96:A5:B4:C3:D2:E1:F0:0A:1B:2C:3D
- SHA-256
- 9F:8E:7D:6C:5B:4A:39:28:17:06:F5:E4:D3:C2:B1:A0:90:81:72:63:54:45:36:27:18:09:FA:EB:DC:CD:BE:AF
| Key | Command or place | Note |
|---|---|---|
| Debug keystore | keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore | Password is android (Google's page) |
| Release or upload keystore | keytool -list -v -alias YOUR_ALIAS -keystore /path/to/release.jks | keytool asks for the keystore password in your terminal |
| Every variant at once | ./gradlew signingReport | Run from the project root; prints Variant, Store, Alias, SHA1 and SHA-256 |
| Play App Signing key | Play Console > Release > Setup > App signing | Copy the app signing key's SHA-1 and SHA-256 there; keytool can't read it |
- Debug and release keys have different fingerprints. Register both with Firebase and Google Cloud while you develop, or sign-in works in one and fails in the other.
- With Play App Signing, the key your users receive is Google's, not the one in this paste. Add Play Console's app signing key to Firebase, Google Cloud and assetlinks.json for the store build.
What does the helper read, and what does it leave alone?
You run keytool or Gradle yourself and paste the text it prints. The helper looks for Alias name or Variant lines, then SHA1 and SHA256 (or SHA-256) lines, and groups identical keys together, because Gradle prints the same debug key under several variants.
It never takes a keystore file, never asks for a store or key password, and sends nothing anywhere. Everything is parsed by your browser, and a fingerprint is a public value anyway: it identifies a certificate and doesn't let anyone sign as you.
The fingerprints are shown in colon-hex, which is what Firebase, Google Cloud and assetlinks.json use. The convert box turns a fingerprint between colon hex, plain hex and base64, for the tools that ask for another form.
colon hex : AA:BB:CC:... (SHA-1 = 20 pairs, SHA-256 = 32 pairs) plain hex : AABBCC... (40 or 64 characters) base64 : the same bytes, 28 or 44 characters
Which fingerprint does each service need?
| Where | Fingerprint | Which key |
|---|---|---|
| Google Sign-In OAuth client, Google API key for an Android app | SHA-1 (Google's page asks for it) | The key that signed the build: debug while developing, app signing key for Play |
| Firebase Android app settings | SHA-1; add SHA-256 as well (ours) | Register debug and the Play app signing key |
| assetlinks.json (Android App Links) | SHA-256, uppercase colon hex | The key users get: Play app signing key |
| Play Console | Shows MD5, SHA-1 and SHA-256 of upload and app signing certificates | Release > Setup > App signing |
How to get and sort your Android SHA fingerprints
- 1Run a commandRun ./gradlew signingReport from your project root, or keytool -list -v against your keystore. Both print SHA1 and SHA-256.
- 2Paste the outputPaste the whole text into the box. Leave out passwords; the helper never needs them.
- 3Read the keysCheck which are debug and which are release or upload. Copy the SHA-1 for Firebase and Google Cloud and the SHA-256 for assetlinks.json.
- 4Add the Play App Signing keyFor store builds, open Play Console > Release > Setup > App signing and add that key's SHA-1 and SHA-256 to the same places.
Frequently asked questions
How do I get the SHA-1 of my debug keystore?
Why does Google Sign-In work in debug but not from the Play Store?
Is it safe to paste keytool output into a web tool?
Does keytool output SHA256 or SHA-256?
How do I turn a plain hex SHA-256 into the colon form for assetlinks.json?
Sources
- Google for Developers, Authenticating your client (SHA-1, debug and release keytool commands) (checked 11 Nov 2026)
- Android Developers, Sign your app (debug keystore, signingReport, Play App Signing keys) (checked 11 Nov 2026)
- Android Developers, Configure Digital Asset Links (SHA-256 for assetlinks.json) (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter