JWT decode and verify
Paste a token to decode the JWT and read its dates in plain words, then check its signature with a key. It runs in your browser, so your token and key stay on your device and are not saved.
Decoding is not verifying. Anyone can write a token that reads well here. Only a signature check with the right key, plus your service's own checks, shows that a token can be trusted.
Nothing is uploaded or saved. This runs on this device.
Check these
What it claims
Check the signature
How to decode a JWT
- Paste the token. A Bearer prefix is removed for you.
- Read the header, the payload and what the dates mean.
- To check the signature, paste the secret or the public key.
- Save the decoded parts as a file if you need them.
Questions
Is my token uploaded or saved?
No. The token and key are read in your browser and kept only until you close the page, and nothing goes in your browser's storage. You can check this yourself. A live token is still a credential, so prefer an expired one or a test one when you can, and turn off browser extensions you don't trust.
Why is decoding not the same as verifying?
The header and payload are only Base64, with no encryption, so anyone can read them or write new ones. Only the signature ties them to a key. A token with a good-looking payload may be a forgery until the signature has been checked.
Does a valid signature mean the token is good?
No. It means the holder of the key signed these exact parts. The result here does not look at the expiry, the audience or the issuer. The dates are shown apart, and your service must check them too.
Which algorithms can it check?
HS256, HS384, HS512, RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384 and ES512, with your browser's WebCrypto. EdDSA works where the browser supports Ed25519, and the page says so if not. Our tests check tokens signed by Node's crypto module and the example from RFC 7515. It does not decrypt encrypted tokens (JWE). It shows their header only.
Why was my key refused?
Browsers read public keys in the form that starts BEGIN PUBLIC KEY, and JWK. The message gives an openssl command for the older RSA PUBLIC KEY form and for a certificate. A private key is refused, because checking needs only the public key.
What do the warnings mean?
Alg "none" means the token claims to have no signature. An HS algorithm with a public key is a known attack, where a service uses its public key as a shared secret, so the page will not check it. A repeated key in the payload can read differently in different programs. A date over 100 billion is probably in milliseconds, while the standard uses seconds.