JWT Expiry Checker
Instantly see if a JWT is expired — with exact expiry time in your timezone, UTC, and remaining lifetime.
Tool input is processed locally in your browser and is not submitted to CodeNimbleTools. Avoid pasting production secrets into any device or website you do not fully trust.
Paste a JWT to see whether it is expired, and exactly when it expires in your timezone and UTC.
Decoding happens locally. The signature is not verified and the token is never sent anywhere.
About this tool
"Is this token still valid?" shouldn't require a Node REPL. Paste a JWT and this checker decodes it locally, reads the exp, iat and nbf claims, and tells you plainly whether it's expired — plus exactly when it expires in your local time and UTC, and the token's total lifetime.
Bearer prefixes are stripped automatically, so you can paste straight from an Authorization header.
How to use it
- Copy a JWT (with or without the
Bearerprefix). - Paste it — the verdict appears instantly.
- Check the exp/iat/nbf rows for precise timestamps.
- Remember: signature is NOT verified — this is a decoder, not a validator.
Useful ways to apply it
- Debugging 401 errors — is the token expired or is something else wrong?
- Checking how long your auth provider's tokens actually live.
- Verifying that a refresh flow issued a token with a future exp.
- Confirming an nbf (not-before) claim isn't rejecting early use.
Worked example
Example input
JWT with exp=1900000000Expected output
Shows the exp timestamp and whether it is before/after the browser clock; signature not verifiedEdge cases to check
- Clock skew can affect near-boundary tokens.
- Tokens may omit exp.
- A future exp value does not prove the token is valid or authorized.
Known limitations
This is a timestamp inspection aid. It does not verify signature, issuer, audience, revocation or server-side session state.
How this tool was reviewed
Reviewed with expired, future, missing and malformed exp values.
Standards and technical references
See the site-wide testing methodology for fixture categories, privacy checks and correction policy.
Frequently asked questions
Is the token sent to a server?
Why does it say the signature is not verified?
What if there's no exp claim?
Privacy
Tool input is processed locally in your browser and is not submitted to CodeNimbleTools. Avoid pasting production secrets into any device or website you do not fully trust.