90 chars · 1 line
118 chars · 10 lines
90 chars · 1 line
118 chars · 10 lines
JWT expiration status
An expired JWT can still be structurally valid and completely decodable. When exp is a valid NumericDate at or before the current time, this decoder labels it Expired and shows the ISO timestamp rather than returning a parsing error. This tool is free to use. No account or payment is required.
Last updated
The decoder treats exp as Unix seconds when it is a finite number. A past value changes the status detail to Expired, but the header and payload are still shown because parsing itself succeeded.
The exp claim 1700000000 corresponds to a past UTC timestamp.
"exp": 1700000000Expired: 2023-11-14T22:13:20.000ZCommon questions
No. Expiration is a claim status. A structurally valid expired token can still be decoded.
Changing the payload changes the signed data and does not create a valid replacement token. Obtain a fresh token from the issuer.
No. It only decodes locally and displays expiration status; application-specific validation belongs in a trusted verifier.
Debugging a specific JWT issue? Browse JWT troubleshooting.