Hash Function Explorer
Hash one string with every algorithm the browser engine carries — MD5, SHA-1, SHA-2, SHA-3, RIPEMD-160, MD4, CRC-32, Adler-32 — side by side.
Every digest, one string
The page hashes the text you paste with each algorithm the engine on the page supports: MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, RIPEMD-160, MD4, CRC-32 and Adler-32. Each digest is printed on its own line, so the lengths and the avalanche behaviour can be compared at a glance.
An algorithm whose library did not load prints unavailable with the reason rather than vanishing, because a missing line and a broken engine would otherwise look identical. MD5, SHA-1 and CRC-32 are here to be compared, not to be trusted: none of them is a password hash or a signature, and the page says so.
All of it runs in this tab over the text you typed. Nothing is uploaded, no digest is stored, and the same text always prints the same digests.
Hash one string with every algorithm the page carries — MD5, SHA-1, the SHA-2 family, SHA-3, RIPEMD-160, MD4, CRC-32 and Adler-32 — and print each digest on its own line.
It compares digests; it does not salt, stretch, sign or verify anything, and an algorithm whose library did not load is named rather than silently skipped.
How to use Hash Function Explorer
Type the text to hash into the field, or press Load sample to load the quick brown fox sentence.
Press Run and read the digests: each algorithm prints on its own line, and an engine that failed to load is named rather than skipped.
Count the hex characters to tell the algorithms apart — 32 for MD5, 40 for SHA-1, 64 for SHA-256 — and use Copy to take the block.
Reading the digests side by side
The length of each digest is a property of the algorithm: 32 hex characters for MD5, 40 for SHA-1, 56 for SHA-224, 64 for SHA-256, 96 for SHA-384, 128 for SHA-512, and 8 for CRC-32 and Adler-32. Seeing them on one page makes the families obvious.
MD5, SHA-1 and CRC-32 are included to be compared, not to be trusted: all three are broken for collision resistance, and none of the twelve is a password hash or a signature. For passwords use a memory-hard KDF; for integrity use SHA-256 or better.
What to Expect
Best for
- Comparing digest lengths and outputs for one input.
- Checking a published test vector against the browser implementation.
What this tool keeps
- Every digest is computed in this tab and the text never leaves it, so the page works offline and stores no digest.
Sample input
abc
Sample output
MD5: 900150983cd24fb0d6963f7d28e17f72 SHA-1: a9993e364706816aba3e25717850c26c9cd0d89d SHA-256: ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad CRC-32: 352441c2 Adler-32: 024d0127
Frequently asked questions
Which algorithms does it run?
MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA3-256, SHA3-512, RIPEMD-160, MD4, CRC-32 and Adler-32 — every digest the engine on this page carries, one line each.
Why does a line say "unavailable"?
That algorithm is implemented in a library this page loads, and the library did not load. The line names the reason rather than vanishing, because a missing line and a broken engine would otherwise look the same.
Is the text uploaded?
No. Every digest is computed in this tab over the text you typed, nothing is sent anywhere, and no digest is stored.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.