90 chars · 1 line
118 chars · 10 lines
90 chars · 1 line
118 chars · 10 lines
JWT claim troubleshooting
A JWT can be structurally valid and decode cleanly without an exp claim. In that case the decoder has no expiration NumericDate to format, so it shows the payload but no Expires or Expired detail. Whether exp is mandatory is a verifier or application policy decision, not a Base64URL decoding rule. This tool is free to use. No account or payment is required.
Last updated
Only a finite numeric exp value is converted to an ISO timestamp. If the claim is missing, the original payload remains visible and no expiration status is added.
The token includes iat but no expiration claim.
{"sub":"123","iat":1700000000}No Expires or Expired detailCommon questions
Not as a decoding matter. Your identity provider or application may still require exp as part of its validation policy.
No. It only displays claims already present in the payload.
No. Decoding does not verify the signature, issuer, audience, or application policy.
Debugging a specific JWT issue? Browse JWT troubleshooting.