Hash functions and what they are good for
A hash function turns any input into a fixed-size fingerprint. The same input always produces the same hash, a tiny change produces a completely different one, and for cryptographic hashes it is practically impossible to find the input from the hash. Every hash generator in this category runs in your browser and shows the digest instantly, typically as hexadecimal.
Choosing a hash algorithm
| Purpose | Good choices | Avoid |
|---|---|---|
| File integrity and checksums | SHA-256, BLAKE2/BLAKE3, CRC-32 for non-adversarial error detection | — |
| Digital signatures and certificates | SHA-256, SHA-384, SHA-512, SHA-3 | MD5, SHA-1 |
| Message authentication | HMAC with SHA-256 | Plain hash of secret + message |
| Storing passwords | bcrypt, scrypt, Argon2 | MD5, SHA-1, plain SHA-256 |
| Legacy compatibility | MD5, SHA-1 | New security designs |
MD5 and SHA-1 are broken for security purposes because collisions can be created deliberately, but they remain common as non-security checksums and in legacy systems. Fast hashes such as SHA-256 are unsuitable for passwords because attackers can try billions of guesses per second; password hashing algorithms like bcrypt are deliberately slow and salted.
Tools in this category
- SHA-2 family (SHA-224 to SHA-512/256), SHA-3, Keccak and SHAKE, RIPEMD-160, Whirlpool, BLAKE2 and BLAKE3.
- Checksums: CRC-16, CRC-32, Adler-32 and xxHash, plus a checksum calculator for files.
- HMAC generator for signing webhook payloads and API requests.
- bcrypt and WordPress password hash generators and checkers for debugging login systems.
- Symmetric encryption and decryption, and the password generator for strong random passwords.
Reading hash output
Digests are usually shown as hexadecimal: MD5 produces 32 hex characters, SHA-1 40, SHA-256 64 and SHA-512 128. Some systems print the same bytes in Base64 instead, which is shorter. Hashes are also case-insensitive when written in hex, so AB12 and ab12 are the same value. When comparing a hash with a published checksum, make sure you hashed exactly the same bytes: line endings and a trailing newline change the result completely.
Common tasks
- Verify a download – hash the file and compare it with the checksum published by the vendor.
- Debug webhook signatures – compute the HMAC of the raw body with the shared secret and compare it with the signature header.
- Check a password hash – verify whether a password matches a stored bcrypt hash when a login fails.
The checksum calculator computes MD5, SHA-1, SHA-256, SHA-512, CRC-32 and more for a file or text at once, which is convenient when a vendor publishes several different checksums.
Hashing happens in your browser. Avoid entering real production passwords or secrets into any online tool, even one that works locally.