JWT Decoder
Decode and inspect JWT token header, payload and signature — no secret needed.
About JWT Decoder
Decodes a JSON Web Token's header and payload without needing the signing secret, showing the claims inside — issuer, subject, expiration, and any custom claims — in readable JSON. A JWT's payload is base64-encoded, not encrypted, so anyone holding the token can already read its contents. Useful for debugging an authentication flow where a token isn't accepted — checking the exp claim against the current time is the single most common cause of a rejected token. This tool decodes only; it does not verify a token's signature.
Older JWT libraries had a well-known vulnerability around the alg: "none" header value, where a token could be accepted with no signature check at all — modern libraries reject this by default, but it's worth confirming for a custom or older implementation.
Notes
Claims decoded:
iat, exp, nbf are shown as human dates.
Related Tools
The three parts of a JWT
A JWT is three URL-safe Base64 strings joined by dots: header.payload.signature. The header names the signing algorithm (alg), the payload holds the claims, and the signature proves the first two parts weren't changed. Only the signature needs a key; anyone can read the header and payload.
Standard claims
| Claim | Meaning |
|---|---|
iss | Issuer: who created the token |
sub | Subject: usually the user ID |
aud | Audience: which service should accept it |
exp | Expiry, as a Unix timestamp in seconds |
nbf | Not valid before this time |
iat | Issued at |
The decoder shows exp, nbf and iat as UTC dates and tells you whether the token has expired. Convert other timestamps with the Unix Timestamp Converter.
Why a valid-looking token is rejected
- Expired, or not yet valid: check
expandnbf. Clock skew between servers of a minute or two is a common cause; most libraries allow a small leeway setting. - Wrong audience or issuer:
aud/issmust match exactly what the API expects. - Algorithm mismatch: the server expects RS256 but the token is HS256, or the other way around.
- Wrong key: after key rotation, the
kidheader must match a key the server still has.
Security notes
- A JWT is signed, not encrypted. Don't put secrets or personal data in the payload.
- This tool decodes only and does not verify the signature. Verification must happen on the server with the expected algorithm fixed, never taken from the token.
- Decoding runs in your browser, but a live token is still a credential: prefer expired or test tokens.