Hash Generator
Generate SHA-1, SHA-256, SHA-384, and SHA-512 hashes from any text.
๐Digital fingerprints, computed locally
Hash any text with SHA-256, SHA-1, SHA-384, or SHA-512using your browser's built-in Web Crypto โ nothing is sent anywhere. A hash is a one-way fingerprint: the same input always yields the same output, but even one changed character produces a completely different hash, and there's no way back.
๐งฎWhat makes a hash a hash
"One-way" means you can't reverse it; "avalanche" means changing a single letter flips roughly half the output bits. Together those properties make hashes ideal for verifying integrity: if the fingerprints match, the data is identical.
hello starts 2cf24dba5fb0โฆ; of Hello starts 185f8db32271โฆ โ one capital letter, an entirely different fingerprint.๐กChoosing an algorithm
- SHA-256 โ the modern default: file checksums, integrity checks, blockchain, certificates.
- SHA-512 โ same family, larger digest; sometimes faster on 64-bit machines.
- SHA-1 โ broken for security (collisions exist); use only to match legacy systems like old Git hashes.
- For storing passwords, none of these raw hashes are right โ real systems use slow, salted algorithms (bcrypt, Argon2).
๐ก Frequently Asked Questions
What is a hash used for?+
Verifying that data hasn't changed: download checksums, digital signatures, Git commits, and blockchains all compare hashes. Same hash = same data, with astronomically high confidence.
Can I decrypt a hash back to the original text?+
No โ hashing is one-way by design; the information to reverse it doesn't exist in the digest. 'Cracking' a hash means guessing inputs until one matches, which is why long random inputs are safe.
Which is better, SHA-256 or SHA-512?+
Both are secure members of the SHA-2 family. SHA-256 (64 hex chars) is the ecosystem default; SHA-512 gives a longer digest and can be faster on 64-bit CPUs. Pick whatever the system you're matching uses.
Is SHA-1 still safe?+
Not for security โ practical collision attacks exist since 2017. It survives only for compatibility (legacy Git, old protocols). For anything new, use SHA-256 or better.
Why shouldn't passwords be stored as SHA-256?+
Because SHA-256 is fast โ attackers can test billions of guesses per second against stolen hashes. Password storage needs deliberately slow, salted algorithms like bcrypt, scrypt, or Argon2.
Is my text uploaded to compute the hash?+
No โ hashing runs in your browser via the Web Crypto API. You can disconnect from the internet and it still works.