93 chars · 1 line
120 chars · 10 lines
93 chars · 1 line
120 chars · 10 lines
JWT NumericDate issue
A quoted iat value does not break JSON decoding, but it is not treated as a numeric issued-at timestamp. The decoder preserves the string in the payload and omits the Issued detail rather than silently coercing claim types. This tool is free to use. No account or payment is required.
Last updated
The decoder does not guess that numeric-looking strings are timestamps. This makes type mistakes visible instead of hiding them behind automatic coercion.
The string remains in JSON but does not create an Issued detail.
"iat":"1700000000""iat":1700000000Common questions
No. It is valid JSON, which is why the token can decode successfully.
Silent coercion would change claim types and could hide issuer bugs.
Only after the token has been verified and accepted under your issuer policy.
Debugging a specific JWT issue? Browse JWT troubleshooting.