A JWT decoder shows a token's header and claims. Reading them does not establish who issued the token or whether an application should accept it. You can inspect an expiration claim with JWT Decoder, but the result deliberately includes signatureChecked: false.
Decode a synthetic token with time claims
- Open the decoder and wait for its Input field to load.
- Paste the complete teaching token below, including the final dot.
- Select Decode and inspect the Result. No key or secret is required for decoding.
eyJhbGciOiJub25lIn0.eyJzdWIiOiJkZW1vIiwibmJmIjoxNzkzNTAyMDAwLCJleHAiOjE3OTM1MDU2MDB9.
The header is {"alg":"none"}. Its payload is:
{
"sub": "demo",
"nbf": 1793502000,
"exp": 1793505600
}
This unsigned example is not a credential and must not grant access. The decoder displays the numbers and an untrusted-claims warning; it does not label the token valid, expired or safe. The dates below are fixed teaching values, not a live status report.
Convert JWT seconds to a readable UTC date
JWT NumericDate counts seconds from the Unix epoch. JavaScript Date expects milliseconds. For this example, multiply by 1,000 before constructing a Date:
new Date(1793502000 * 1000).toISOString()
// "2026-11-01T03:00:00.000Z"
new Date(1793505600 * 1000).toISOString()
// "2026-11-01T04:00:00.000Z"
Z means UTC. The expiry instant is also 09:30 in India (UTC+05:30). Omitting the multiplication produces 1970-01-21T18:11:45.600Z for this exp value. That result is a unit mistake, not evidence that the original token claims a 1970 expiry.
Check the exact expiry boundary
Under RFC 7519's exp and nbf rules, exp excludes its instant; nbf includes its instant. With zero clock tolerance, compare these hypothetical reference times:
| Reference time (UTC) | Time-claim comparison only |
|---|---|
| 1 November 2026, 02:59:59 | Before nbf: too early. |
| 1 November 2026, 03:00:00 | At nbf, before exp: within the stated time window. |
| 1 November 2026, 03:30:00 | Before exp: 1,800 seconds remain. |
| 1 November 2026, 04:00:00 | At exp: outside the stated time window. |
These comparisons do not authenticate the claims. A verifier may allow a small configured clock tolerance; use the application's documented policy. A missing exp is not proof of validity or indefinite access. A string such as "1793505600" is not the NumericDate number required for exp, even if this inspection tool displays it.
What decoding cannot tell you
A plausible timestamp, user ID or role can be forged. The decoder performs no signature, expiry, issuer or audience validation. Application verification needs trusted keys, the expected issuer and audience, and a configured algorithm policy. JWT best practices require algorithm verification; a token's visible alg value is not permission to trust that algorithm.
The workspace reads three Base64URL segments containing JSON object header and payload. It does not decrypt five-part JWE tokens. For ordinary text encoding instead, use Base64 Encoder/Decoder.
Keep real access and refresh tokens out of screenshots, shared clipboard history and support messages. Use synthetic examples when sharing a debugging question. Browser-local decoding does not remove the access risk of a copied credential.