This JWT decoder reads a JSON Web Token and shows its header and payload as formatted JSON, the signing algorithm, and when the token was issued and expires. Decoding runs in your browser, so the token is not sent anywhere. It does not verify the signature, so use it to inspect a token, not to decide whether to trust one.

How to use the JWT decoder

  1. Paste the token into Paste a JWT. A leading Bearer is removed for you.
  2. Read the status line: it says whether the token has expired, is not valid yet, or how long it stays valid.
  3. Check Algorithm, Issued at (iat), Not before (nbf) and Expires (exp), shown in your local time.
  4. Use Copy next to Header or Payload to grab the formatted JSON.

How it works

A JWT is three Base64URL strings joined by dots: header.payload.signature. The tool splits the token, converts each of the first two parts from Base64URL (which uses - and _ and drops the = padding) back to bytes, decodes them as UTF-8 and parses the result as JSON. The time claims are Unix timestamps in seconds, which are compared with your device clock.

The signature is the third part. Checking it needs the secret key (for HS256) or the issuer’s public key (for RS256 or ES256), and that check must happen on your server. This page never sees a key, so it cannot tell a real token from a forged one. If any part is not valid Base64URL, not UTF-8 or not a JSON object, the status line names the part and the problem.

Example

The prefilled token has this header and payload:

{
  "alg": "HS256",
  "typ": "JWT"
}
{
  "sub": "1234567890",
  "name": "Ana Silva",
  "role": "editor",
  "iat": 1767225600,
  "exp": 1767229200
}

Here iat 1767225600 is 1 January 2026 at 00:00 UTC and exp 1767229200 is one hour later, so the tool reports the token as expired. Its signature is a placeholder, which is fine for decoding because the signature is never checked. Paste your own token over it to inspect a real one.

Common claims

Claim Meaning
iss Issuer: who created the token
sub Subject: usually the user ID
aud Audience: which service should accept it
exp Expiry time, in Unix seconds
nbf Not valid before this time
iat Issued-at time
jti Unique token ID, used to block replays

Common mistakes: trusting payload data without verifying the signature, storing secrets in the payload (anyone can read it, it is only encoded, not encrypted), and accepting "alg": "none". To turn a raw timestamp into a date, use the timestamp converter; to decode other Base64 text, try the Base64 encoder.

Frequently asked questions

Does this verify the JWT signature?

No. It only decodes the header and payload. Always verify the signature on your server with the right key before trusting any claim.

Is it safe to paste a token here?

This page decodes locally and sends nothing. Still, a live token can act as a password, so avoid pasting production tokens into websites you do not trust, and prefer expired or test tokens.

What if my token has five parts?

A five-part token is an encrypted JWE, not a signed JWT. The tool tells you so, because its payload is encrypted and cannot be read without the key.

Why is the expiry time off by some hours?

Dates are shown in your local time zone. The underlying value is in UTC seconds, so the moment is the same.

Can anyone read my JWT payload?

Yes. Base64URL is an encoding, not encryption. Do not put passwords or private data in a JWT payload.