Pages

Topics

Tools

↑↓navigate↵openescclose
Encoding & Security

JWT Decoder

Decode a JSON Web Token header and payload, read every standard claim in UTC and your time zone, verify HS256, RS256, PS256 or ES256 signatures with a secret, a PEM public key, a JWK or a JWKS, and sign a new token in the browser.

Runs entirely in your browser — nothing you paste is uploaded.

JWT claim reference

quick reference
iss
Issuer: the authority that created and signed the token.
sub
Subject: the principal the claims are about, usually a user id.
aud
Audience: the API or service the token is meant for, which must be checked before accepting it.
exp
Expiration time as NumericDate seconds; the token must be rejected after this instant.
nbf
Not before: the token must not be accepted before this instant.
iat / jti
Issued at in NumericDate seconds, and a unique token id used for revocation lists.

Frequently asked questions

answered below the tool
Can this tool verify an asymmetric signature?

Yes. Paste the issuer's public key as PEM, a single JWK or a JWKS and RS256, PS256 and ES256 (and their SHA-384 and SHA-512 variants) are verified in your browser with Web Crypto; in a JWKS the key is picked by the kid in the token header.

Is it safe to paste a token here?

Decoding runs in your browser and nothing is uploaded, but a token is a live credential: revoke it if it may have been logged or shared.

Why does exp show a time in the past?

exp is NumericDate seconds in UTC. The tool shows it in UTC, in your local time and as how long ago it expired.

All Node.js guides