JWT Decoder
Decode and inspect JSON Web Token header, payload, expiry, and claims.
Client-Side Execution & Privacy Guarantee
This utility executes 100% locally in your web browser. Your inputs, tokens, queries, and data payloads are never transmitted to any external server or backend.
A JSON Web Token consists of three Base64url-encoded parts separated by dots: header, payload, and signature. The first two parts are JSON objects that can be read by anyone who possesses the token.
This tool splits the token, decodes the header and payload, and presents the claims in readable form. It does not verify the signature; verification requires the signing key and is performed by the service that issued the token.
Structure of a JWT
The header typically contains the algorithm (alg) and the token type (typ). The payload contains the claims: registered claims such as iss, sub, aud, exp, nbf, and iat, plus any private claims the issuer chose to include.
The signature is the third segment. It is produced by signing the concatenated header and payload with the secret or private key indicated by the algorithm. Without the key the signature cannot be checked.
Expiration and time claims
The exp claim is a Unix timestamp indicating when the token should no longer be accepted. The tool converts this value to a human-readable date and indicates whether the token has already expired relative to the current time.
Other time claims (nbf, iat) are likewise converted. Clock skew between the issuer and the verifier is common, so a token that appears slightly expired may still be accepted by the real service.
What decoding does not prove
Anyone can create a JWT with arbitrary claims and a forged signature. Decoding shows you the contents but gives no assurance that the token was issued by the expected party or that it has not been altered.
Use the decoded information for debugging and inspection. Always perform proper signature verification and claim validation in the application that trusts the token.
When to use this tool
- Inspecting the claims inside an access or ID token
- Checking whether a token has expired
- Debugging authentication failures caused by missing or unexpected claims
- Learning the structure of JWTs during development
- Extracting a user identifier or role without calling the issuer
How to use the JWT Decoder
- Paste the complete JWT (three segments separated by dots) into the input.
- Click decode.
- Examine the header for the algorithm and type.
- Review the payload claims, paying attention to exp, iss, aud, and any custom fields.
- Note the expiration status shown by the tool.
- Copy individual claim values if you need them for further testing.
- Do not paste production tokens that grant access to sensitive systems into untrusted pages; this tool runs locally, but browser extensions or other scripts on the same page could still observe the input.
Worked examples
Standard example token
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
Header: {"alg":"HS256","typ":"JWT"}\nPayload: {"sub":"1234567890","name":"John Doe","iat":1516239022}
The signature is not verified. The iat claim is the issued-at timestamp.
Token with expiration
eyJhbGciOiJub25lIn0.eyJzdWIiOiJ1c2VyMSIsImV4cCI6MTUxNjIzOTAyMn0.
Header: {"alg":"none"}\nPayload: {"sub":"user1","exp":1516239022}
An alg of none indicates an unsigned token. The exp claim shows the token expired in 2018.
Common mistakes and tips
- Never rely on client-side decoding for authorization decisions. The signature must be verified on the server.
- Tokens with alg none or an empty signature should be rejected by any production verifier.
- The tool displays times in your local timezone. Compare them with the issuer’s clock if timing issues appear.
- Base64url encoding omits padding. The decoder adds any required padding automatically.
- Large tokens or tokens containing binary claims are rare; most payloads are small JSON objects.
Frequently asked questions
Does the tool verify the signature?
No. It only decodes the header and payload. Signature verification requires the correct key and must be performed by the trusting party.
What does an expired token look like?
The exp claim is in the past. The tool highlights this condition so you can see it immediately.
Can I decode a token that uses RS256 or ES256?
Yes. The algorithm is shown in the header, but the signature is not checked regardless of the algorithm.
Why is the payload sometimes unreadable?
If the middle segment is not valid Base64url or does not decode to JSON, the tool reports an error. Malformed tokens cannot be inspected.
Is it safe to paste a real token?
Processing is local, but any token that grants access should be treated as a secret. Prefer short-lived test tokens when possible.