Skip to content

JWT Decoder

🎫Developer
Free · No sign-up · Your files never leave your browser

Free, no sign-up — paste a token and read its header, payload and expiry in seconds, right in your browser.

A JSON Web Token looks like one unreadable string, but it is really three parts joined by dots. This JWT Decoder opens the first two parts in your browser and shows them as plain JSON: the header, the payload, and — if the payload carries an expiry claim — the moment that token stops being current. It is useful for debugging logins and checking API responses.

JWT Decoder

Decode a JSON Web Token — header, payload and expiry. 100% local, nothing is sent anywhere.

Decoding is not verification. This tool reads a token; it does not check the signature, so a decoded token proves nothing about who issued it or whether it was changed. Never paste a production token or any secret into any website. This tool runs locally in your browser, as described on this page, and still treats every real token as sensitive.

The signature section of the token is not shown and is not checked. Only trust a token after your own server or application has verified its signature with the correct key.

A JSON Web Token looks like one unreadable string, but it is really three parts joined by dots. This JWT Decoder opens the first two parts in your browser and shows them as plain JSON: the header, the payload, and — if the payload carries an expiry claim — the moment that token stops being current. It is useful for debugging logins and checking API responses.

Decoding is not verification. This tool does not check the signature. It never has the issuer’s key and does not display the third part. A decoded token therefore proves nothing about authenticity: anyone can build a token that decodes beautifully and says anything at all. Only a server or application that verifies the signature with the correct key can decide whether a token should be trusted.

🔒Private by design
Your files never leave your device
⚡Instant
No uploads, no queues, no waiting
🎁Free, no sign-up
No account, no card, nothing to install

What the three parts of a token mean

The header is small JSON naming the algorithm and type — for example, `alg` HS256 and `typ` JWT. The payload is also JSON, carrying claims such as `sub`, `name`, `iat` (issued at) and `exp` (expiry). The third part is the signature, created from the header, payload and a key. Base64url encoding is not encryption: anyone holding the token can decode the first two parts, as this tool does.

How to use the JWT Decoder

  1. Paste the token, complete with both dots. The tool trims stray spaces at the start and end.
  2. Click Decode. The header appears first, then the payload, each as readable JSON.
  3. Read the expiry line. If the payload has an `exp` claim, it becomes a date and time on your device, marked EXPIRED in red or valid in green.
  4. Copy the payload if needed. Copy Payload copies only the payload JSON.
  5. Clear up afterwards. Remove real tokens from the box and your clipboard when you finish.

A worked example you can try

Paste this well-known public sample token:

`eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c`

The header decodes to `{“alg”:”HS256″,”typ”:”JWT”}` and the payload to `{“sub”:”1234567890″,”name”:”John Doe”,”iat”:1516239022}`. That payload has no `exp` claim, so the tool reports “No exp claim” — and still warns that the signature is NOT verified. This sample is a teaching example, not a credential for any real service.

How the expiry line works — and what it does not mean

JWT dates are Unix timestamps in seconds. The tool multiplies `exp` by 1,000, builds that date, and compares it with the time on your device: past is EXPIRED, future is valid. Here, valid means only that the printed date has not passed. It does not mean the token is genuine or acceptable to any API — a forged token can carry any future date. No `exp` claim is not proof of safety or permanence either.

Safety: never paste production tokens into any website

A live token is a credential: whoever holds it may act with its permissions until it expires. Never paste production tokens, session or refresh tokens, API secrets, or signing keys into any website — including this one. This tool runs locally: decoding happens in your browser with built-in functions, no library is loaded, and nothing is sent anywhere, exactly as coded. A real token can still end up in screenshots or clipboard history, though. Prefer expired, test, or sample tokens, and revoke any real token you suspect has been exposed.

When decoding fails

An empty box gets “Paste a JWT first.” Text without exactly three dot-separated parts is reported as not a JWT. Parts that cannot be decoded or parsed as JSON get “Could not decode”. Usual causes: a truncated copy, line breaks around the token, or a string that was never a JWT — an opaque session ID has no readable header or payload.

Frequently asked questions

Does this JWT decoder verify the signature of a token?

No. Decoding is not verification. The signature is not checked, decoded, or even displayed, and a decoded payload proves nothing about who issued the token or whether it was changed. Trust a token only after your own server or application verifies its signature with the correct key.

Is the token I paste sent to a server?

No. The tool runs locally in your browser, decodes the header and payload with built-in functions, loads no library, and sends nothing anywhere. Even so, never paste production tokens or secrets into any website, including this one — use expired, test, or sample tokens instead.

Why does the expiry line say valid if the signature is not verified?

On that line, valid means only that the date in the exp claim has not passed yet on your device — a date comparison, not a judgement about the token. The line always carries the warning “signature NOT verified (decode only)”, and an expired token is marked EXPIRED in red.

What does it mean when a token has no exp claim?

The payload contains no expiry timestamp to convert, so the tool reports “No exp claim” instead of a date. That does not mean the token lasts forever or is safe: the issuing or receiving system may enforce its own lifetime and rules, not written inside the token.

Why does the tool say my token is not a JWT or could not be decoded?

A JWT has exactly three parts separated by dots, and the first two must be base64url-encoded JSON. A wrong part count gets “Not a JWT — expected 3 parts separated by dots.”; parts that fail to decode or parse get “Could not decode”. Check for a truncated paste, line breaks, or a non-JWT string such as an opaque session ID.

Can I use the decoded payload as proof of who a user is?

No. Anyone can create a token whose payload names any user, role, and future expiry, and it will decode perfectly. The payload is a claim, not proof. Proof comes only from signature verification and claim checks by a system holding the correct verification key.

Related tools

Built by Umar Hayat — VeloSpark Digital

More Converter & Utility Tools

Top Tools

Tool Categories

More from VeloSpark

© 2026 VeloSpark Digital · Privacy Policy · Terms of Service · Disclaimer · About · Contact · Editorial Policy · Privacy settings

🍪 We value your privacy. We use cookies and browser storage to run this site, remember your favorites and understand which tools help people most. If ads are enabled on this site later, cookies may also be used to show them. The tools themselves work either way — your files never leave your device. You can change your choice at any time from the Privacy settings link in the footer. Read our Privacy Policy.