Webhook Signature Verifier (HMAC)

Verifies a webhook's HMAC signature locally. Paste the raw body, the signature header and your signing secret, pick the provider and see the expected signature, a constant-time comparison and a timestamp check.

Use the tool

Why this tool exists

A webhook handler that rejects every request with "invalid signature" is a common and frustrating bug. The cause is usually small: the body was parsed and re-serialised before hashing, the secret has a trailing newline, the wrong header was used, or the timestamp window was exceeded. This tool lets you take a failing delivery and check it step by step. Paste the exact raw body and the headers, choose GitHub, Stripe, Slack, Shopify, Standard Webhooks (Svix) or a generic HMAC, and it computes the expected signature and compares it. Verification runs in your browser, but the signing secret is sensitive: use test secrets, or rotate a real one after debugging.

How to use it

  1. Paste the raw request body into the first box, exactly as received.
  2. Paste the signature header lines, or just the signature value, into the second box.
  3. Choose the provider, enter the signing secret, and set a timestamp tolerance if relevant. Then read the result.

Frequently asked questions

Why must the body be the raw bytes?

The signature is computed over the exact bytes sent. If your framework parses and re-serialises JSON first, spacing or key order can change and the HMAC no longer matches.

Which providers are supported?

GitHub (X-Hub-Signature-256), Stripe (Stripe-Signature), Slack (X-Slack-Signature), Shopify (X-Shopify-Hmac-Sha256), Standard Webhooks and Svix, and a generic HMAC in hex or Base64.

What does the timestamp tolerance do?

For providers that sign a timestamp, such as Stripe and Slack, it rejects requests older than the number of seconds you set. Zero skips the check. You can also set the current time to test old samples.

Is it safe to enter my secret?

The computation is local and nothing is uploaded, but treat the secret as sensitive. Prefer a test secret, and rotate a production secret if you pasted it anywhere.