About the JWT Decoder
Debugging authentication often means checking what is inside a token: which user it belongs to, which roles it grants and when it expires. Paste a JWT and see its header and payload as formatted JSON, with the iat and exp timestamps converted to readable dates.
Because tokens can grant access to real accounts, decoding happens entirely in your browser. The signature is not verified — that requires the secret or public key on your server.
How to use the JWT Decoder
- Paste a JWT (with or without the “Bearer” prefix).
- Read the decoded header and payload.
- Check the algorithm and expiry in the summary tiles.
Features
- Header and payload as formatted JSON
- iat, exp and nbf as readable dates
- Expired / not-yet-valid status
- HMAC signature verification with a secret
- Secret never leaves your browser
Supported formats
- JWT (JWS compact serialization)
Frequently asked questions
Is my code uploaded?
No. Formatting and minifying run in your browser, so proprietary code and secrets never leave your device.
Does this verify the signature?
No. Verification needs the signing key. Never trust a token’s contents on the server without verifying it.
Can it decode encrypted tokens (JWE)?
No. Encrypted tokens have five parts and can only be read with the decryption key.