Skip to main content
GARGLOO

JWT Decoder Online – Free, No Upload

Read any token's header, payload and expiry.

Runs on your device

At a glance

Input:
Text / data you paste
Processing:
Runs locally in your browser
Privacy:
Nothing you type is sent to a server

Last updated: 2026-11-04

Common use cases

  • Checking why an API rejects a token — expired, wrong audience, missing claim
  • Reading a token's roles and permissions during development
  • Comparing tokens across environments without an online decoder
  • Teaching how JWT structure works: header, payload, signature

About this tool

Paste any JWT and read it instantly: header and payload as formatted JSON, expiry status against your clock, and the signature segment — decoded locally, never uploaded, never verified server-side.

How to use it

  1. Paste the full token (three parts, separated by dots).
  2. Header and payload decode immediately — no button needed.
  3. Check the expiry badge and claims, copy either JSON block as needed.
  4. Try the sample token to see the layout before pasting a real one.

Practical tips

  • Copy tokens without surrounding quotes — a leading or trailing quote breaks decoding.
  • Check exp first when debugging auth failures: expiry is the most common rejection reason.
  • Use the sample token to learn the layout, then paste your own — never the reverse order with production tokens.
  • Compare iat and exp to spot clock-skew problems between issuer and API.

Common mistakes

  • Treating a readable payload as proof the token is valid — decoding is not verification.
  • Pasting production tokens into random online decoders — decoding there means uploading a credential.
  • Ignoring the device clock when expiry looks wrong — the badge trusts your clock.
  • Assuming every token has an exp claim — some do not expire, and the badge simply stays absent.

How this compares

Online decoders upload your token to their server; terminal decoding needs flags memorized. This tool decodes in the tab with expiry badges and copy buttons, and nothing is transmitted. The tradeoff: no signature verification — that needs the key, which a local page rightly never asks for.

Good to know

  • Decoding only — signatures are displayed, never verified.
  • Header and payload must be JSON objects; other payloads fail with a plain error.
  • Expiry uses your device clock, so a wrong clock mislabels validity.
  • Tokens are credentials: this page is local-only, but prefer test tokens for inspection.

Frequently asked questions

Is my token uploaded to a server?

No. Decoding happens entirely in your browser — the token never leaves your device.

Does this verify the signature?

No — verification needs the secret key (or public key) and the algorithm, which this page never asks for. It decodes and displays; it does not vouch for the token. Always validate signatures server-side before trusting a token.

What does the expiry badge mean?

It reads the exp claim against your device clock: green while the token is still valid, red once exp has passed. A wrong device clock makes the badge wrong — check the raw timestamp too.

Why does decoding fail on my token?

A JWT has three dot-separated parts and the first two must be base64url JSON objects. Truncated pastes, wrapped lines and extra quotes are the usual causes — re-copy the full token, quotes excluded.

Is it safe to paste a production token here?

Decoding here is local-only, so the token stays on your device. As a habit, prefer test tokens for inspection, and never paste production tokens into online decoders you do not trust.

All developer tools
JWT Decoder Online – Free, No Upload | GARGLOO