JWT Decoder

Paste a JWT to see its header, claims and expiry clearly. Decoding is local; the signature is not verified.

waiting for a token
—
—

How to use the jwt decoder

  1. Paste the token (with or without the Bearer prefix).
  2. Read the decoded header and payload, with registered claims highlighted.
  3. Check the expiry countdown — red means the token has already expired.
  4. Copy individual claim values if you need them elsewhere.

A JWT is three Base64url segments joined by dots: header, payload and signature. Only the signature provides any guarantee — that the token was issued by someone holding the key, and that nobody edited the payload afterwards. The decoded content itself is plain JSON: readable by anyone who holds the token, so a token must be treated like a password.

This page decodes the first two segments and gives you a readable view of the registered claims. It does not verify the signature, because that requires the issuer's secret or public key and should happen on your server, never in a browser tab. A green "decodes correctly" result therefore means "well-formed", not "trustworthy".

Claims worth checking

If you need to base64-decode individual claims or payloads by hand, the Base64 tool handles the URL-safe variant.

Frequently asked questions

Is my token uploaded?

No. Decoding is local JavaScript. Still, treat any token you paste — including into a browser tab — as a secret.

Do you verify the signature?

No. Verification needs the issuer's key and belongs on the server. This tool only decodes.

Why does a valid JWT fail to decode here?

Most often the token was truncated when copied, contains newlines, or is an opaque reference token rather than a JWT.

Can I edit the payload?

You can edit the text, but the signature will no longer match and any server that verifies it will reject the token.

Related tools