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.
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.