Anatomy of a JWT
A JWT (RFC 7519) is three Base64URL strings joined by dots: header (algorithm and type), payload (the claims) and signature. The first two are just encoded JSON — anyone holding the token can read them, which is exactly what this page does. Never put secrets in a JWT payload.
Decoding is not verifying
The signature proves the token was issued by someone holding the key. Checking it needs that secret (HS256) or public key (RS256/ES256), and should happen on your server with a maintained library. This decoder does not verify signatures, so it never asks for your key.
Standard claims
| Claim | Meaning |
|---|---|
iss | Issuer — who created the token |
sub | Subject — usually the user ID |
aud | Audience — who the token is for |
exp | Expiry time (Unix seconds) |
nbf | Not valid before |
iat | Issued at |
jti | Unique token ID |