JWT Decoder
Decode a JWT's header and payload with expiry checks — decode only: the signature is displayed but never verified, as that needs a secret key.
Decode only: the signature is shown but never verified — cryptographic verification requires the secret or public key and must happen on a server you control.
How to use
- Paste the full JWT (three dot-separated parts).
- Read the algorithm, expiry status and ISO timestamps.
- Inspect the decoded header and payload objects.
Example
Input: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjMifQ.sig
Output: alg HS-256 · payload {sub: 123} shown pretty-printed
How it works
A JWT is three Base64URL parts joined by dots: header, payload and signature. This tool decodes the header and payload only — decoding is not signature verification, and the token is never sent to a server.
Limits & compatibility
- Decode only — signature verification requires the secret/public key and belongs on a server.
- Tokens are not trusted: expired/no-exp tokens are labelled, not treated as valid.
- Malformed tokens (wrong part count, non-JSON sections) are rejected with clear errors.
Privacy
Decoding runs locally in your browser. Tokens — including session tokens — are never sent to a server or stored.
Related tools
Questions about JWT Decoder
Is my input private?
Yes. This tool runs entirely in your browser — your input never leaves your device, is never uploaded to a server and is never stored.
How accurate is the result, and what are the limits?
The tool page states its formula and limits openly. Check them before relying on a result, and verify anything consequential — financial, legal, medical or safety-critical — against an authoritative source.
What happens to files I open with this tool?
Files are processed locally in your browser and never uploaded; closing the tab discards them. Text tools never store what you paste — it lives only in the page while you use it.