Free Online HMAC Generator for SHA-256, SHA-1, SHA-384 and SHA-512
Work out an HMAC over any text with SHA-1, SHA-256, SHA-384 or SHA-512. The key can be read as text, as hex or as base64, which is the usual reason a webhook signature does not match, and the result is given as hex and base64 together. Paste the signature you were sent and the page says whether it agrees.
Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.
How to Use HMAC Generator
Step by step, start to finish.
Exactly what was signed. For a webhook that means the raw request body, before any parsing, including a trailing newline if there is one.
Text, hex or base64. Getting this wrong is the most common cause of a mismatch, because the wrong reading still produces a confident looking HMAC.
SHA-256 unless the documentation says otherwise. SHA-1 is still used by some older providers and is acceptable inside HMAC, which is explained in the notes.
Paste the signature into the compare box in any of the four forms. The page tells you which form it recognised and whether it agrees.
Key Features
What this tool does, and what it does not do.
SHA-1, SHA-256, SHA-384 and SHA-512, all through the browser own Web Crypto.
As text, as hex or as base64, with the byte length shown so you can sanity check it.
Hex in both cases, base64 and base64url, so no conversion is needed to compare.
Recognises any of the four forms, and strips a scheme prefix if there is one.
The four real causes of a failed webhook check, in the order worth trying.
A real signing secret can be used here without it leaving the tab.
About HMAC Generator
An HMAC answers a narrow question: did this message come from someone holding the shared key, and has it been changed. It is the primitive behind webhook signatures, signed URLs, API request signing and session cookies, and it is built from an ordinary hash used twice with two keys derived from yours. That construction is what makes it safe where a plain hash of the secret and the message joined together is not.
This page exists mostly for debugging, because an HMAC that does not match is a miserable thing to chase. The arithmetic is never the problem: it is in the browser own cryptography here and in a vetted library at the other end. What differs is the input. The key is often hex or base64 and gets read as text, the message is often a re-serialised copy of the body rather than the raw bytes, and the two sides often disagree about hex versus base64. All three are visible on this page at once, which usually makes the answer obvious within a minute.
What the page deliberately does not do is pretend to validate anything. A matching HMAC tells you the sender had the key, and nothing about whether the request is fresh, whether it has already been processed, or whether the key has since been rotated. Those are decisions for the system receiving the request, and a tool that implied otherwise would be teaching the wrong lesson.
Frequently Asked Questions
Common questions about this tool.