Reading a token
Paste the token
The whole string, three parts separated by dots. It often starts with
eyJ. A sample token is loaded when the page opens.Read the dates
Issued, Expires and Not before are converted from Unix timestamps into dates and times, and (expired) is added when the expiry time has passed.
Look at the header
The header shows the signing algorithm, such as HS256 or RS256, and the token type.
Look at the payload
The claims are shown as formatted JSON: who the token is about (sub), who issued it, the audience, and any custom fields such as a role or account ID.
Example: why an integration suddenly stopped working
A small agency's reporting dashboard (fictional names throughout) stops pulling data from a client's tool, and the log shows the access token it was using. Decoding it shows a one-hour lifetime: issued at 09:00 UTC and expired at 10:00 UTC. The integration had been running on that token for hours without refreshing it, so the fix is in the refresh step, not in the client's account.
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyXzg4NDEiLCJlbWFpbCI6Im9wc0BraXRlYnJvb2suZXhhbXBsZSIsInJvbGUiOiJ2aWV3ZXIiLCJpYXQiOjE3OTQzMDEyMDAsImV4cCI6MTc5NDMwNDgwMH0.c2lnbmF0dXJl
Issued: 2026-11-10T09:00:00.000Z
Expires: 2026-11-10T10:00:00.000Z (expired)
Not before: n/a
Header: { "alg": "HS256", "typ": "JWT" }
Payload: { "sub": "user_8841", "email": "ops@kitebrook.example", "role": "viewer", "iat": 1794301200, "exp": 1794304800 }Common claims
- iat
- Issued at: when the token was created, as a Unix timestamp.
- exp
- Expiry: after this time the token should be refused.
- nbf
- Not before: the token should be refused until this time.
- sub
- Subject: the user or account the token is about.
- iss
- Issuer: the service that created the token.
- aud
- Audience: the service the token is meant for.
Questions people ask
Is it safe to paste a JWT into a website?
Only if the site decodes it locally, as this page does: the token never leaves your browser. Even so, treat live tokens like passwords. A valid, unexpired token can often be used to act as that user until it expires, so avoid sharing it in screenshots, tickets or chat messages.
Why can anyone read a JWT?
The header and payload are encoded with base64url, which is a way of writing data as text, not encryption. The signature only proves the token has not been altered and was issued by someone holding the key. That is why tokens should never contain passwords, card numbers or other secrets.
What does the error about three parts mean?
A JWT always has a header, a payload and a signature joined by two dots. If the text has fewer parts, something is missing, often because the token was cut off when copied from a log or a long line in an email. Copy it again in full and paste it once more.
How do I convert the iat or exp number myself?
They are Unix timestamps: seconds since 1 January 1970, UTC. This page converts them automatically, but you can also paste a number into the Unix timestamp converter on this site to see it in your local time zone.
Where your data goes
The token is decoded on this page in your browser. It is not sent to Map Extract or anywhere else, and the signature is not checked against any server.
Checked against the tool on