Can the ByteKiln JWT Decoder verify JWT signatures?
Yes — for HS256, HS384, and HS512 tokens. Enter your HMAC secret in the Signature panel and the tool verifies the signature locally using the browser's SubtleCrypto API. RS256 and asymmetric algorithms are not yet supported.
Does it tell me if the JWT token is expired?
Yes. If the payload includes an exp claim, the tool compares it against the current time and shows a clear Valid or Expired status badge. The exact expiry date and time are also displayed.
What security warnings does the JWT Decoder show?
The tool warns when the algorithm is set to "none" (no cryptographic signature), when the exp claim is missing entirely, or when the token has already expired. These are common JWT security issues to watch for.
Is my JWT token sent to a server?
No. The ByteKiln JWT Decoder runs entirely in your browser. Your token is decoded locally using JavaScript and never transmitted, logged, or stored anywhere.
What is the difference between the JWT header and payload?
The header identifies the token type and signing algorithm (e.g. HS256). The payload contains the claims — statements about the subject like user ID, roles, and expiry time. Both sections are Base64URL-encoded JSON objects.