JWT Decoder
Show the header and payload of a compact JWT, and compare exp, nbf, and iat with the clock.
About this tool
The first two parts are decoded as JSON. The third part is not checked against a key. The notes say the signature was not checked.
Do not paste a production token into a site you do not trust. This page does not send the token anywhere.
How to use it
- Paste a compact JWT, three base64url parts separated by dots.
- Decode it.
- Read the header and payload JSON. The signature is not checked.
Limitations
- Decoding does not verify the signature. The guide on decode versus verify explains that difference.
- exp, nbf, and iat are compared with the clock you can see. Other claims are only displayed.
Header and payload only
Two segments are parsed, the third is ignored
A compact token is split on dots after trimming. The page requires a non-empty header segment and a non-empty payload segment. Each of those is base64url: minus and underscore are turned back into plus and slash, padding equals signs are added to a multiple of four, and the bytes are parsed as JSON. The object printed in the panel is that header and that payload. The third segment, when present, is not checked, not printed as raw signature bytes, and not compared to any key. The notes always include a line that the signature was not checked and that the decode does not prove the token is authentic. Read /guides/jwt-decode-vs-verify/ for why those are different steps.
There is no key field on this page. Pasting a secret next to the token does nothing, because the secret is not an input. A token you minted with the HS256 generator can be opened here, and the claims will show, and the MAC will still be unverified. Trust in the issuer has to come from a verifier that has the key, not from a pretty JSON view.
Clock notes for exp and nbf
If the payload is an object with a finite exp, the page treats exp as seconds and compares exp times 1000 with the browser clock. A past exp is reported as expired for that clock. A future exp is reported as still in the future. If nbf is finite and still ahead of the same clock, a note says so. iat is not given its own comparison. It appears only because it is part of the payload JSON you can read. Other claims are displayed and not judged. A skewed clock changes the notes without changing the claims.
How a bad token fails
Fewer than two segments, or an empty header or payload segment, throws a message that a JWT needs a header and a payload separated by dots. Bad base64 or JSON that does not parse throws as well, and you get the exception rather than a partial object. Extra dots do not by themselves fail the parse: only the first two segments are decoded. An unsigned token that ends with a trailing dot still has those two segments, so it decodes, and the missing MAC is still not a verification. None of these outcomes is a cryptographic pass. They only mean the first two segments were JSON.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

