Hash & HMAC Generator
Generate cryptographic hashes (SHA-1, SHA-256, SHA-512, SHA-3, plus MD5 and CRC32 for compatibility) of text and HMAC signatures that use a secret key. Use it to check that a webhook or API signature (such as GitHub's sha256=) matches the HMAC you compute from the payload and a shared secret, to create hashes for config values or cache keys, and to compare how each algorithm transforms the same input. Output is lowercase hexadecimal. Text is hashed as UTF-8, so it cannot hash a file (it cannot be used to verify a downloaded file's checksum), and MD5 and SHA-384 are not supported. To store passwords, use bcrypt or Argon2. All hashing runs locally in your browser, so the text and secret you enter are never sent to a server.
Configuration
All algorithms at once
Shown for the current input in the selected output format.
Verify a webhook signature
Paste the body exactly as received, your signing secret and the signature header. It recomputes the HMAC and tells you whether it matches (GitHub, Stripe, Slack or generic). Everything stays in your browser.
GuideHow to use & features
- Paste text into the input field and choose a hash algorithm.
- Provide a secret key when you need an HMAC output.
- The output is shown in hexadecimal (hex) format.
- Copy the result for API testing, signatures, or integrity checks.
SamplesSample input & output
Hash SHA-256
Algoritmo: SHA-256 Texto: hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
FAQFAQ
Which algorithms are supported?
SHA-256, SHA-512 and SHA-1. They are computed with the browser's standard Web Crypto API, so results match other environments.What is HMAC?
A hash made with a secret key for tamper detection. Only a party with the same key can produce the same value. It is used to check webhook and API signatures.Is MD5 supported?
Yes. MD5, SHA-3 (224 / 256 / 384 / 512) and CRC32 are not in the browser's standard API, so the tool computes them itself (MD5 and SHA-3 also have HMAC). MD5 and CRC32 are not for tamper detection or signatures, though; use them to match files or stay compatible with old systems.What format is the output?
A lowercase hexadecimal string: 64 characters for SHA-256, 128 for SHA-512 and 40 for SHA-1.What happens with Japanese text?
The text is turned into UTF-8 bytes before hashing. When comparing against another tool, match the character encoding and whether there is a trailing newline.Can I use it to store passwords?
No. SHA-256 and similar are fast to compute, so use a dedicated method such as bcrypt, scrypt or Argon2 to store passwords.
Use casesCommon use cases
Checking a webhook signature
Confirm by hand that a `sha256=...` value sent by GitHub or others equals the HMAC-SHA256 of the payload and secret.Testing an API signature
See the values while you work out how an HMAC-signed API builds its signature, before implementing it.Getting the SHA-256 of text
Quickly create a hash for a config value, a cache key or an identity check.Preparing sample hashes for documentation
Produce example hash values to put in documents.
NotesNotes & limitations
MD5 and CRC32 are not for security
Besides SHA-1, SHA-256, SHA-384, SHA-512 and SHA-3 you can also get MD5 and CRC32. But different data can be made to share an MD5 hash, and CRC32 only detects accidental errors. Use them to match files or stay compatible with old systems, and use SHA-256 or stronger for signatures and tamper detection. CRC32 has no HMAC.Do not use it to store passwords
General-purpose hashes are fast, which makes them weak against brute force. Store passwords with a dedicated method such as bcrypt, scrypt or Argon2.Do not use SHA-1 for security
Collision attacks are known. Use it only for compatibility with old systems or plain identification, not for signatures or security checks.One character of difference changes the value
A trailing newline and whitespace are included. The HMAC secret is used as a UTF-8 string, so a Base64 or hex key cannot be treated as raw bytes.
AboutAbout this tool
Hash and HMAC Generator
Hash functions and HMAC signatures are used to verify integrity, compare data, sign webhook payloads, and debug authentication flows. This tool helps generate common SHA hashes and HMAC values in the browser from text input.
Common use cases
- Verify file or payload integrity: Compare expected and actual hash values during debugging.
- Debug webhook signatures: Recreate HMAC values from a payload and shared secret.
- Generate test fixtures: Prepare sample hashes for documentation, tests, or API examples.
Security note
Plain hashes are not suitable for storing passwords without a dedicated password hashing algorithm and salt. HMAC secrets and production payloads should be handled carefully and should not be shared in public examples.
Articles for this tool
JWT Security Deep Dive: Attack Vectors, JWKS, and Production Best Practices
A guide to JWT security: the alg:none attack, algorithm confusion, key management with JWKS, token revocation strategies, and a production security checklist.
Hashing, Salt, and HMAC: A Developer's Guide to Secure Data Handling
How SHA-256, bcrypt and Argon2 work, why salting passwords is non-negotiable, when to use HMAC vs plain hashing, with patterns in JavaScript, Python and Go.
Encoding vs Hashing vs Encryption: The Difference and When to Use Each
Base64 encoding, SHA-256 hashing and encryption are constantly confused but serve different purposes. A comparison table, examples, and when to use each.
