What it does
A hash function turns any input into a short fixed-length fingerprint. The same input always gives the same hash, and even a one-character change produces a completely different result. Hashes are used to verify downloads, detect changes and identify content.
Which algorithm?
- SHA-256, SHA-384, SHA-512 are current, secure choices for integrity checks and signatures.
- MD5 and SHA-1 are broken for security purposes (collisions can be created). They are still common for non-security checksums and legacy systems, so they are included here.
More algorithms
- SHA3-224, -256, -384, -512 are the NIST SHA-3 (Keccak) functions. They are not the same as the older Keccak submissions that some blockchains call "keccak256".
- BLAKE2b-512 and BLAKE2s-256 (RFC 7693) are fast modern hashes. Only the unkeyed, default-length forms are offered.
- CRC-32, CRC-32C and Adler-32 are checksums that catch accidental damage. They are not secure: anyone can create data with a chosen checksum. Do not use them to prove that data is genuine.
These run in a background worker and only when you press Compute, so the page stays responsive. They are slower than SHA-256 because the browser has no built-in version: expect roughly 10 to 60 MB per second, so a 200 MB file can take several seconds per algorithm. Pick only what you need, and use Cancel to stop.
Compare with an expected hash
Paste the checksum a publisher lists. Case, spaces, colons and a leading 0x are ignored, and every hash on this page is checked: MD5, SHA-1, SHA-2, the HMAC if you entered a key, and any extra algorithm you computed. A match means the bytes are identical to what the publisher hashed. It cannot tell you whether the publisher or the page that listed the checksum can be trusted. Base64 digests are not compared.
PBKDF2 key derivation
PBKDF2 (RFC 8018) turns a password and a salt into a key by repeating HMAC many times, using your browser's WebCrypto. A warning appears when the iteration count is below current OWASP guidance (600,000 for SHA-256, 220,000 for SHA-512) or the salt is short. For storing user passwords prefer bcrypt, scrypt or Argon2, which are not offered here. The password, salt and key are not stored or sent anywhere.
Verify a checksum file
Choose a file in sha256sum or md5sum style (hash name) or BSD style (SHA256 (name) = hash), then the files it lists. Each listed file is shown as OK, FAILED or MISSING. Names are matched exactly, then by the last part of a path. The algorithm is guessed from the hash length (64 digits is read as SHA-256); choose it by hand for SHA3-256, BLAKE2s or similar. Files stay on your device and are read in a background worker.
Important
Hashes are not encryption and are not suitable on their own for storing passwords. Use a slow, salted algorithm such as bcrypt, scrypt or Argon2 for that. HMAC combines a hash with a secret key to prove a message came from someone who knows the key.
Example
The text abc has the MD5 hash 900150983cd24fb0d6963f7d28e17f72 and the SHA-256 hash ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. Adding a trailing newline, as echo abc does in a terminal, gives a different hash, so a mismatch with a command-line result is often a line break. Text is hashed as UTF-8 bytes.
Using the tool
- Verify a download: choose the file, then compare the SHA-256 row with the checksum the publisher lists. Hex digits are not case sensitive, so use "Uppercase hex" if the published value is upper case.
- Text or file: when a file is chosen, it is hashed instead of the text box. Press Clear to go back to text. Files above 200 MB are refused with a message.
- HMAC: enter a secret key to get an HMAC of the same text or file with the chosen algorithm. The key is read as UTF-8 text; for a binary key, use a tool that accepts hex.
Hashing is not encoding
A hash cannot be turned back into the original data, unlike Base64, which is only a reversible encoding. HMAC with SHA-256 is the signature used by HS256 tokens, which you can build with the JWT Generator or read with the JWT Decoder. Certificate fingerprints are hashes of the certificate bytes and are shown by the X.509 Certificate Inspector. To create secrets worth keeping, use the Password Generator rather than hashing a short word.
Privacy
This tool runs entirely in your browser. Files you choose are read on your device and are never uploaded.