Practical guide
Inspect the header and payload of a JSON Web Token while debugging a system you control. Decoding reveals claims but does not verify who issued them or whether the signature is valid.
Steps that matter
- Prefer a test token with no real personal data or active production permissions.
- Paste the complete token and inspect its header, payload and interpreted time claims.
- Perform signature, issuer, audience and policy validation in the receiving application before trusting any claim.
Worked example
An exp claim is a timestamp in seconds since the Unix epoch. A decoded token with a future exp can still have a forged signature, the wrong audience or revoked permissions.
Check before using the result
- The decoder does not decrypt encrypted tokens or validate a token for authentication.
- Treat tokens as credentials even if their payload looks harmless. Do not include them in bug-report emails or screenshots.