JWT Decoder
v1.0JWT Decoder splits a JSON Web Token into its header, payload and signature and shows the first two pretty-printed. The header, payload and signature are color-coded in the pasted token and on the three panels below, so you can see which part produced which output.
Paste is forgiving: an Authorization: header name, a Bearer prefix, surrounding quotes and wrapped line breaks are stripped before decoding, and the tool tells you when it did that. If the token is malformed, each problem gets its own message (wrong number of parts, a header that isn't valid base64url, a payload that isn't valid JSON), and any segments that did decode are still shown.
exp, iat and nbf appear as UTC dates with a relative time such as "in 3 hours", and exp and nbf carry an Expired, Not yet valid or Active badge. iss, sub, aud and jti show their full names. A lifetime bar drains from iat to exp, and once expiry is close it becomes a live countdown.
A security review lists what a verifier should check, each with why it matters:
- Errors:
"alg": "none", an expired token, and header keysjku,jwk,x5uorx5c. - Warnings: no
exp, a lifetime over a day, anexpbeforeiat, a futurenbf, or claims likepasswordorapi_keyin the payload. - Notes: no
issoraud, nokid, and that HS256 tokens can be minted by anyone who can verify them.
These describe the token as written, not whether its signature is genuine.
Signature verification supports HS256/384/512 with a shared secret, and RS, PS and ES (256/384/512) with a public key. The panel asks for whichever one the token's alg needs. A public key can be a PEM, a JWK, or a whole JWKS, where the header's kid picks the entry. Certificates and private keys are refused with an explanation.
Everything runs in your browser. The token, secret and key never leave the page, and there is deliberately no Share button because a JWT is often a live credential.