Developer · JSON Web Tokens

JWT expiry calculator.

Paste a token to see whether it has expired, how long it has left and how long it lived. The token is decoded in this page and is never sent anywhere.

RFC 7519 claimsSignature not verifiedNo upload

How to check a JWT's expiry

  1. Paste the full token. A leading Bearer is removed for you.
  2. Press Calculate.
  3. See whether the token has expired, how long remains, how long it lived and the dates for exp, iat and nbf.
  4. To make a new expiry, enter how far from now it should be and read the epoch value.

How JWT time claims work

A JSON Web Token carries three standard time claims as NumericDate values, which are seconds since 1 January 1970 UTC: exp is when the token expires, nbf is the time before which it must not be accepted, and iat is when it was issued. The lifetime is exp minus iat. A server must reject a token on or after exp and before nbf. If a value has thirteen digits it is probably in milliseconds, which JWT does not use, and the converter flags that.

This tool only reads the payload. It does not verify the signature, so a token that looks valid here may still be forged or revoked. Never trust a token because it decodes cleanly.

Your token stays in the frame

The decoder runs in your browser, inside an isolated frame on this page that has no network access. Your file is read and written back by your own device, so it is not uploaded to TNAADO or anyone else, and nothing is stored. The advertising on this page sits outside the frame and cannot see what you choose. A token can grant access to an account, so it is decoded locally and never sent anywhere. Even so, prefer expired or test tokens when you can, and rotate any live token you have pasted somewhere you do not control.

How JWT expiry works

RFC 7519 defines three time claims as NumericDate values, seconds since 1970-01-01T00:00:00Z: exp (expiration), nbf (not before) and iat (issued at). A token must not be accepted on or after its exp time and must not be accepted before nbf.

Lifetime is exp - iat. To issue a token that lasts an hour, set exp to the current epoch seconds plus 3600. If a value has 13 digits it is probably milliseconds, which JWT does not use.

Source: IETF RFC 7519, sections 2 and 4.1.4 to 4.1.6. This page decodes the payload only; verifying a signature needs the issuer’s key and belongs in your server.

Frequently asked questions

Is my token sent to a server?

No. The token is decoded in this page with built-in browser functions. The isolated tool frame also loads no advertising or analytics scripts.

Does this verify the signature?

No. It reads the claims only, so an unexpired result is not proof the token is genuine.

Why does my token say expired when the server accepts it?

Servers may allow clock skew. This page compares against your device clock with no leeway.

Handle tokens with care

Do not paste production tokens that are still valid into any online tool you do not trust. Expire or rotate a token you have shared.

Advertisement
Advertisement