JWT Decoder

Read the JSON header and payload of a compact JWT without sending the token away.

Your input is processed in this browser and is not uploaded.

JWT Decoder

Inspect a compact three-part token’s JSON header and payload without sending it to a decoding service. Decoded claims remain untrusted input.

How to use it

  1. Paste the complete token, including both dots.
  2. Select Run tool.
  3. Read the claims, then verify security-sensitive information using the issuer’s trusted verification process.

Worked example

The unsigned demonstration token eyJhbGciOiJub25lIn0.eyJzdWIiOiIxMjMifQ. decodes to header { "alg": "none" } and payload { "sub": "123" }. The report explicitly contains "signatureVerified": false.

Limits and troubleshooting

No signature, expiry, audience, issuer or algorithm policy is verified. Five-part encrypted tokens are unsupported. Do not expose a real access token in a public screenshot. The tool decodes JSON but cannot establish that any claim is true. Numeric claims such as exp can be read with Unix Timestamp Converter in seconds mode; interpreting that time still does not verify the token. Input limit: 200,000 characters.

Frequently asked questions

Does exp prove the token is usable until that time?

No. A verifier must authenticate the token and apply all required claim and policy checks.

Why is the signature always unverified?

The decoder has no verification key, issuer trust configuration or application authorization policy.