JWT Decoder
Paste a JSON Web Token to read its header and claims. See when it was issued and when it expires, and check an HMAC signature with your secret.
Token
Header
Payload
Times and signature
Decoding does not need the secret. Anyone holding a JWT can read it, so never put passwords in one.
Decoded in this browser tab. Tokens are never sent anywhere.
How to use the JWT Decoder
- Paste the token. A leading “Bearer ” is removed for you.
- Read the decoded header and payload.
- Check the issued, not-before and expiry times, shown in your time zone.
- To check an HS256, HS384 or HS512 signature, enter the secret.
Example
Input
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5cResult
{
"sub": "1234567890",
"name": "John Doe",
"iat": 1516239022
}Signed with the secret your-256-bit-secret.
What it does
- Expiry at a glance
- The exp, iat and nbf claims are shown as dates with “2 hours ago” or “in 5 minutes”, and expired tokens are flagged.
- HMAC signature check
- Verifies HS256, HS384 and HS512 signatures with the browser’s Web Crypto. The secret never leaves this page.
- Clear errors
- Explains malformed tokens, including encrypted JWE tokens, which cannot be read without the key.
Frequently asked questions
Is it safe to paste a production token here?
Decoding happens in your browser and nothing is sent anywhere. Still, a valid token is a credential, so treat it like a password and prefer expired or test tokens.
Does decoding prove the token is genuine?
No. Anyone can decode a JWT, since the payload is only Base64URL-encoded. Only a signature check with the right key proves it was not changed.
Can I verify RS256 or ES256 tokens?
Not yet. Those need the issuer’s public key. You can still decode and read them here.