Data & Requests · LOCAL TOOL

JWT Inspector

Read a compact JWT header and payload as JSON and translate common time claims into dates. The signature segment is deliberately not verified.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

Separating decoding from verification prevents a common debugging mistake: readable claims do not prove that a token is authentic or safe to trust.

How to use it

Paste the three-part token.
Inspect the decoded header and payload.
Check exp, nbf, and iat against the local clock.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "token": "eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiJkZW1vLXVzZXIiLCJleHAiOjQxMDI0NDQ4MDB9."
}

Expected sample result from the local tool

Decoded only · signature and authorization were not verified.

{
  "header": {
    "alg": "none",
    "typ": "JWT"
  },
  "payload": {
    "sub": "demo-user",
    "exp": 4102444800
  },
  "timeClaims": {
    "exp": {
      "seconds": 4102444800,
      "iso": "2100-01-01T00:00:00.000Z",
      "relationToLocalClock": "not expired"
    }
  },
  "verification": "NOT PERFORMED"
}

Readable claims do not prove authenticity. Verify the signature and application-specific issuer, audience, and policy checks.

LIMITS AND INTERPRETATION

What the result cannot tell you.

This tool only decodes the token. It does not verify a signature, check issuer or audience configuration, contact an identity provider, or establish authorization.

Inputs are processed in this page and are not written to local storage.