JWT Decoder
Decode and inspect JSON Web Tokens instantly β view headers, payloads, claims, and expiration status
JWT Structure and How to Handle Tokens Safely
Three parts (RFC 7519)
A JWT is `header.payload.signature` joined by dots. The header (algorithm) and payload (claims) are merely Base64URL-encoded β not encrypted; anyone can read them. The signature only proves the content wasn't altered.
Reading standard claims
- `exp` / `iat` / `nbf`: expiry, issued-at, and not-before times (Unix timestamps)
- `sub`: subject (user ID), `iss`: issuer, `aud`: audience
Security notes
- Never put secrets (passwords, national IDs) in the payload β every token holder can read it.
- This decoder runs entirely in your browser and sends nothing to a server, but pasting production tokens into random online tools is a habit worth avoiding.
- Decoding is not verification: servers must validate the signature and `exp` before trusting any claim.
Frequently Asked Questions
Related Tools
Sources & References
Content last reviewed: 2026-08-22