JWT Decoder

Decode JSON Web Tokens, read every claim in plain language, spot security issues and verify the signature — without your token ever leaving the browser.

Runs locally — nothing is sent to a server

Encoded token

Header


            

Payload


            

Anatomy of a JSON Web Token

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwiZXhwIjoxNzk5OTk5OTk5fQ.Rk9vbmV3c2lnbmF0dXJl…

Header

Says how the token is signed: the algorithm (alg), the token type (typ) and often the key ID (kid).

Payload

The claims: who the user is, who issued the token, who it is for, and when it expires. Readable by anyone.

Signature

A cryptographic signature of header and payload. Changing a single character makes verification fail.

JWT Security Checklist

  • ✓ Always verify the signature on the server — decoding is not validation
  • ✓ Pin the expected algorithm; reject "none" and unexpected algorithms
  • ✓ Check exp, nbf, iss and aud on every request
  • ✓ Keep access tokens short-lived and rotate refresh tokens
  • ✓ Use long, random HMAC secrets (at least 256 bits) or asymmetric keys
  • ✓ Never put passwords, card numbers or personal documents in the payload
  • ✓ Only fetch keys (jku, x5u) from allow-listed URLs
  • ✓ Store tokens in httpOnly, Secure cookies when possible

Frequently Asked Questions