All Hashes Generator

What this tool does

All Hashes Generator runs up to 30 hash functions and checksums over the same input at once, from MD5 and SHA-256 to BLAKE3, Keccak-256 and XXH3. Paste text or drop a file, filter the list, paste an unknown digest to see which algorithm produced it, and export everything as JSON or CSV.

Different systems expect different digests: a Linux mirror publishes SHA-256, an old download page lists MD5, Ethereum uses Keccak-256, a backup tool reports BLAKE3 and a database stores CRC32 or xxHash. Running a separate tool for each is slow, and when you are handed a mystery hex string you often do not know which algorithm made it.

This generator feeds the same bytes through every algorithm in one view. The Popular set computes eight common hashes; the full set adds MD4, SHA-224/384, all four SHA-3 and Keccak sizes, BLAKE2b, BLAKE2s, RIPEMD-160, Whirlpool, the Chinese SM3 standard and the non-cryptographic checksums CRC-32, CRC-32C, CRC-64, Adler-32 and the xxHash family. Hashing uses WebAssembly, files are streamed in 4 MB chunks and nothing leaves your device.

How to use All Hashes Generator

1. Choose Text or File as the input source.
2. Type or paste text, or drop a file of any size.
3. Under Options pick the Algorithm set: Popular algorithms (8 hashes) or All algorithms (30 hashes & checksums).
4. Set the Input encoding to Hexadecimal bytes or Base64 bytes when you are hashing raw binary rather than text.
5. Choose an Output format, and type in Filter algorithms to narrow the table, for example “sha3” or “256”.
6. Paste a digest into “Identify an unknown hash” to see which algorithm reproduces it, then copy the JSON or download the CSV.

Tips for better results

• SHA3-256 and Keccak-256 differ only in a padding byte, yet give completely different results. Ethereum addresses and Solidity use Keccak-256, not SHA3-256.
• BLAKE3 and XXH3 are by far the fastest options on large files, which matters when you hash many gigabytes.
• The identify feature only finds a match if you also supply the exact original input, including any salt and trailing line break.
• A digest length narrows the search: 32 hex characters means a 128-bit function such as MD5 or MD4, 64 means a 256-bit one.

Common use cases

• Producing a complete set of test vectors for a library you are porting or testing.
• Working out which algorithm a legacy system used by hashing a known value and matching its stored digest.
• Publishing several checksums for a release so users can verify with whichever tool they have.
• Comparing the output lengths and formats of hash families while learning about them.

Common mistakes to avoid

• Treating CRC-32, Adler-32 or xxHash as security hashes. They detect accidental errors but are trivial to forge.
• Expecting different algorithms to agree. Each produces an unrelated value, so compare only like with like.
• Hashing hex text as UTF-8 characters when you meant the bytes it represents; switch the input encoding first.