How to use it 01 Paste a token; a leading Bearer is tolerated. 02 Read the header badges (alg, typ, kid) and the decoded JSON segments. 03 Check the time-claims table for exp, iat, nbf, auth_time and updated_at. 04 Turn on Show raw segments to see where each part begins and ends.
Worked readouts
The RFC 7519 sample as loaded by the panel button decodes to alg HS256 , typ JWT , segments of 40 / 94 / 43 characters and a 32 B signature; the same claims in compact form give 36 / 86 / 43 — segment length follows the whitespace in the sample, not the claim set. exp = 1300819380 reads 2011-03-22T18:43:00Z and the status is Expired.
A token with kid = k-2026 , iat = 1760000000 and exp = 1760086400 reads 2025-10-09T08:53:20Z and 2025-10-10T08:53:20Z ; evaluated at 2025-10-09T20:00:00Z it is active with 46,400 seconds remaining.
A millisecond nbf of 1700000000000 is corrected to 1700000000 and reads 2023-11-14T22:13:20Z .
A header with alg: none is flagged, and its signature is 0 B ; a five-part JWE is refused with "encrypted token, cannot be read".
Seconds, and a millisecond guess JWT time claims are numeric seconds since the Unix epoch. Values above 10¹¹ are treated as milliseconds and divided by 1000, because some implementations write Date.now() by mistake; the corrected value is shown and the original stays visible. The signature segment is returned as text plus a byte count — decoding is base64url plus JSON parsing, nothing more.
Limits
Local HMAC only. The panel can verify HS256/HS384/HS512 with a pasted shared secret entirely in the page; it never fetches a key or contacts a server, and asymmetric algorithms (RS/ES/PS) are reported as unverifiable rather than treated as passing. A green time status still only means the time claims look sane.
Not encrypted. A payload is readable by anyone holding the token; clear real tokens from the box when done. What it does not do. It does not sign, mint or validate tokens, and it does not call an issuer's JWKS endpoint. Cron parses schedules and Text diff compares texts.
Decoded is not trusted Anyone can paste a token with alg: none or a rewritten payload; the panel decodes it and the time claims may look valid, because decoding says nothing about authenticity. The local HMAC verifier only checks a secret you already hold — asymmetric tokens still need the public key or JWKS on the server. Treat the output as text from an untrusted source: read the claims, then verify the signature with the matching key. The millisecond correction is a convenience heuristic, not a specification: a value below 10¹¹ is used as-is, and a larger one is silently divided.
Where it is used Reading a token from a bug report Paste the quoted token, read the header and time claims, and copy the payload for the report without sending credentials anywhere.
Checking a clock-skew complaint Compare iat and exp with the current time; the seconds-remaining figure shows whether the failure is expiry or skew.
Privacy Decoding runs entirely in your browser; the token, header and payload are never uploaded, stored or logged.
References
IETF, RFC 7519: JSON Web Token (JWT) , rfc-editor.org (访问日期:2026-10-07)— registered claims and the sample token.
IETF, RFC 7515: JSON Web Signature (JWS) , rfc-editor.org (访问日期:2026-10-07)— compact serialization and the alg header.
IETF, RFC 7518: JSON Web Algorithms (JWA) , rfc-editor.org (访问日期:2026-10-07)— none and the signing algorithms.
Calculators in this hub
Hand-picked tools, one click away. The mini versions compute live and carry your values into the full calculator.
Sources & review
Reviewed by CalcX Editorial Team
Updated 2026-10-07