Choose the algorithm
Pick a hash such as SHA-256, or pick an HMAC variant if the digest must be keyed.
Hash any text with MD5, SHA-1, SHA-256 or SHA-512, or compute a keyed HMAC for request signing and webhook verification. Everything is calculated in your browser, so your text and key stay on your device.
A fixed length fingerprint of any text, calculated on your device.
Pick a hash such as SHA-256, or pick an HMAC variant if the digest must be keyed.
Type or paste the string you want to hash into the input box.
Select Calculate Hash, then copy the digest. For HMAC, enter or generate a key before calculating.
SHA-256 covers most needs. The older functions are here so you can verify legacy values.
| Algorithm | Digest length | Use it for |
|---|---|---|
| SHA-256 | 256 bits | Default choice for checksums, integrity checks and signing |
| SHA-512 | 512 bits | Integrity checks where a longer digest is preferred |
| SHA-1 | 160 bits | Verifying old checksums, not suitable for security decisions |
| MD5 | 128 bits | Legacy file checksums only, never for security |
| HMAC variants | Same as the base hash | Keyed digests for webhooks, API signatures and message authentication |
Not for passwords: this tool produces fast hashes for checksums and message digests. Password storage needs a slow, salted function such as Argon2, bcrypt or scrypt.
Everything needed for a quick digest, a comparison or a signed payload.
Calculate MD5, SHA-1, SHA-256 or SHA-512 digests from the same input box.
Compute an HMAC with your own key, or generate a random key and copy it.
Copy the digest to the clipboard in one click, ready to paste into a test or a header.
Hashing runs in your browser, so neither the text nor the HMAC key is uploaded.
No. Hashing and HMAC calculation run with JavaScript in your browser, so your text and your key never leave your device.
Use SHA-256 or SHA-512 for anything new. MD5 and SHA-1 remain available for verifying legacy checksums, but they are not collision resistant and should not be used for security decisions.
A plain hash can be recalculated by anyone who has the text. An HMAC mixes in a secret key, so only holders of that key can produce or verify the value, which makes it suitable for signing requests and webhooks.
No. A hash is a one way function that compresses input into a fixed length digest. The only way to find the original text is to guess it and compare, which is why password storage needs a slow, salted function rather than a fast hash.
The most common causes are a trailing newline in one of the inputs, a different character encoding, or a different output case. Hash the exact same bytes, including any whitespace, to get an identical digest.
No. Password storage requires a slow, salted function such as Argon2, bcrypt or scrypt, which this tool does not provide. Use it for checksums and message digests instead.