The decoder expects the standard header.payload.signature shape. It Base64URL-decodes the header and payload JSON, shows the algorithm when present, and converts exp into local time with an active or expired label.
The signature segment is displayed as text, but no secret, public key, issuer policy, or audience check is applied. A valid status means the token can be parsed, not that it should be trusted for login, authorization, or production debugging.
Common questions and answers about this topic.
A JWT (JSON Web Token) is a compact, URL-safe token format used for securely transmitting information between parties as a JSON object.
The header and payload are decoded and displayed as formatted JSON. The signature segment is separated as text, and the page also shows expiration status and algorithm information when those claims exist.
This tool decodes and displays the token contents. Signature verification requires the secret key and is not performed client-side for security reasons.
No, JWT decoding happens entirely in your browser. Your token is decoded locally with JavaScript — the token content is never sent to any server.