JWT Decoder and Signature Verifier
Decode JWT header and payload, inspect claims and expiry, and verify HS256/384/512 or RS/ES signatures locally in your browser.
JWT Token
Decoding and signature verification run entirely in your browser. Tokens are never uploaded.
Signature Verification
RS / ES signatures are verified with the Web Crypto API. No key or token leaves the page.
Expiry is evaluated against your local system clock, which may differ from the server.
Header
Payload
Claims
About This Tool
The JWT decoder turns a compact token into readable header and payload JSON, explains the standard claims and tells you whether the token is currently valid, expired or not yet active. Expiry is compared against your local clock, and the page reminds you that a time offset between your machine and the server can change the result.
Signature verification runs locally as well. HS256, HS384 and HS512 signatures are recomputed from the shared secret, while RS and ES signatures are checked with the Web Crypto API using a pasted public key. Nothing is sent to a server, which matters when the token belongs to a real user session.
Key Features
Full claim breakdown
Header, payload and a claim table with plain-language meaning for iss, sub, aud, exp, nbf, iat and more.
Expiry status
Shows valid, expired or not-yet-valid with the exact local time and remaining seconds.
Local signature check
Recomputes HMAC signatures or verifies RS / ES signatures with a pasted public key, without network access.
When to Use It
Integration debugging
Check which scopes, roles and audience a token actually carries instead of guessing from server logs.
Expiry investigation
Confirm whether a 401 response comes from an expired token, an early nbf claim or clock skew.
Signature sanity check
Verify that a token was signed with the secret or key you expect before blaming the gateway.
How to Use It
- 1Paste the token into the input area.
- 2Read the decoded header, payload and claim table.
- 3Check the expiry banner and local time details.
- 4For HMAC tokens enter the shared secret, or paste a public key for RS / ES, then verify the signature.
Frequently Asked Questions
Is my token uploaded anywhere?
No. Decoding, claim analysis and signature verification all run in the browser. The page never calls an API and never stores the token.
Why does signature verification fail with a correct secret?
Check that the alg header matches the secret type, that the secret is used as raw text rather than base64, and that the token was not truncated when copied.
