Hash Generator
MD5 and SHA-1 are broken
MD5 collisions are craftable in seconds on commodity hardware ($0.65 of GPU time), SHA-1 since SHAttered (2017). Use only SHA-256+ for security. MD5/SHA-1 are fine for non-security uses like cache keys or checksums.
Related tools
Known-answer tests (sanity-check this calculator)
- "hello" → SHA-256 =
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 - "" (empty) → SHA-256 =
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - "hello" → MD5 =
5d41402abc4b2a76b9719d911017c592 - "hello" → SHA-1 =
aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
Frequently asked questions
Where are MD5/SHA-1 still acceptable?
Checksums for accidental corruption (CDN integrity, file downloads where security isn't the goal). Cache keys (no attacker model). Non-adversarial deduplication. NEVER for passwords, signatures, or certificates.
Why don't you include bcrypt/scrypt/Argon2?
Those are PASSWORD-HASHING algorithms — deliberately slow with built-in salt + work factor. Web Crypto API doesn't expose them, and you shouldn't compute them in browsers anyway — password hashing happens on the server.
File hashing shows a different value than online tools?
Encoding! Text tools may add a trailing newline, or differ on EOL (\n vs \r\n). Files hash exactly their bytes. Most online tools hash UTF-8 of the visible text, which may differ from your file's actual encoding.
Salting + hashing — do I need it?
For password storage: YES, absolutely, use bcrypt/Argon2 (which integrate salt). For checksums / dedup: salt is pointless. For token uniqueness: use random tokens directly, not hashes.