Anatomy of a JWT
- Header — the signing algorithm (alg) and token type (typ).
- Payload — the claims: who issued the token, for whom, and until when it's valid.
- Signature — made with the server's key; only it proves the token hasn't been changed.
The parts are base64url-encoded and separated by dots. Base64 is encoding, not encryption — anyone can read a token's payload.
Registered claims
| Claim | Meaning |
|---|---|
| iss | issuer |
| sub | subject (e.g. user ID) |
| aud | audience — the service it's for |
| exp | expiry time (Unix time) |
| nbf | not valid before |
| iat | issued at |
Convert Unix times with the timestamp converter.
Frequently asked questions
Is it safe to paste a token here?
The token is decoded only in your browser and never sent anywhere. Still, treat live tokens like passwords and don't paste them into sites you don't trust.
Why isn't the signature verified?
Verification needs the server's secret or public key. Being able to read a token doesn't mean it's genuine.