โ† back

jwt decoder

paste ยท decode ยท read. all local, nothing sent.
A JWT (JSON Web Token) has three base64url parts separated by dots: header.payload.signature. The header and payload are just base64url-encoded JSON โ€” anyone can read them (they are not encrypted). The signature is a hash of the first two parts using a secret; it's what lets a server verify the token wasn't tampered with. If you're passing secrets in a JWT payload: don't.

standard claims (rfc 7519)

ississuer โ€” who created the token
subsubject โ€” who the token is about (usually a user id)
audaudience โ€” who the token is for
expexpiration โ€” unix timestamp; server rejects after this
nbfnot before โ€” unix timestamp; server rejects before this
iatissued at โ€” unix timestamp when token was made
jtijwt id โ€” unique identifier for replay prevention