JWT

JWT Decoder

Decode a JWT and inspect its header, payload, and expiry claims.

Input
Result

Please input

JWT Decoder

Paste a JSON Web Token to read its header and payload as indented JSON. The iat (issued at), nbf (not before) and exp (expires at) claims are shown as ISO 8601 dates in UTC, and the signature part is shown as it is. Decoding happens in your browser, and unlike most tools on this site, the token is not put in the page URL.

How to use

  1. Paste the token into the JWT box. It usually starts with eyJ and has three parts separated by dots.
  2. The header and payload are decoded from Base64URL and shown as indented JSON right away.
  3. Check the Issued at, Not before and Expires at labels, which appear when the payload has iat, nbf or exp as numbers.
  4. Copy the header or payload with the copy button above each block, for example to paste into a bug report.
  5. If the token cannot be decoded, the message “This does not look like a valid JWT.” appears instead of a result.

Frequently asked questions

Does this verify the signature?
No. Checking a signature needs the secret or the public key, so this tool only decodes and shows the contents, and a note on the page says so. Verify tokens on your server with a JWT library before trusting them.
Is my token sent to a server or saved?
No. Decoding runs entirely in your browser. The token is also not written into the page URL, so it does not end up in your browser history or in a link you share. Still, treat real tokens like passwords: anyone who has one can use it until it expires.
What is inside a JWT?
Three parts separated by dots: a header (the algorithm, such as HS256 or RS256, and the token type), a payload with the claims, and a signature. The header and payload are only Base64URL-encoded, not encrypted, so anyone who has the token can read them. Do not put secrets in a payload.
How are iat, nbf and exp shown?
These claims are Unix time in seconds. When they are numbers, they are converted to ISO 8601 in UTC, for example 2024-01-01T00:00:00.000Z. The tool does not judge whether the token has expired; compare Expires at with the current time, or use the Unix Timestamp Converter.
Why do I get “This does not look like a valid JWT”?
The token needs at least two parts separated by dots, and each part must be valid Base64URL. A token cut off when copying, or extra characters such as quotes around it, are common causes. If a part decodes but is not JSON, its raw text is shown instead.
Can it decode encrypted tokens (JWE)?
No. Encrypted tokens need the key to decrypt. This tool is meant for signed tokens (JWS), the usual kind of access token and ID token.
What is it useful for?
Debugging sign-in and API errors: checking which user (sub) and audience (aud) a token is for, which scopes or roles it carries, and whether it has expired or is not valid yet.