JWT Decoder
A JSON Web Token is three Base64url strings joined by dots: a header naming the algorithm, a payload of claims, and a signature over the first two parts. Decoding needs no key; the decoder here splits the token, Base64url-decodes each part and pretty-prints the JSON.
It then interprets the registered claims for you: iss, sub, aud, and the timestamps iat, nbf and exp, converted to local time with a “expires in 40 minutes” style summary. An expired token or an alg: none header is flagged.
Enter the shared secret and the page will recompute an HMAC signature with the Web Crypto API and compare it to the token’s third part. Tokens signed with RSA or ECDSA (RS256, ES256) need the public key and are decoded but not verified here.
What leaves your browser
Tokens and secrets stay in your browser. Nothing is sent to any server. A JWT often grants access to an account, so treat it like a password: paste tokens from test environments, and revoke any production token you have pasted into third-party tools.
Is a JWT encrypted?
No, it is signed. Anyone can read the payload; the signature only proves it was issued by someone with the key and has not been altered. Encrypted tokens (JWE) are a separate, rarer standard.
Why does signature verification fail?
Wrong secret, a secret that is itself Base64-encoded on the server side, or an RS/ES algorithm that needs a public key rather than a shared secret.
Should I store sensitive data in a JWT?
No. The payload is readable by the client and by anyone who intercepts the token. Store an identifier and look the rest up server-side.
What does alg: none mean?
An unsigned token. Libraries that accept it let anyone forge tokens. Servers must reject it.