When to use it
Inspect a JWT that an API returned: who is signed in, when it expires, what scopes are attached. Handy for making sense of a token pasted in a bug report or server log.
How it works
Paste the token in the input. The three segments (header · payload ·
signature) are unpacked below. Time claims like exp, iat, and
nbf are rendered as readable dates; an expired exp gets an
"Expired" label.
Signatures are not verified
Verifying a JWT needs either the shared secret (HS256) or the issuer's
public key (RS256/ES256). Handling a secret in the browser is a bad
default, so this tool only shows the raw base64url signature. To
actually trust a token, verify with a server-side library
(jsonwebtoken, jose, …).
Where does your token go?
Header, payload, and signature are parsed in your browser. Your token is never uploaded or saved. Close the tab and it's gone.