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
Security check
Verify signature
Header
Payload
Claims explained
Generated token
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
A JSON Web Token (RFC 7519) is a compact, URL-safe token made of three Base64URL parts separated by dots: a header (algorithm and token type), a payload (claims such as user ID, roles and expiration) and a signature that proves the token was issued by someone holding the key.
Yes. Decoding and signature verification run entirely in your browser with the Web Crypto API — the token, secret and keys are never sent to our servers. As a general rule, prefer expired or test tokens on any online tool, and never share private keys.
No. A standard signed JWT (JWS) is only Base64URL-encoded, so anyone holding the token can read the payload. The signature prevents tampering, not reading. Never put passwords or other secrets in claims. Encrypted tokens (JWE) have five parts instead of three.
The most common causes are a wrong secret, a secret that is Base64-encoded but was entered as plain text (or the opposite), the wrong public key for the kid in the header, or a token that was modified after signing. For RS/ES/PS tokens use the public key, a certificate or the JWKS from the issuer.
They are Unix timestamps in seconds. exp is when the token expires, iat is when it was issued and nbf is the moment before which it must not be accepted. The decoder converts them to your local time and shows how long ago or from now each one is.
HS256 uses one shared secret to both sign and verify, so every service that verifies tokens can also create them. RS256 (and ES256, PS256, EdDSA) uses a private key to sign and a public key to verify, which is safer when several services need to validate tokens.
Yes. The Encoder tab signs a header and payload with HS256, HS384 or HS512 and a secret you provide, which is handy for local development and tests.
Was this tool helpful?
Thanks for your feedback!
Could not send your feedback. Please try again.