# JWT Decoder

> Decode a JWT online in your browser: header and payload as JSON, exp, nbf and iat as readable dates, a warning for alg: none. The token is not sent.

- URL: https://jsonstatham.dev/jwt/
- Language: English (en)
- Russian version: https://jsonstatham.dev/ru/jwt.md
- Updated: 2026-11-20

Paste a JWT to decode its header and payload into readable JSON and see when it expires. Decoding runs in your browser: the token is not sent anywhere. The signature is not verified — that takes the key.

## How to decode a JWT

1. Paste the token, with or without “Bearer ” in front.
2. Read the header and payload as JSON; exp, nbf and iat appear as dates in UTC and in your time.
3. Verify the signature on your server with the right key: decoding proves nothing about who issued the token.

## Decode a JWT locally: what a decoder can and can’t tell you

A JWT is three Base64url parts: header, payload and signature. Anyone can decode the first two — they are encoded, not encrypted. Only the key can check the third. That is why alg: none is a warning sign: a token without a signature is a token anyone could have written.

## JWT decoder FAQ

### Is it safe to paste a JWT here?

The token is decoded in your browser and is never sent to our server or stored; this page makes no requests to our API. Usage statistics tied to a random device ID record that a token was decoded, never the token. Still, treat a live token like a password and prefer expired or test tokens.

### Does it verify the signature?

No. Verifying needs the secret or the public key, and that belongs on your server. Every decoded token here is marked “Signature not verified”, because decoding alone proves nothing.

### Why does my token show as expired?

exp is a time in seconds since 1970, in UTC. If it is earlier than your clock, the token has expired; an nbf later than your clock means it is not valid yet. The check uses this browser’s clock.

### What if my token has five parts?

That is an encrypted JWT (JWE), not a signed one. Its payload can’t be read without the decryption key, so the decoder stops and says so.

## Other tools

- [JSON Formatter](https://jsonstatham.dev/) — 2 spaces, 4 spaces or tabs, order kept.
- [JSON Validator](https://jsonstatham.dev/validator/) — exact line and column for every error.
- [JSON Diff](https://jsonstatham.dev/diff/) — what changed, with JSON Pointer paths.
- [JSON Viewer](https://jsonstatham.dev/viewer/) — a tree with search and a path for every node.
- [Base64 Encode & Decode](https://jsonstatham.dev/base64/) — in your browser, nothing sent.
- [JSON to Query String](https://jsonstatham.dev/json-to-query/) — arrays, nesting and spaces your way, and back.
- [Unicode Unescape](https://jsonstatham.dev/unicode-unescape/) — \u0430 from DevTools into letters, in your browser.
- [JSON Minifier](https://jsonstatham.dev/minifier/) — one line, every byte accounted for.
- [JSON to YAML](https://jsonstatham.dev/json-to-yaml/) — same order, same numbers, safe quoting.
- [YAML to JSON](https://jsonstatham.dev/yaml-to-json/) — numbers as written, anchors expanded, no guessing.
- [JSON Position Finder](https://jsonstatham.dev/json-position/) — turn “position 1234” into a line and column.
