API Toolkit

JWT Verify

All tools

Confirm an HS256 token was signed with the secret you expect, without sending either anywhere.

How it works

Four simple steps

1

Paste the JWT

Add the full three-part token.

2

Enter the secret

Type the HS256 shared secret; the field is masked.

3

Press Verify

The HMAC is recomputed and compared with the signature.

4

Read the result

VALID or INVALID appears above the decoded payload.

JWT Verify

About JWT Verify

Your API started returning 401 after a deploy, and you suspect the staging and production services no longer share the same signing secret. Checking one failing token against each candidate secret settles the question in under a minute.

Paste the token, type the secret and press Verify. The tool takes the first two segments exactly as they appear, computes HMAC-SHA256 over them with your secret through the Web Crypto API, encodes the result as Base64URL and compares it with the third segment. You see VALID signature or INVALID signature, followed by the decoded payload so you can confirm you checked the right token.

It always uses HS256 and does not read the alg value from the header, so RS256 or ES256 tokens simply show as invalid; those need the issuer's public key in your own code. The secret is used as the UTF-8 text you type. If your provider stores the secret Base64-encoded and signs with the decoded bytes, this page cannot reproduce that. Expiry, issuer and audience are not checked, so read them with the JWT decoder or the token expiry checker. To create a correctly signed test token for comparison, use the HS256 JWT generator.

The secret field is masked, and both values stay in the page for the HMAC calculation. Clear them when you finish on a shared machine.

Keyboard shortcut

Ctrl Enter - Run tool

Use cases

Signature debugging

Confirm HS256 tokens against the secret your service uses.

Env mismatch checks

See whether staging tokens fail because the secret differs.

Security demos

Show valid vs tampered payloads without a cloud JWT site.

Instructions

How to use this tool

FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. It only checks the signature. An expired token with a correct signature still shows as VALID, so look at exp separately.

This page only computes HS256. RS256 and ES256 sign with a private key and verify with a public key, which is a different check from an HMAC with a shared secret.

Yes. The secret is used exactly as typed, so a trailing space or newline copied from a config file produces a different signature. Retype or trim it if a token you expect to pass fails.

View more FAQs

Related tools

View all

Webhook HMAC Signer

Sign and verify GitHub, Stripe, and Slack webhook signatures locally.

Open

Webhook Replay Diff Lab

Compare webhook payload timelines, re-check HMAC digests, and spot idempotency gaps locally.

Open

JSONPath Playground

Query JSON with JSONPath and JMESPath-style paths side by side.

Open

GraphQL Studio

Format, validate, and cost-estimate GraphQL documents with cURL export.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools