← All tools/Minifiers/Code/JWT Decoder

JWT Decoder

Read a JSON Web Token’s header, payload and expiry — decoded in your browser, so the token never leaves your device.

Paste a token from an Authorization header or a login response. It is decoded in your browser and never sent anywhere.

Expiry status

No expiry claim

HS256 · issued 18 Jan 2018, 01:30 UTC

Header 36 charsPayload 74 charsSignature 43 chars

Header

{
  "alg": "HS256",
  "typ": "JWT"
}

Payload

{
  "sub": "1234567890",
  "name": "John Doe",
  "iat": 1516239022
}
Issued (iat)18 Jan 2018, 01:30 UTC
Expires (exp)No expiry claim

Signature (Base64URL — not decoded)

SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

How it works

token = header.payload.signature  (three Base64URL parts, joined by dots)
header  = JSON.parse(base64urlDecode(part 1))   → {"alg":"HS256","typ":"JWT"}
payload = JSON.parse(base64urlDecode(part 2))   → claims like sub, name, iat, exp
iat / exp are Unix timestamps (seconds since 1 Jan 1970).
The signature (part 3) is NOT decoded here — checking it needs the secret key.

Worked example — the jwt.io sample token decodes to header {"alg":"HS256","typ":"JWT"} and payload {"sub":"1234567890","name":"John Doe","iat":1516239022}. The iat timestamp is 1516239022 seconds, which is 18 Jan 2018, 01:30 UTC. This token has no exp claim, so it carries no expiry date.

Decoding is not verifying: anyone can read a JWT’s payload, and only the signature — checked with the secret key — proves the token is genuine. Long tokens wrap instead of pushing the page sideways.

Frequently asked questions

Is it safe to paste my token here?

Yes, on this page — decoding happens entirely in your browser and the token is never sent to a server. As a habit, though, do not paste production tokens into random websites: a JWT’s payload is only Base64-encoded, so anyone who has the token can read it.

Why can’t I see what is inside the signature?

The signature is not JSON — it is a cryptographic hash of the header and payload, made with the server’s secret key. Its only job is to prove nobody changed the token; it contains no readable claims of its own.

What does “No expiry claim” mean?

The token has no exp claim, so it never expires on its own. Many real tokens do carry one — usually 15 minutes to a few hours after issue — and this page shows “Expired” or “Valid” with the exact expiry time when it is present.

What is the difference between decoding and verifying a JWT?

Decoding just reads the header and payload, which anyone can do. Verifying checks the signature against the secret key or public key, which is what proves the token is genuine and unmodified. This page decodes; it does not verify, because verification needs the key.

My token will not decode — why?

Most often the copy is incomplete: a token copied from a log or a header can lose its last characters, or pick up a line break or a space. A JWT always has exactly three parts separated by dots. Opaque tokens (random strings with no dots) are not JWTs and cannot be decoded this way.

More tools

Tell us what you think

Loving this tool, or stuck on something? Tell us — it takes a minute.

We’ll only use your name and email to reply if needed. The tool and page are filled in for you.