JWT Decoder

Inspect the header, payload, and registered time claims of a JSON Web Token. This page does not verify the signature and does not save the token.

The signature is not checked. A decoded payload is not verified. This page does not save the token or send it anywhere.

Signature checked: no. Nothing from this token is written to local storage.

How to use it

  1. Paste a token with three segments. Leave the page to drop it from memory.
  2. Read the header and payload. iat and exp are shown as ISO-8601 UTC.
  3. If exp is in the past, the page says the token is expired. That still does not mean the signature was checked.

Common mistakes

  • A decoded payload is not a verified token.
  • alg in the header is displayed only. It is not used to check a signature.
  • Do not paste a live production token into a shared computer.

Examples

Three segments

header.payload.signature

Each of the first two segments is Base64URL JSON.

Expiration

exp is a NumericDate in seconds. The page compares it with the current time and does not call the token verified.

Frequently asked questions

Processing stays in this browser tab. What you paste is not uploaded, and this tool does not write it to local storage. The token is not saved. The signature is not checked, so a decoded payload is not verified.