JWT Decoder
Decode and inspect JSON Web Tokens — view the header, payload claims, and signature in a readable format (RFC 7519).
Optional: paste the issuer's public key to verify the signature locally in your browser when you decode. The algorithm is read from the token's own header and must match the key type. If you generated this token with the JWT Encoder tool, use the public key shown there.
What is a JWT?
A JSON Web Token (JWT, pronounced "jot") is a compact, URL-safe way to represent claims between two parties. A JWT consists of three base64url-encoded segments joined by dots: a Header, a Payload, and a Signature. They are widely used as OAuth 2.0 access tokens, ID tokens in OpenID Connect, and for other assertion-based protocols.
Header
Describes the token itself: the type and the algorithm used to sign it. Common fields:
- alg: the signing algorithm, e.g. RS256 (RSA + SHA-256), ES256 (ECDSA), or HS256 (HMAC). Determines how the signature was computed.
- typ: token type, typically JWT. DPoP proofs use dpop+jwt; JWT-SVIDs use other values.
- kid: key ID, a hint to the recipient about which public key to use for verification. Often maps to a key in the issuer's JWKS endpoint.
Payload
Contains the claims, statements about the subject and additional metadata. RFC 7519 defines a set of registered claim names:
- iss (Issuer): who issued the token, typically the Authorization Server URL.
- sub (Subject): the principal the token is about, usually a user or service identifier.
- aud (Audience): intended recipient(s). A resource server should reject tokens where it is not listed.
- exp (Expiration Time): Unix timestamp after which the token must not be accepted.
- iat (Issued At): Unix timestamp when the token was issued.
- nbf (Not Before): Unix timestamp before which the token must not be accepted.
- jti (JWT ID): unique identifier for the token, useful for preventing replay attacks.
Any additional fields beyond the registered names are custom claims added by the issuer, for example scope, roles, or application-specific context.
Signature
The third segment is the signature, computed by the issuer over the encoded header and payload using the private key indicated by alg. It guarantees the token has not been tampered with and that it was issued by the expected party. This tool can verify the signature client-side if you provide the issuer's public key (SPKI PEM) below; otherwise verification typically happens on the server, using a public key fetched from the issuer's JWKS URI.