JWT Decoder Online: Read and Debug JSON Web Tokens Without Code

WhatsApp
Telegram
Facebook
Twitter
LinkedIn
jwt decoder tool decoding a JSON web token header and payload

If you work with APIs, you work with JWTs. JSON Web Tokens are how modern apps pass identity around: login endpoints return them, APIs validate them, and when authentication breaks, the first question is always “what is actually inside this token?” A jwt decoder answers that in seconds — paste the token, read the claims, find the problem.

Quick Jump Navigation (Table of Contents)

What a JWT actually is

A JWT is three base64-encoded parts separated by dots: header.payload.signature.

  • Header — says how the token is signed (usually {“alg”:”HS256″,”typ”:”JWT”}).
  • Payload — the claims: who this is (sub), who issued it (iss), when it expires (exp), when it was issued (iat), and any custom data your app added.
  • Signature — proves the token was not tampered with. Verifying it requires the secret or public key; decoding does not.

Decoding is not decrypting. A JWT is signed, not encrypted — anyone who has the token can read the payload. That is by design, but it is also why you should never put secrets in a token.

Why you need a decoder instead of doing it by hand

You can technically split the token on dots and base64-decode the middle part yourself. In practice you will not:

  • Debugging auth failures. A 401 response usually means the token expired, the issuer is wrong, or the claims do not match what the API expects. Reading the payload tells you which in one glance.
  • Checking expiry. The exp claim is a Unix timestamp — human-unreadable. A decoder converts it to a real date and tells you whether the token is expired right now.
  • Inspecting scopes and roles. If your app gates features on claims like roles or scope, the decoder shows exactly what the token carries — no guessing.
  • Comparing tokens. Paste two tokens (before and after a refresh, or from two environments) and diff the claims to spot what changed.

Decoding with Trencada (paste and read)

Trencada’s JWT decoder works entirely in your browser — the token is never sent to a server, which matters because tokens are credentials:

  1. Paste your JWT into the input.
  2. The header and payload decode instantly into readable, formatted JSON.
  3. Key claims are highlighted: expiry (with a human-readable date and an expired/valid indicator), issued-at, issuer, subject.
  4. Malformed tokens get a clear error instead of a cryptic failure.

No signup, no code, no terminal. Just paste and read.

The claims worth checking every time

When a token misbehaves, check these first:

exp (expiration). The most common cause of 401s. If the token is expired, no amount of debugging the payload will help — get a fresh one.

iss (issuer). APIs often reject tokens from the wrong issuer. After switching environments (dev → staging → prod), stale tokens from the old environment are a classic failure.

aud (audience). A token minted for one service may be rejected by another. If you are calling a new endpoint with an old token, check the audience.

iat / nbf (issued at / not before). Clock skew between your machine and the server can make a valid token look invalid. If nbf is in the future relative to the server, the token will be rejected.

Custom claims. Roles, permissions, tenant IDs — whatever your app added. When authorization logic breaks, the decoder shows whether the claim is missing, misspelled, or has an unexpected value.

A real debugging session

You log in, get a token, call the API, and get 401 Unauthorized. Before touching code:

  1. Paste the token into the decoder.
  2. Check exp — expired? Refresh it.
  3. Check iss and aud — do they match this environment and this API?
  4. Check your custom claims — does the token actually carry the role your endpoint requires?

Nine times out of ten, the answer is in the payload. The tenth time, it is the signature — and that is a server-side problem, not a decoding one.

Security notes (read this once)

  • Tokens are credentials. Anyone with your JWT can impersonate you until it expires. Do not paste production tokens into random websites — use a decoder that runs in your browser so the token never leaves your machine.
  • Never put secrets in the payload. The payload is readable by anyone. Put user IDs and roles there; put passwords and API keys nowhere near it.
  • Short expirations win. The shorter the exp, the smaller the window if a token leaks. Access tokens measured in minutes, refresh tokens measured in days.
  • Decoding does not verify the signature. A decoded payload tells you what the token claims. Only signature verification tells you whether to trust it — that happens on your server, with your secret.

Frequently asked questions

Can I decode a JWT online for free?

Yes — paste any JWT into the decoder above and read its header and payload instantly, free, with no signup.

Is it safe to paste my token into an online decoder?

Only if the decoding happens in your browser. Trencada’s decoder processes the token locally — it is never uploaded to a server.

Why does my JWT say “invalid token”?

Usually it is malformed: missing parts, extra whitespace, or characters that are not valid base64url. Copy the token again carefully — line breaks and quotes are the usual culprits.

Can a decoder verify the token’s signature?

Signature verification needs the signing secret or public key. Most online decoders (including this one) decode the payload without verifying the signature — which is fine for debugging claims and expiry.

What is the difference between JWT and OAuth?

OAuth is the authorization framework; JWT is a token format often used inside OAuth flows. They solve different problems and frequently appear together.

Let the Token Tell You What’s Wrong

When auth breaks, the token is telling you why — you just have to read it. A jwt decoder turns an opaque string into the claims, the expiry, and the mismatch that is causing your 401. Paste, read, fix, move on.

Decode your token free — paste and read, no signup.

Trustpilot

Run 450+ client-side PDF, image, developer & calculator utilities in your browser (Zero Cloud Upload):

Open Local Dev & JSON Tools →