Developer Utilities

JWT Decoder

Decode JWT header and payload JSON locally, inspect common claims and compare timestamps without verifying token signatures.

Browser processing · No account required

Decode a JWT

Local decoding only. Tokens are held in memory and are never saved, logged or sent to a server.

Decoding does not verify the signature or establish trust in the claims. Use synthetic tokens while learning.

Decoded claims

Add your input, then run the tool to see results.
WORK WITH CONFIDENCE

Understand your results

For developers inspecting a token’s encoded claims with privacy.

The decoder reads three compact JWT segments locally. It decodes header and payload as Base64URL UTF-8 JSON objects, screens the segment syntax, and displays common claims and NumericDate values. Every claim remains unverified.

How to use this tool

  1. Paste a synthetic or authorized JWT in the token field.
  2. Decode its header and payload and inspect the unverified status.
  3. Review timestamps against the displayed device-clock observation and copy decoded JSON if appropriate.

What the observations mean

Expiration and not-before messages compare supplied NumericDate seconds with the device clock when Decode is clicked. A future expiration does not establish validity or authorization.

Worked example

Inspect an unsigned synthetic token.

Header {"alg":"none","typ":"JWT"} · Payload {"sub":"demo","exp":1700003600}

The synthetic example is shown as unverified and expired when compared with a later device time. alg=none is explicitly identified as unsigned.

Limits and processing

Three compact segments and up to 32,768 characters. No JWE decryption, signature, issuer or audience verification. Duplicate JSON keys follow JSON.parse behavior; unsafe numeric ranges are rejected.

Common problems and practical fixes

The token has the wrong number of parts
Use a compact three-part JWT. Avoid copying a Bearer prefix or surrounding metadata.
JSON decoding fails
Check Base64URL syntax and UTF-8 encoding. Header and payload must be objects with supported numeric values.
Expiration differs from the server
Check your device clock and the verifier’s leeway or policy. Decode again to refresh this observation.

Best practices

Treat all displayed claims as untrusted and keep live bearer credentials out of screenshots and shared output.

Practical tips

  • Use the synthetic example for learning instead of a live credential.
  • Validate signatures, issuer and audience with your application’s trusted verification system.
A LITTLE MORE CLARITY

Frequently asked questions

Practical answers for using the JWT Decoder.

Does a decoded token prove identity?

No. Decoding does not verify a signature or establish that any claim is true.

Can it decode encrypted tokens?

Five-part JWE tokens are outside this three-part JWT decoder.

Where is my token stored?

The tool holds it in this page’s memory. It does not save it in storage or URLs, log it, or send it to an API.