Frequently Asked Questions
What is a JWT token?
JWT (JSON Web Token) is a compact, URL-safe token format used for securely transmitting information between parties. It consists of three Base64URL-encoded parts: header, payload, and signature, separated by dots.
Can this tool verify JWT signatures?
This tool decodes and inspects JWT tokens — it displays the header, payload, and raw signature. Signature verification requires the secret key or public key, which is not needed for decoding.
What are exp and iat claims?
exp (expiration time) indicates when the token expires. iat (issued at) indicates when the token was created. Both are Unix timestamps. This tool automatically validates these claims and highlights expired tokens.
Is my token safe?
Yes. All decoding happens entirely in your browser. No data is ever sent to any server. You can verify this in the Network tab of your browser's developer tools.
What JWT algorithms are supported?
This decoder works with any JWT regardless of the signing algorithm (HS256, RS256, ES256, etc.) because it only decodes the token — it does not verify signatures.
What is the difference between JWT and session tokens?
Session tokens are random strings stored server-side, requiring a database lookup on every request. JWTs are self-contained — they carry all user data inside the token itself, eliminating server-side storage but requiring careful expiration management.
Is it safe to store JWT in localStorage?
Storing JWT in localStorage is vulnerable to XSS attacks — any JavaScript on the page can read it. Use httpOnly cookies instead for sensitive tokens, or keep short-lived JWTs in memory and use refresh tokens in httpOnly cookies.
What is the difference between HS256 and RS256 in JWT?
HS256 uses a shared secret key for both signing and verification — simpler but requires sharing the secret. RS256 uses a private/public key pair — the issuer signs with a private key, anyone can verify with the public key. Use RS256 for distributed systems.