JWT decoder

Decode a JWT's header and payload and check its expiry — everything stays in your browser.

Header
{"alg":"HS256","typ":"JWT"}
Issued at (iat)
1/18/2018, 2:30:22 AM
Not before (nbf)
—
Expires (exp)
—
Signature
present — not verified

Last updated: October 2026 · Report a calculation error

Anatomy of a JWT

  1. Header — the signing algorithm (alg) and token type (typ).
  2. Payload — the claims: who issued the token, for whom, and until when it's valid.
  3. Signature — made with the server's key; only it proves the token hasn't been changed.

The parts are base64url-encoded and separated by dots. Base64 is encoding, not encryption — anyone can read a token's payload.

Registered claims

ClaimMeaning
ississuer
subsubject (e.g. user ID)
audaudience — the service it's for
expexpiry time (Unix time)
nbfnot valid before
iatissued at

Convert Unix times with the timestamp converter.

Frequently asked questions

Is it safe to paste a token here?

The token is decoded only in your browser and never sent anywhere. Still, treat live tokens like passwords and don't paste them into sites you don't trust.

Why isn't the signature verified?

Verification needs the server's secret or public key. Being able to read a token doesn't mean it's genuine.

See alsoWhole category

  1. IT-01Base64 encoder and decoderEncode text to Base64 or decode a Base64 string back to text.
  2. IT-02JSON formatter and validatorBeautify or minify JSON, check that it is valid and see exactly where a syntax error is.
  3. IT-03HEX / RGB / HSL color converterConvert colors between HEX, RGB and HSL with a live preview.
  4. IT-04SHA-256 hash generatorGenerate SHA-256, SHA-1 and SHA-512 hashes of any text.