Skip to main content
SiteIndex

Developer

JWT Decoder Documentation

Use the free JWT Decoder →

Decode readable JWT headers and payloads locally without verifying signatures.

What does it do?

Decode readable JWT headers and payloads locally without verifying signatures.

How does it work?

Splits a three-part readable token, decodes its unpadded Base64URL header and payload as JSON objects, and displays them locally. A finite numeric exp claim is compared to the device clock, including epoch zero. Expiry status is explicitly unverified; the signature is not checked.

When to use it
  • Inspect claim names in a synthetic development token.
  • Check whether an exp value uses numeric Unix seconds.
  • Identify an unsigned alg none token without trusting its contents.
Inputs and outputs
Input
Text, files, or values entered in the browser, depending on the tool.
Output
A result shown in the browser that can be reviewed or copied where supported.
Limitations
  • Does not verify signatures, issuer, audience, not-before claims, revocation, or authorization. Never use the displayed status as an authentication decision.
  • Only readable three-part JSON-object tokens are supported, not encrypted five-part JWE. Header and payload must use unpadded Base64URL.
  • Input is capped at 100,000 characters. Expiry comparisons depend on the device clock and JavaScript Date range.
Privacy and data handling

Inputs for this browser-side tool are processed locally and are not sent to SiteIndex. Normal page analytics may still be collected as described in the Privacy Policy. Read the Privacy Policy.

How to use it

  1. Paste a synthetic or redacted three-part JWT; avoid sharing production credentials.
  2. Select Decode token to inspect the JSON objects and any exp claim.
  3. Treat the result only as readable data, not evidence that a token is authentic or authorized.

Related tools