JWT Decoder & Signature Verifier
Paste a JSON Web Token to read its header and claims, see the issued and expiry times as real dates, and check the signature with the secret or public key. The token is decoded in your browser, so access tokens from real systems are not sent to anyone.
How to use this tool
- Paste the token. A leading "Bearer " is removed for you.
- Read the header and payload, and the iat, nbf and exp times with how long the token is still valid.
- To check the signature, enter the shared secret for HS256/384/512, or paste the public key (PEM, JWK or JWKS) for the other algorithms.
- Press "Verify signature".
What this tool can do
Header and payload
Both parts are decoded from Base64URL and shown as formatted JSON.
Expiry at a glance
iat, nbf and exp are shown in your local time and in UTC, with whether the token has expired or how long it remains valid.
Signature verification
HS256, HS384, HS512, RS256 to RS512, PS256 to PS512, ES256, ES384, ES512 and EdDSA (Ed25519), with a secret, a PEM public key, a JWK or a JWKS.
Stays in your browser
Tokens and keys are never uploaded, which matters because a valid access token works as a password.
Tips and common problems
The signature is not valid
For HS tokens the secret must match exactly; some systems use a Base64-decoded secret instead of the text. For RS and ES tokens make sure the public key belongs to the key ID (kid) in the header.
The token has five parts
That is an encrypted JWE, not a signed JWT. Its content cannot be read without the private key.
alg is "none"
The token carries no signature. Servers must reject such tokens unless they were deliberately designed to accept them.
Frequently asked questions
Is it safe to paste a production token here?
The token is decoded and verified in your browser and not sent anywhere. Still, treat live tokens like passwords and prefer expired or test tokens when you can.
Does decoding a JWT prove it is genuine?
No. Anyone can write any payload. Only a valid signature checked with the right key shows that the token came from the issuer.
Where do I find the public key for RS256?
Identity providers publish it in a JWKS, usually at /.well-known/jwks.json. Paste the whole JWKS or the single JWK; the first key is used.
Can this tool create or sign tokens?
No, it decodes and verifies. Use your server library to issue tokens, with a key from the Key Pair Generator or the Secret Key Generator.
More developer tools
Key Pair Generator
RSA, ECDSA and Ed25519 key pairs as PEM, PKCS#1, OpenSSH and JWK, with the SSH fingerprint.
Open tool →Base64 Encode & Decode
Text and files to Base64 or Base64URL, data URIs, and Base64 back to text, hex or a file.
Open tool →Secret Key Generator
Random secrets in hex, Base64 or Base64URL, API keys and passwords, with the entropy shown.
Open tool →