🔐 Hash Generator
Compute SHA-1, SHA-256, and SHA-512 digests of any text you type or paste, to compare strings and check data integrity. The hash is computed by your browser's Web Crypto API — nothing is uploaded or stored.
🔐 Generate a Hash
What is a Hash Generator?
A hash generator turns any input into a short, fixed-length fingerprint. The same input always produces the same digest, and even a tiny change produces a completely different one — which makes hashes ideal for verifying that an APK, ROM, or file downloaded intact. This page hashes text; for a downloaded file, run shasum -a 256 (macOS, Linux) or certutil -hashfile (Windows) on the file and compare.
This tool uses your browser's native Web Crypto API, so the digest is computed entirely on your device and nothing is uploaded or stored. Pick SHA-256 for everyday integrity checks, SHA-512 for extra length, and treat SHA-1 as legacy-only since it's no longer collision-resistant.
❓ Frequently Asked Questions
What is a cryptographic hash and what is it used for on Android?
A hash is a fixed-length fingerprint of some input data — change one character and the hash changes completely. Android developers and power users use hashes to verify that a downloaded APK or ROM matches its published checksum, to compare files and to sign data. This tool computes SHA-1, SHA-256, and SHA-512 of TEXT you type or paste; to check a downloaded file, hash the file itself (macOS or Linux: shasum -a 256 <file>; Windows: certutil -hashfile <file> SHA256) and compare the result with the published checksum.
Is my text sent to a server to be hashed?
No. The digest is computed locally by your browser's built-in Web Crypto API (window.crypto.subtle) — the text never leaves your device and nothing is stored. It runs entirely in your browser, so it's safe for sensitive input.
Which hash algorithm should I use?
SHA-256 is the sensible default for integrity checks and most modern uses. SHA-512 produces a longer digest and is common for high-assurance verification. SHA-1 is included for compatibility with older checksums but is considered cryptographically weak — avoid it for security-critical work.
Can I use SHA-256 to store passwords?
No. The OWASP Password Storage Cheat Sheet says: "Fast hashing algorithms such as SHA-256 are not suitable for password storage because they allow attackers to perform large numbers of guesses quickly." It recommends slow algorithms such as Argon2id, bcrypt or PBKDF2 with a unique salt per password. SHA-1 is worse still: it is broken for security use and kept here only to match legacy checksums.
Can I reverse a hash back to the original text?
No. Cryptographic hashes are one-way by design — you cannot recover the input from the output. But anyone can hash guesses and compare, so a short or guessable input (a PIN, a phone number, a common password) is found quickly; a hash does not hide it. To confirm a match, hash the candidate input and compare the two digests.