#️⃣ Hash Generator
Compute an MD5, SHA-1, SHA-256, SHA-384, or SHA-512 digest of any text, entirely in your browser — handy for checksums, fingerprints, and verifying that data has not changed.
#️⃣ Text to Hash
What is a Hash Generator?
A hash generator turns text into a fixed-length digest that acts as a fingerprint of the input. Because the same text always produces the same digest, hashes are ideal for verifying that a file or message has not been altered.
Use SHA-256, SHA-384, or SHA-512 for anything that matters; treat MD5 and SHA-1 as legacy-only. And never store passwords with a plain fast hash — use a slow, salted password-hashing scheme instead.
❓ Frequently Asked Questions
What is a hash function?
A hash function maps any input to a fixed-length string of hex digits called a digest. The same input always yields the same digest, while even a one-character change produces a completely different one. Hashes are one-way — you cannot reconstruct the original text from the digest — which makes them useful for integrity checks and fingerprints.
Which algorithm should I use?
For integrity and general fingerprinting, SHA-256 is the sensible default. SHA-384 and SHA-512 offer longer digests for extra collision margin. MD5 and SHA-1 are included because you still encounter them in legacy checksums, but both are cryptographically broken and should not be used for security-sensitive work. None of the five, SHA-256 included, is fit for storing passwords: 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, and points to Argon2id, bcrypt or PBKDF2 with a unique salt.
Is my text sent to a server?
No. SHA-1, SHA-256, SHA-384, and SHA-512 are computed with the browser's built-in Web Crypto API, and MD5 runs as pure JavaScript in the page. Nothing you type is uploaded or stored, so it is safe for hashing values you would rather keep local.
Can I get the original text back from a hash?
No — hashing is one-way by design, so there is no 'un-hash' operation. Anyone who appears to reverse a hash is really matching it against a precomputed table of known inputs. That is exactly why passwords should be hashed with a slow, salted algorithm rather than a plain fast hash.