The key is used only in this tab. It is never transmitted, stored or logged.
An HMAC generator produces a keyed hash message authentication code by mixing a secret key with a message before hashing. Unlike a plain digest, an HMAC proves both integrity and authenticity, which is why HMAC-SHA256 signatures verify webhook deliveries and signed API requests. ToolGuest computes HMAC digests locally in your browser.
What this hmac generator does
An HMAC — a keyed hash message authentication code — is what you get when a secret key is mixed into a hash computation. A plain digest proves only that the data has not changed: anyone can recompute it, so it says nothing about who produced it. An HMAC proves that whoever produced the message also held the key, which is exactly the property you need when a webhook arrives and you must decide whether to trust it.
This HMAC generator online supports HMAC-MD5, HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512. Enter the message, enter the key, and the keyed digest for every algorithm appears at once. HMAC-SHA256 is the default because it is what most payment processors, messaging platforms and API gateways use to sign their deliveries.
The key never leaves your browser. Both the key and the message are processed in the tab by the Web Crypto API, so testing a webhook signature with a real production secret does not involve sending that secret to a third-party site. That matters: an HMAC generator that posts your key to a server is exactly the wrong tool for the job.
How to Generate an HMAC-SHA256 Signature in 3 Steps
- 01
Turn on keyed mode
Switch the keyed toggle so the secret key field appears. The tool then computes HMAC digests instead of plain hashes.
- 02
Enter the message and the key
Paste the exact message or webhook body, then the shared secret. Both are processed locally and never transmitted.
- 03
Copy or compare the signature
Copy the HMAC-SHA256 value, or paste the expected signature into the verifier to confirm your implementation matches the provider's.
Built for speed, privacy and accuracy
Every digest is computed on your own device, with no server in the middle.
Keyed digests, five algorithms
HMAC-MD5, HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512 all computed from the same message and key.
Your key never leaves the tab
Both key and message are processed locally by the Web Crypto API. A production signing secret is never transmitted.
Webhook signature testing
Reproduce the HMAC-SHA256 a provider computes over a raw request body to confirm your verification code is correct.
Native constant-time HMAC
SHA-family HMACs use the browser's own importKey and sign routines, not a JavaScript reimplementation.
Signature verifier
Paste the expected signature and the tool confirms which variant matches, normalising case.
Free, ad-free, offline
No account, no quota, no banners. Works with the network off once loaded.
Hash algorithm bit lengths and hex lengths
Exact digest sizes, plus what each algorithm is for and whether it is safe for security work.
| Algorithm | Digest size | Hex characters | Primary use | Security guidance |
|---|---|---|---|---|
| HMAC-SHA256 | 256-bit | 64 | The standard for webhook signatures and signed API requests | Use this unless a provider specifies otherwise |
| HMAC-SHA512 | 512-bit | 128 | Higher-assurance API signatures and token schemes | Strong; use when specified |
| HMAC-SHA1 | 160-bit | 40 | Legacy OAuth 1.0 and TOTP implementations | Sound as a MAC, but legacy |
| HMAC-MD5 | 128-bit | 32 | Legacy signature schemes that predate SHA-2 | Sound as a MAC, but legacy |
ToolGuest hash generator vs. legacy web hash tools
Concrete differences that matter when the input is sensitive or the clock is running.
| Metric | ToolGuest | Legacy web hash tools |
|---|---|---|
| Data transmission | 0 bytes sent to a server — 100% local browser | Third-party web requests |
| Key handling | Key stays in the browser tab | Key sent to a remote server |
| HMAC variants | MD5, SHA-1, SHA-256, SHA-384, SHA-512 | Usually SHA-256 only |
| Execution speed | <50ms instant local compute | Network latency plus ad load |
| Ads and popups | Zero, ever | Cluttered banner ads |
| Offline readiness | Works offline once loaded | Network dependent |
Used by engineers in the USA, UK, Germany, Canada, Australia and Spain
One English page serves every market, so a release engineer in Seattle and one in Dublin verify files the same way.
Seattle · United States
Engineers reproduce provider HMAC-SHA256 signatures while debugging webhooks.
London · United Kingdom
Security teams confirm signing schemes without exposing secrets.
Berlin · Germany
Developers test payment gateway signature verification locally.
Toronto · Canada
IT teams validate signed API requests before rollout.
Sydney · Australia
Teams debug timestamp-prefixed signature schemes.
Madrid · Spain
Developers verify TOTP and legacy HMAC constructions.
HMAC Generator questions, answered
The questions developers and security teams ask most about SHA-256 hashing.
What is an HMAC and how is it different from a plain hash?
How do I generate an HMAC-SHA256 signature online?
Why is my HMAC signature different from the one the provider sent?
Is HMAC-MD5 still secure?
Is it safe to paste my signing secret into this HMAC generator?
Which HMAC algorithm should I use?
What is the difference between an HMAC and a digital signature?
Is this HMAC generator free?
Specialised hash, checksum and cryptography tools
Every page shares one hashing engine and one privacy model. Pick the digest you need.
Sign without exposing the key.
HMAC-SHA256 and four more keyed digests, computed entirely in your browser.
Open the generator