🔑 JWT Decoder
Decode and inspect JSON Web Tokens. Nothing leaves your browser.
Last updated: November 8, 2026 · By the BoltQuickTools team
Reading the contents of a JSON Web Token
When an API returns 401, or a login works for one user and not another, you often need to see which claims the token really carries. A JWT is Base64URL text, so it is unreadable at a glance. This page splits it into header, payload and signature and shows the claims with readable dates.
Decoding a token
- Paste the token into Paste JWT Token. Pasting decodes automatically. If you type or edit the token instead, click Decode.
- Check the banner at the top of the results, then read the Header and Payload JSON and the Claims list.
- Encoded Token colours the three segments so you can see where each one starts. Load Sample fills in a test token and Clear empties the page.
The sample token, decoded
Click Load Sample and the two JSON blocks show:
{
"alg": "HS256",
"typ": "JWT"
}
{
"sub": "1234567890",
"name": "John Doe",
"email": "[email protected]",
"role": "admin",
"iat": 1716239022,
"exp": 1816239022
}
The Claims list relabels known keys and converts the timestamps to your local time zone, with a relative age after each:
| Label shown | Claim | Value |
|---|---|---|
| Subject | sub | 1234567890 |
| Name | name | John Doe |
email | [email protected] | |
| Role | role | admin |
| Issued At | iat | 20 May 2024, 21:03:42 UTC |
| Expires At | exp | 22 July 2027, 06:50:22 UTC |
The banner reads Token valid until that expiry passes, and Token EXPIRED after it. A token with no exp shows No expiration claim (exp) found.
What the banner does not tell you
- The signature is never checked.
Token validonly means theexptime has not passed on your device clock. A forged token with a futureexpgets the same green banner. nbfis displayed but not enforced. A token that is not valid until next year still reads as valid.- Odd
expvalues are handled loosely.exp: 0is reported as having no expiry. A non-numericexpshowsToken validwithInvalid Date. Anexpin milliseconds lands thousands of years ahead. - Exactly three dot-separated parts are required. Anything else gets
Invalid JWT: Expected 3 parts, so encrypted five-part JWE tokens are rejected. - Paste only the token. With the
Bearerprefix still attached you getFailed to decode header. - A payload of the JSON value
nullstops the script with no message, leaving any earlier results on screen.
To verify a signature, use your server's JWT library with the real key. To produce test tokens to feed into this page, use the JWT generator. For a lone timestamp, the timestamp converter is quicker, and web security basics covers the wider context.
Things people ask about decoded tokens
Why can anyone read my token without the secret?
The header and payload are encoded, not encrypted. The secret only protects the signature, which proves the contents were not altered. Keep anything confidential out of the payload.
Why does a token show as expired when it just worked?
The comparison uses your device clock. If that clock is ahead of the server's, a token can look expired here while the server still accepts it. Many servers also allow a little clock skew.
Is it safe to paste a production token?
The decoding code in this page makes no network requests. The page does load analytics, plus ads if you accept them, and any valid token is a credential until it expires. Prefer a token from a test account, or one that has already expired.