Bearer token analysis
The JWT decoder splits a bearer token into header, payload, and signature. Claims appear in a readable layout, and you can verify HMAC with a secret—ideal for OAuth, SSO, and internal API debugging.
Header and message body
Algorithm and token type sit in the first block; claims live in the second. Base64 and truncation errors are flagged early.
Try a sample token to compare fields with your identity provider docs.
Claims list
Standard fields such as iss, sub, exp, and aud are listed clearly; expired exp is obvious without manual epoch math.
Nested claim objects expand like JSON elsewhere in the app.
HMAC verification with a secret
Enter a secret to confirm the token was not tampered with. The key is not stored or sent to a server—crypto runs locally.
For asymmetric algorithms, follow your IdP guide and verify with the published public key.