Examples
-
Sample HS256 JWT
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
About JWT Decoder
A JWT looks like gibberish until you realize it's just three Base64URL segments glued together with dots: header, payload, signature. Once you know that, reading one is trivial - verifying it safely is not.
Paste a token and this decodes the header and payload back into readable JSON so you can inspect claims, expiry, and algorithm at a glance - no server round-trip, no account required.
Decoding is not the same as verifying. Anyone can read an unsigned JWT's contents; that's by design. Never trust a token's claims without checking its signature against your issuer's keys first, and treat production tokens with the same care as a password.
FAQ
- Is it safe to paste production JWTs?
- Processing is local, but anyone with screen access can read them. Prefer dev tokens; rotate secrets if exposed.
- Why not use plain Base64 decode?
- JWT uses Base64URL without padding. Use this decoder, not the MIME Base64 tool.