MD5, SHA-256, SHA-3, Keccak-256, BLAKE2, BLAKE3, RIPEMD-160, CRC-32 and 23 more of text, hex, Base64 or a file, and HMAC
Get the MD5, SHA-1, SHA-256, SHA-384, SHA-512 and double SHA-256 of text, bytes or a file up to 100 MB at once, with the CRC-32, CRC-16 and Adler-32 checksums, or an HMAC with a secret key. Under Show, list SHA-3, Keccak, BLAKE, RIPEMD-160 and 31 algorithms in all.
How to use it
Type or paste text, or open a file to hash its exact bytes. Under Input, hash the text as UTF-16 or Latin-1, or paste bytes as hex or Base64. Every hash and checksum is computed at once; switch between hex and Base64 output. Under Show, pick SHA-2 and SHA-3, the other families, or all 31. To check a hash you were given, paste it under the list: the page names the algorithm it matches. For an HMAC, turn on "HMAC with a key"; the key can be text, hex or Base64.
Examples
Hash of "abc"
abc
MD5 900150983cd24fb0d6963f7d28e17f72 SHA-256 ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
Checksums of "123456789"
123456789
CRC-32 cbf43926 CRC-16 bb3d Adler-32 091e01de
The check values each algorithm is published with, so you can tell which CRC another tool computes.
Bytes pasted as hex
68 65 6c 6c 6f
SHA-256 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
Input: Hex bytes. The same bytes as the text "hello", so the same hash.
Which hash to use
| Algorithm | Output | Use it for |
|---|---|---|
MD5 | 128 bits, 32 hex | Legacy checksums only; broken for security |
SHA-1 | 160 bits, 40 hex | Git object ids, legacy checks; broken for signatures |
SHA-256 | 256 bits, 64 hex | File integrity, API signatures, general use |
SHA-384 | 384 bits, 96 hex | Subresource Integrity (SRI), TLS |
SHA-512 | 512 bits, 128 hex | Same uses as SHA-256 where a longer hash is wanted |
SHA-256d | 256 bits, 64 hex | SHA-256 of the SHA-256: Bitcoin block and transaction IDs (shown there byte-reversed) |
CRC-32 | 32 bits, 8 hex | The checksum in zip, PNG and gzip files; catches accidents, not tampering |
CRC-16 | 16 bits, 4 hex | CRC-16/ARC, used by Modbus-era and serial protocols |
Adler-32 | 32 bits, 8 hex | The checksum at the end of zlib data |
SHA-224, SHA-512/224, SHA-512/256 | 224 or 256 bits | Shorter SHA-2 hashes; SHA-512/256 is faster than SHA-256 on 64-bit machines |
SHA3-224 to SHA3-512 | 224 to 512 bits | The FIPS 202 standard, built unlike SHA-2 (a sponge) |
Keccak-256 | 256 bits, 64 hex | Ethereum addresses and Solidity keccak256; not equal to SHA3-256 (different padding) |
SHAKE128, SHAKE256 | 256 or 512 bits shown | Extendable output: any length; the first 32 or 64 bytes are shown |
RIPEMD-160 | 160 bits, 40 hex | Bitcoin addresses (after SHA-256), PGP |
BLAKE2b, BLAKE2s, BLAKE3 | 512, 256, 256 bits | Fast modern hashes: Argon2, libsodium, WireGuard, file sync tools |
Whirlpool, SM3 | 512, 256 bits | ISO/IEC 10118-3; SM3 is China’s national standard |
MD4 | 128 bits, 32 hex | NTLM password hashes and rsync; broken |
xxHash32, xxHash64 | 32, 64 bits | Fast non-secure hashes (seed 0) for caches and dedupe |
Text is hashed as UTF-8, unless you pick
Questions
- Is my text or file uploaded?
No. Everything runs in your browser, so your data stays on your device. Nothing you paste is uploaded unless you share it. SHA-1 and SHA-2 come from your browser’s Web Crypto API, the others from open-source code loaded with the page (the SHA-3, BLAKE and RIPEMD families from the audited @noble/hashes), which matters when you hash passwords or keys. - Can I use these hashes to store passwords?
No. MD5 and SHA are fast by design, which makes password guessing fast too. Store passwords with a slow, salted algorithm such as Argon2id, scrypt or bcrypt. - Which CRC-16 is this?
CRC-16/ARC (polynomial 0x8005, reflected, starting at 0), the one most hash pages call CRC-16: "123456789" gives bb3d. CRC-16/CCITT and Modbus use other settings and give other values. - Why is there no HMAC for CRC-32 or double SHA-256?
HMAC is defined for hash functions such as MD5 and SHA; a checksum has no key. SHAKE and BLAKE3 have keyed modes of their own, and xxHash is not a keyed hash, so they are left out too. With "HMAC with a key" on, the list shows the HMAC of every other row. - Why is my Keccak-256 different from SHA3-256?
SHA3-256 is Keccak with the padding byte FIPS 202 added (0x06 instead of 0x01). Ethereum and Solidity’s keccak256 use the original Keccak, so pick the Keccak-256 row: the empty string gives c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470. - How do I hash a password with bcrypt, Argon2 or scrypt?
Use the bcrypt page: password hashes are slow and salted on purpose, unlike the hashes here. It makes and checks bcrypt, Argon2id, scrypt and PBKDF2 hashes.