About the All Hash Generator
When you need to identify which algorithm produced a given digest, or you just want to compare, this tool computes a whole set of hashes from one input at once: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, Keccak-256, RIPEMD-160, BLAKE2b, BLAKE3, CRC32 and xxHash64. Each is labelled with its length, so you can match an unknown hash by its character count and value.
Seeing them stacked together makes three properties concrete that are otherwise abstract: every algorithm returns a fixed length regardless of how long the input is, changing a single character scatters every digest in the list completely, and the same input always returns the same output. That last property is why an unsalted password hash is weak, since identical passwords collide across every row in the table no matter which algorithm was chosen.
Character count is the fastest way to narrow down an unfamiliar digest. Thirty-two hex characters points at MD5 or RIPEMD-128, forty at SHA-1 or RIPEMD-160, sixty-four covers SHA-256, SHA3-256, Keccak-256 and BLAKE2s, and 128 means SHA-512 or Whirlpool. Where candidates share a length, hash a known input here and compare the whole column at once. It is handy for verifying a download against whichever checksum a site publishes, for teaching how output length and content differ across algorithms, and as a quick reference. All computation happens locally. To identify an unknown hash by format alone, use the Hash Identifier; for a file instead of pasted text, the File Hash Generator.
How to use
- Paste text on the left.
- Read every hash on the right, each labelled.
- Compare against the checksum you are verifying.
Common questions
- Which hashes are included?
- MD5, SHA-1, SHA-224/256/384/512, SHA3-256/512, Keccak-256, RIPEMD-160, BLAKE2b, BLAKE3, CRC32 and xxHash64.
- How do I match an unknown hash?
- Compare its length and value to the list. A 32-character hex string is likely MD5; 64 is likely SHA-256. The Hash Identifier helps too.
- Is anything uploaded?
- No. Every hash is computed in your browser.