Header
0 bytesDecoded header appears here.
Security utility
Decode JSON Web Token segments, review algorithms and registered claims, and check token timing fields directly in the browser.
Decoding is local and does not verify the cryptographic signature.
Waiting for a JWT.
Decoded header appears here.
Decoded payload appears here.
Registered and custom payload claims are listed in source order.
| Claim | Value | Meaning |
|---|---|---|
| Decode a JWT to inspect claims. | ||
A compact JWS token usually has header, payload, and signature segments separated by dots. The first two segments are Base64URL encoded JSON.
Claims such as iss, sub, aud, exp, nbf, and iat carry issuer, subject, audience, and timing information. Each application decides which claims matter.
Decoding a JWT is not verification. A trusted verifier must validate the signature, algorithm, issuer, audience, clock skew, and application policy.
Usage guide
It decodes the header and payload, lists claims, highlights timing fields, and shows signature segment metadata without claiming trust.
Load the sample token, compare alg and typ, inspect exp and nbf, then paste your own token to review the claim table.
Use it while debugging authentication flows, checking token expiration, comparing issuers or audiences, or explaining that decoding is not verification.