FAQ
Frequently Asked Questions
What is a JWT (JSON Web Token)?
A JWT is a compact, URL-safe token format used for securely transmitting information between parties. It consists of three parts: a header (algorithm and type), a payload (claims), and a signature. JWTs are commonly used for authentication, authorization, and information exchange in modern web applications.
Is it safe to decode JWTs online?
Our JWT Debugger processes everything client-side in your browser. Your tokens are never sent to any server, making it completely safe to use. However, never share your production tokens publicly, as payloads may contain sensitive information.
What are JWT claims?
JWT claims are statements about the token subject. Registered claims include 'iss' (issuer), 'sub' (subject), 'aud' (audience), 'exp' (expiration), 'iat' (issued at), and 'nbf' (not before). Custom claims can include any application-specific data.
How do I verify a JWT signature?
JWT signatures are verified using the algorithm specified in the header (e.g., HS256, RS256). This decoder shows the signature but doesn't verify it—you need the secret key or public key for verification. Never expose your secret keys.
Why is my JWT showing as expired?
JWTs have an 'exp' (expiration) claim that specifies when the token expires. If the current time is past this timestamp, the token is considered expired. You'll need to obtain a new token from your authentication provider.
What's the difference between HS256 and RS256?
HS256 uses a symmetric secret key for both signing and verification. RS256 uses asymmetric cryptography with a private key for signing and a public key for verification. RS256 is preferred for distributed systems where the verification key needs to be shared.