JWT Token Decoder
Decode and inspect JSON Web Token headers, payloads, signatures, and common claims.
Your token is decoded in the current session and is not sent to the Brilliance API. Decoding a token does not verify its signature or prove that the token is authentic.
JWT contents are normally readable
A typical signed JWT contains a Base64URL-encoded header, payload, and signature. The header and payload are encoded, not encrypted, so anyone who receives the token can usually decode those portions.
Never treat decoded claims as trusted data
A JWT should be accepted only after cryptographic signature verification and application-specific validation of the expected signing algorithm, issuer, audience, lifetime, and other required claims.