Australian Jeevitham TECHDeveloper tools

Tech / JWT Decoder

JWT Decoder

Paste a JSON Web Token to read its header and payload, with issued, not-before and expiry times in plain dates. Your token never leaves this page.

Header

Payload

Check an HS256 signature (optional)

Only HMAC tokens (HS256, HS384, HS512) can be checked here. Tokens signed with RS/ES keys need the issuer's public key. Never paste a production secret into any website you do not trust.

About JSON Web Tokens

A JSON Web Token (JWT), defined in RFC 7519, is a compact way to pass facts - such as who a user is and when their login ends - between systems. It has three parts separated by dots: the header, the payload and the signature. The header and payload are just URL-safe Base64 JSON, so anyone can read them. The signature proves they have not been changed.

Common claims in the payload

ClaimMeaning
issIssuer - who created the token
subSubject - usually the user's ID
audAudience - who the token is for
expExpiry time
nbfNot valid before this time
iatIssued at

The times are Unix timestamps in seconds. You can check one with the timestamp converter.

HS256 or RS256?

HS256 signs and checks the token with one shared secret. RS256 signs with a private key and checks with a public key, so other services can verify tokens without being able to create them. This page can check HS256 signatures.

Is it safe to decode a token here?

Decoding happens in your browser and the token is not sent anywhere. But while a token is valid it works like a password, so avoid pasting live production tokens into any website, and never put secrets in a JWT payload - it is not encrypted.