Hash Generator
Fingerprints for text. Turn anything you type into a SHA-256, SHA-384, or SHA-512 digest β the same one-way hashes behind checksums and Git commits.
How to use
- Type or paste your text. Anything from a password candidate to a file manifest.
- Pick SHA-256, 384, or 512. 256 is the everyday default; bigger digests are slower but stronger.
- Read the digest. It computes automatically as you type β no button needed.
- Copy the hash. Paste it wherever the checksum is needed.
Hashes, checksums, and what they're for
A hash turns any input β a word, a file, a whole disk image β into a fixed-length fingerprint. Change one character and the fingerprint changes completely. That makes hashes perfect for verification: download a file, hash it, and compare against the publisher's checksum. If they match, the file arrived intact and untampered-with.
What a hash is not is encryption. There's no key and no way back β you can't un-hash a value into the original. And the algorithms have different jobs now: MD5 and SHA-1 are fine as quick checksums for spotting corruption, but they're too fast and too collision-prone to protect passwords, which is why login systems use slow, salted hashing instead. Everything you type here is hashed in your browser and never sent anywhere, so it's safe for checking sensitive strings β just don't paste an actual password into any tool, this one included, as a general rule of digital hygiene.
Frequently asked questions
What is a SHA-256 hash used for?
Verifying integrity: download a file, hash it, and compare against the publisher's checksum β if they match, the file wasn't corrupted or tampered with. SHA-256 also underpins Git commits, Bitcoin, and certificate signatures.
Can a hash be reversed to get the original text?
No β that's the whole point. SHA hashes are one-way: easy to compute, practically impossible to invert. Weak passwords can still be guessed by brute force, though, so don't hash βpassword123β and call it secure.
What's the difference between SHA-256, 384, and 512?
Digest length: 64, 96, or 128 hex characters, all from the SHA-2 family. Longer digests resist collision attacks better. SHA-256 is plenty for checksums and everyday use; 512 is for the extra-paranoid.
Why does it say a secure context is required?
Browsers only expose the native crypto API on HTTPS pages and localhost. If you see that message, you're likely on plain HTTP β the page itself is fine, the browser is just being cautious about cryptography.
Is my text sent to a server?
No. Hashing runs locally in your browser through the Web Crypto API. Your text never leaves the page.
Related tools
Keep the momentum going.