JWT Decoder

Decode a JWT's header and payload with expiry checks — decode only: the signature is displayed but never verified, as that needs a secret key.

Developer Tools Runs in your browser · no upload

Reviewed 17 November 2026 · Free · No account needed

ExecutionYour browserInput never leaves your tab
File retentionNoneNothing is stored
AccountNot requiredNo sign-up, no paywall
PriceFreeNo trial, no usage cap on the tool itself

How to use

  1. Paste the full JWT (three dot-separated parts).
  2. Read the algorithm, expiry status and ISO timestamps.
  3. Inspect the decoded header and payload objects.

Example

Input: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjMifQ.sig

Output: alg HS-256 · payload {sub: 123} shown pretty-printed

How it works

A JWT is three Base64URL parts joined by dots: header, payload and signature. This tool decodes the header and payload only — decoding is not signature verification, and the token is never sent to a server.

The token is split on dots and the header and payload are base64url-decoded (- and _ restored to + and /, padding re-added) and parsed as JSON objects. The alg claim, iat and exp as ISO timestamps, and an expired flag (exp compared with your device clock) are summarised. The signature part is displayed as-is — it is NOT verified, because verification needs the secret or public key.

Worked example

A token with header {"alg":"HS256","typ":"JWT"} and payload {"sub":"123"} shows alg HS-256, the payload pretty-printed, and iat/exp as readable dates where present.

Edge cases to know

  • Decode only: an unsigned or forged token reads exactly like a valid one — never act on the payload without verifying the signature on a server.
  • A token must have three non-empty dot-separated parts; sections that are not JSON objects are rejected with clear errors.
  • The expired flag is judged against your device clock — a wrong system clock flips it.
  • Decoding happens entirely in the page; the token is never sent to a server.

Limits & compatibility

  • Decode only — signature verification requires the secret/public key and belongs on a server.
  • Tokens are not trusted: expired/no-exp tokens are labelled, not treated as valid.
  • Malformed tokens (wrong part count, non-JSON sections) are rejected with clear errors.

Privacy

Decoding runs locally in your browser. Tokens — including session tokens — are never sent to a server or stored.

Related tools

FAQ

Questions about JWT Decoder

Does it verify the token's signature?

No — this is a decode-only tool by design. Signature verification needs the secret or public key, and checking keys belongs on a server, not in a browser page. The signature section is displayed as an opaque string, and a decoded token is never treated as a trusted one: expired tokens and tokens without an expiry are labelled as such.

What does it show from the header and payload?

Both sections are pretty-printed JSON. The alg from the header is reported, and numeric iat and exp claims in the payload are converted to ISO timestamps, with the expiry status computed against your device's clock. Anything the tool cannot interpret it simply shows as part of the decoded object rather than hiding it.

Why is my token rejected?

The most common reasons: the token does not have exactly three dot-separated sections, one of the sections is empty, or the header and payload do not decode to JSON objects — arrays and other shapes are refused. Each failure produces a specific error message, and decoding runs entirely in your browser, so even live session tokens stay on your device.