Decode a JWT to read its header, payload and claims, check expiry and verify the signature - privately in your browser.
Last updated:
Production tokens are safe here: decoding and verification run on your device.
| Part | Contains | Encoded as |
|---|---|---|
| Header | Algorithm (alg) and type (typ), sometimes key ID (kid) | Base64URL JSON |
| Payload | Claims: user ID, roles, expiry and custom data | Base64URL JSON |
| Signature | Proof the token was issued by the key holder and not changed | Base64URL bytes |
| Claim | Name | Meaning |
|---|---|---|
| iss | Issuer | Who created the token |
| sub | Subject | The user or entity the token is about |
| aud | Audience | Which API should accept it |
| exp | Expiration | Unix time after which it is invalid |
| nbf | Not before | Unix time before which it is invalid |
| iat | Issued at | When it was created |
| jti | JWT ID | Unique ID to prevent reuse |
| Algorithm | Type | Verify with |
|---|---|---|
| HS256 / HS384 / HS512 | HMAC (shared secret) | The same secret |
| RS256 / RS384 / RS512 | RSA | Public key (PEM) |
| PS256 / PS384 / PS512 | RSA-PSS | Public key (PEM) |
| ES256 / ES384 / ES512 | ECDSA | Public key (PEM) |
| none | Unsigned | Never accept |
| Language | Example |
|---|---|
| JavaScript | JSON.parse(atob(token.split(".")[1].replace(/-/g,"+").replace(/_/g,"/"))) |
| Node.js | jwt.decode(token) / jwt.verify(token, secret) (jsonwebtoken) |
| Python | jwt.decode(token, key, algorithms=["HS256"]) (PyJWT) |
| Bash | echo $TOKEN | cut -d. -f2 | base64 -d |
| Place | How to get it |
|---|---|
| Browser request header | DevTools → Network → request → Headers → Authorization: Bearer … |
| Local or session storage | DevTools → Application → Local Storage |
| Cookies | DevTools → Application → Cookies (HttpOnly ones are hidden from scripts) |
| Postman | Authorization tab or the Console |
| Auth providers | Auth0, Firebase, Cognito, Okta return id_token and access_token |
Paste it above. The header and payload are decoded instantly, with claims explained and expiry checked.
Decoding runs entirely in your browser and nothing is sent. Still, tokens grant access, so avoid sharing them elsewhere.
Look at the Status card. It compares the exp claim with the current time and shows how long until or since expiry.
Yes. Paste the HMAC secret for HS256/384/512, or the PEM public key for RS, PS or ES algorithms, and press Verify.
Yes. The header and payload are only Base64URL-encoded. The secret is needed only to verify or create the signature.
A JWT (JWS) is signed but readable. A JWE is encrypted and has 5 parts; its content cannot be read without the key.
Check whether the secret is Base64-encoded (tick the box) and that the token was copied fully without spaces.
Authorization headers send "Bearer