HMAC + Hash Generator
Generate SHA-256/SHA-512 hashes and HMAC signatures for API requests or webhook checks entirely in your browser.
Message and secret
Enter a message and optional HMAC secret
Masked by default. Screen sharing, browser extensions, clipboard history, and local device access can still expose secrets.
Signature output
Hash or HMAC output
Hex and Base64 output appears here.
How to verify webhook signatures
Paste the exact webhook body or API message, choose the signing algorithm, enter the shared secret, and generate the HMAC. Then paste the expected signature from the request header to compare the values.
The verifier accepts raw hex, Base64, and common prefixed formats such as sha256=....
Hashing is not password storage
SHA-256 and SHA-512 are fast cryptographic hashes. They are useful for checksums and signatures, but they are not password hashing algorithms. Use Argon2id, bcrypt, or scrypt for storing user passwords.
What this HMAC / Hash does
Use this HMAC SHA256 generator, SHA256 hash generator, SHA512 hash generator, verify HMAC signature tool, and webhook signature checker for browser-local API debugging. It produces hex and Base64 outputs for SHA-256, SHA-512, HMAC SHA-256, and HMAC SHA-512.
When developers use it
- Verify webhook signatures by hashing the exact request body with the shared secret and comparing the expected header value.
- Generate SHA-256 or SHA-512 hashes for payload checksums, fixture verification, and integration debugging.
- Compare raw hex, Base64, or prefixed values such as sha256=... without uploading secrets or request bodies.
Privacy, input, and output
Hashing and HMAC signing use Web Crypto locally in your browser session. PayloadHarbor does not upload the message, secret, or generated signature.
Paste the message or payload, choose hash-only or HMAC mode, select SHA-256 or SHA-512, and optionally paste an expected signature. The output shows hex and Base64 values with copy and download controls.
Validation rules and limitations
- This tool is for API signatures, webhook checks, and checksums; SHA-256 and SHA-512 are not safe password-storage algorithms.
- HMAC verification only confirms that the provided message, secret, and expected signature match; it does not validate timestamp freshness, replay windows, or provider-specific canonicalization rules.