JWT Decoder
Paste a JSON Web Token and see what is inside: the header, the payload, the claims in plain language, the dates converted from Unix seconds, and whether the token has expired. The token is decoded in your browser and is never sent anywhere. This tool does not check the signature.
Status
Checking the time…
Algorithm: HS256
| Claim | Meaning | Value |
|---|---|---|
| sub | Subject | 1234567890 |
| iat | Issued at | 2018-01-18T01:30:22.000Z |
The signature is not checked here: a decoded token is not proof that it is genuine.
How it works
- Paste the token. A leading Bearer and line breaks are ignored.
- Read the status line: expired, still valid or not valid yet.
- Check the header, the payload and the list of claims.
- Copy the decoded result if you need it elsewhere.
What people use it for
Debugging a login
See why an API refuses a token: expired, wrong audience or not valid yet.
Checking claims
Read the subject, issuer, audience and the exact expiry time.
Learning how tokens work
See that the payload is only encoded, not encrypted.
Questions
- Does this verify the token?
- No. It only decodes it. Anyone can read a JWT's payload, and anyone can write one: trusting a token requires checking its signature with the right key on your server.
- Is it safe to paste a real token?
- The decoding happens in your browser and nothing is sent or stored. Even so, treat a live token like a password: prefer an expired or test token, and do not paste production tokens into sites you do not trust.
- How are the dates read?
- The exp, nbf and iat claims are numbers of seconds since 1 January 1970 UTC. The page converts them to dates and compares exp and nbf with the time on your device.
- What is a token with five parts?
- An encrypted token (JWE). Its content is not readable without the decryption key, so the tool says so instead of guessing.