100% client-side · zero server upload · ad-free

HMAC Generator Online
Keyed Hash Message Authentication Codes

Generate an HMAC-SHA256 signature from a message and a secret key in milliseconds. This keyed hash message authentication code generator supports HMAC-MD5, HMAC-SHA1, HMAC-SHA256, HMAC-SHA384 and HMAC-SHA512, computed entirely inside your browser.

5 HMAC modes0 uploads<50ms local$0 free
Live
0 chars 0 bytes entropy 0.00
UPPERCASE
HMAC keyed mode
⌘⏎ recompute · copy signature · focus
Recent
Ready
Instant answer

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.

HMAC Generator

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

How to Generate an HMAC-SHA256 Signature in 3 Steps

  1. 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.

  2. 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.

  3. 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.

Why ToolGuest

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.

Algorithm specification

Hash algorithm bit lengths and hex lengths

Exact digest sizes, plus what each algorithm is for and whether it is safe for security work.

HMAC output sizes. An HMAC digest is exactly the same length as the underlying hash, so the hex length alone identifies which variant produced a signature.
Algorithm Digest size Hex characters Primary use Security guidance
HMAC-SHA256256-bit64The standard for webhook signatures and signed API requestsUse this unless a provider specifies otherwise
HMAC-SHA512512-bit128Higher-assurance API signatures and token schemesStrong; use when specified
HMAC-SHA1160-bit40Legacy OAuth 1.0 and TOTP implementationsSound as a MAC, but legacy
HMAC-MD5128-bit32Legacy signature schemes that predate SHA-2Sound as a MAC, but legacy
Head to head

ToolGuest hash generator vs. legacy web hash tools

Concrete differences that matter when the input is sensitive or the clock is running.

MetricToolGuestLegacy web hash tools
Data transmission0 bytes sent to a server — 100% local browserThird-party web requests
Key handlingKey stays in the browser tabKey sent to a remote server
HMAC variantsMD5, SHA-1, SHA-256, SHA-384, SHA-512Usually SHA-256 only
Execution speed<50ms instant local computeNetwork latency plus ad load
Ads and popupsZero, everCluttered banner ads
Offline readinessWorks offline once loadedNetwork dependent
Built for Tier-1 teams

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.

FAQ

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?

An HMAC, or keyed hash message authentication code, mixes a secret key into the hash computation. A plain hash is unkeyed: anyone who has the message can recompute the digest, so it proves only that the data has not changed accidentally. An HMAC can only be reproduced by someone holding the same key, so a valid HMAC also proves the message came from a party that knows the secret. That is the property webhook signature verification depends on.

How do I generate an HMAC-SHA256 signature online?

Switch on keyed mode on this page, paste the exact message into the input, and enter the shared secret into the key field. The HMAC-SHA256 signature appears immediately. If you are reproducing a webhook signature, paste the raw request body exactly as it was sent — any re-serialisation of JSON will change the bytes and therefore the signature.

Why is my HMAC signature different from the one the provider sent?

In almost every case the bytes differ, not the algorithm. The three usual causes are: the body was parsed and re-serialised as JSON rather than hashed raw, the signature was computed over a timestamp prefix as well as the body (a common scheme), or the key is not the raw secret but a Base64-decoded or hex-decoded form of it. Check the provider's documentation for the exact string it signs.

Is HMAC-MD5 still secure?

As a keyed message authentication code, HMAC-MD5 is still considered sound: the collision attacks that broke plain MD5 do not translate into forgery attacks against HMAC-MD5. That said, it is legacy, and new systems should use HMAC-SHA256. Keep HMAC-MD5 only for interoperability with a system that already uses it.

Is it safe to paste my signing secret into this HMAC generator?

The secret is processed entirely in your browser and is never transmitted, so there is no request carrying it anywhere. That is precisely why this tool exists rather than a server-side one: an HMAC generator that posts your key to a backend has handed that backend your signing secret. You can confirm the behaviour in your browser's network panel — no request contains the key.

Which HMAC algorithm should I use?

HMAC-SHA256 unless a provider specifies otherwise. It is what the overwhelming majority of payment processors, messaging platforms and API gateways use, it has no known practical weakness, and its 64-character output is universally supported. Use HMAC-SHA512 where a specification asks for a wider digest, and keep HMAC-SHA1 or HMAC-MD5 only for legacy schemes such as OAuth 1.0.

What is the difference between an HMAC and a digital signature?

An HMAC is symmetric: the same secret key both signs and verifies, so both parties must hold it. A digital signature is asymmetric: a private key signs and a public key verifies, so the verifier never needs the signing secret. HMAC is simpler and faster and is the right choice for shared-secret webhook verification; digital signatures are the right choice when the verifier must not be able to forge a signature.

Is this HMAC generator free?

Yes. There is no account, no payment, no quota and no advertising, because the computation happens on your own device. The page is a static file, so it keeps working offline once loaded.

Sign without exposing the key.

HMAC-SHA256 and four more keyed digests, computed entirely in your browser.

Open the generator