JWT Decoder
About this tool
A three-part token in an Authorization header is opaque until you split it. This JWT decoder pretty-prints header and payload JSON and shows the signature as-is. Decoding is not verification. Use JWT verify for HMAC/RSA checks and expiry.
Features
- Splits header, payload, and signature
- Pretty-prints claims as JSON
- Reassembles edited JSON into a token without signing
How to use
- Paste a full JWT, usually three segments joined by dots.
- Read alg and typ in the header, then claims such as sub and exp.
- Edit JSON locally if you are mocking a client, then reassemble.
- Move to JWT verify when you need HS256/RS256 signature checks.
When to use it
- Login fails and you want to see whether the token carries a user id
- You need exp and iss before deciding to verify
- Docs mention a three-part JWT and you want the header alg
Examples
- A typical header is {"alg":"HS256","typ":"JWT"}.
- exp is Unix seconds; treating it as milliseconds misreads expiry.
FAQ
What are the three JWT parts?
Header, payload, signature, joined by dots. The first two are Base64URL JSON. This page does not check the signature.
Can I forge a login?
Decoding is not authentication. Without the secret you cannot produce a valid signature.
How is this different from JWT verify?
This page is for reading claims. Signature, expiry, and iss/aud live on JWT verify.
Refresh tokens?
Any JWT-shaped string can be expanded, whatever the product calls it.
What about alg none?
You can still read the payload. Rejecting none belongs on the verify page.
Is the token uploaded?
No. Decoding stays in the browser.
Back to Encoding Tools Hub
Guides