JWT Verify
About this tool
Decoding never proves the signature. This JWT verifier uses Web Crypto locally and reports Signature, Expiration, and Claims separately. HMAC secrets for HS*; PEM public keys for RS/ES. alg none fails. Production still verifies on the server with a trusted key store.
Features
- Local HMAC and asymmetric signature checks
- Expiry with optional clock skew
- Expected iss, aud, and sub
How to use
- Paste the JWT and an HMAC secret or PEM public key.
- Run verify and read Signature, Expiration, and Claims.
- Optionally set expected iss, aud, sub and clock skew.
- On failure, match alg to the key type before clicking again.
When to use it
- An API returns JWT signature invalid and you want to reproduce it
- Confirm an HS256 or RS256 token was not altered
- Clock drift might be tripping exp
Examples
- HS256 fails if the shared secret is off by one character.
- RS256 wants the public key; pasting the private key is unsafe and the wrong step for verify.
FAQ
Are secrets uploaded?
No. Verification uses Web Crypto in the browser. This site does not receive the secret or token.
Which algorithms are supported?
HS256, HS384, HS512, plus RS256/384/512 and ES256/384/512. alg none fails the signature check.
JWT signature invalid — what next?
Match algorithm and key, check the token was not truncated, and confirm you are not using another environment’s secret. This page does not re-sign a payload.
Can this replace backend auth?
No. It is a debugging helper. Production systems must verify on the server.
How is this different from the JWT decoder?
The decoder shows claims. This page answers whether the signature and expiry hold.
Valid signature but expired?
The token was not altered, but exp has passed. Issue a new session, or confirm clock skew is not a false fail.
Back to Hash & Token Tools Hub
Guides