Multi-Algorithm Hash Generator
Hash text with 20 algorithms at once: MD5, SHA-1, SHA-2, SHA-3, Keccak, RIPEMD-160, BLAKE2, BLAKE3, Whirlpool, SM3, CRC32. Hex or Base64, live in your browser.
All digests update as you type. An empty input gives the digests of an empty string.
Runs entirely in your browser. Your data is never uploaded.
What is Hash Generator?
Computes the digest of your text in 20 algorithms simultaneously – MD5, SHA-1, SHA-224/256/384/512, SHA3-224/256/384/512, Keccak-256/512, RIPEMD-160, BLAKE2b-512, BLAKE2s-256, BLAKE3, Whirlpool, SM3, MD4 and CRC32 – so you can compare them or find the one you need. Weak algorithms are marked.
How to use Hash Generator
- Type or paste text into Input; all digests update instantly.
- Switch the input encoding to Hex to hash raw bytes instead of UTF-8 text.
- Choose the Output format: lowercase hex, uppercase hex or Base64.
- Copy a single value from the table, or use Copy to copy all lines.
Example
abc
MD5: 900150983cd24fb0d6963f7d28e17f72 SHA-1: a9993e364706816aba3e25717850c26c9cd0d89d SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad CRC32: 352441c2
Excerpt; the tool shows all 20 algorithms.
When to use Hash Generator
Use it to look up the digest of a string in several algorithms, to identify which algorithm produced a known hash, or to compare implementations. Do not use fast hashes to store passwords – use bcrypt, scrypt or Argon2. For files use a file checksum tool so line endings and encoding are not altered.
How Hash Generator works
The text is encoded as UTF-8 (or decoded from hex) and the bytes are fed to each algorithm's WebAssembly implementation from hash-wasm. SHA-2 uses the Merkle–Damgård construction, SHA-3 and Keccak use the sponge construction (they differ only in padding), BLAKE2/BLAKE3 are based on the ChaCha permutation, and CRC32 is a checksum, not a cryptographic hash. Results are checked against FIPS 180-4, FIPS 202, RFC 7693 and Node.js/OpenSSL in unit tests.
Common Use Cases
- Find which algorithm produced a known hash by comparing against all outputs
- Get the SHA-256 and SHA3-256 of a string for test fixtures
- Compute a Keccak-256 hash (as used by Ethereum) of text
- Check CRC32 checksums of short strings
- Show students how small input changes alter every digest
Security Note
Input is hashed locally and never uploaded. Fast hashes are unsuitable for password storage.
FAQs
What is the difference between SHA3-256 and Keccak-256?
Both use the Keccak sponge, but SHA3-256 (FIPS 202) uses different padding than the original Keccak submission. Ethereum uses Keccak-256, so the two give different results for the same input.
Why are MD5, SHA-1, MD4 and CRC32 marked as weak?
Collisions can be produced for them, so they must not be used for signatures, certificates or integrity against attackers. They are still fine for non-security checksums.
Can a hash be reversed?
No. Hashes are one-way; "decrypting" sites only look up precomputed values of common inputs.
Why does my program give a different hash?
Usually because of encoding: trailing newlines, Windows line endings or a non-UTF-8 encoding change the bytes. Use Hex input to hash exact bytes.