Hash Generator
Compute MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes of any text, instantly, side by side — plus verify text against a known hash. Runs entirely in your browser.
How to use the hash generator
- Type or paste text into the input box, or click Load sample.
- MD5, SHA-1, SHA-256, SHA-384, and SHA-512 hashes all compute instantly, side by side.
- Click Copy next to any hash to copy just that value.
- To verify a file or string against a known hash, paste it into the Verify against a hash field — it checks against all five algorithms automatically.
What it's for
- ✓ Verifying a downloaded file's checksum against a published hash
- ✓ Generating a quick fingerprint of a config value or API key for logging (never the secret itself)
- ✓ Comparing two pieces of text for exact equality without diffing them character by character
- ✓ Testing hash-based logic in code you're writing, against a known-correct reference
FAQs
Is my text sent to a server to compute the hash?
No. SHA-1/256/384/512 are computed with the browser's native Web Crypto API, and MD5 runs through a pure JavaScript implementation — both execute entirely on your device. Nothing you type here ever leaves your browser.
Which hash algorithm should I use?
For checksums and file-integrity verification, SHA-256 is the current standard. MD5 and SHA-1 are both cryptographically broken for security purposes (collisions are practical to find) but are still widely used for non-adversarial checksums, like verifying a download finished correctly.
Why does the same input always produce the same hash?
Hash functions are deterministic — the same input always maps to the same output. That's what makes the "verify against a hash" field useful: if a file or string hashes to the value you were given, you can be confident it's unmodified.
Can two different inputs produce the same hash?
In theory, yes (a "collision") — but a secure hash function makes finding one computationally infeasible. MD5 and SHA-1 no longer meet that bar for security-sensitive use (attackers can construct collisions), which is why SHA-256 or better is recommended wherever security matters.
Should I use this to hash passwords?
No. Plain SHA-256/MD5/etc. hash passwords too fast and without a salt, which makes them crackable by brute force. Password storage needs a purpose-built, slow algorithm like bcrypt, scrypt, or Argon2 — this tool is for checksums and data integrity, not password storage.