JWT Decoder & Debugger
What is a JSON Web Token (JWT)?
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
Why Use Our JWT Debugger?
JWTs often contain sensitive user identity data, roles, and authorization scopes. Unlike many online tools that send your token to an external server, our debugger runs 100% client-side in your browser. Your authentication tokens and API secret keys never leave your machine.
What this tool does
What this tool does
- Header & payload decoding: Instantly view the algorithm, token type, and all claims in tree or JSON view
- RFC 7519 claims inspector: Structured breakdown of iss, sub, aud, exp, nbf, iat, and jti with human-readable timestamps
- Live expiration countdown: Shows real-time validity status with active countdown or expiration elapsed time
- Multi-algorithm verification: Verify signatures locally for HS256 (HMAC), RS256 (RSA), and ES256 (ECDSA)
- Developer quick-copies: 1-click copy for Authorization: Bearer headers and cURL commands
How to Use
- Paste Token or Pick Sample: Paste your raw JWT string or pick one of the pre-loaded samples (Active HS256, Expired Token, RBAC Token).
- Inspect Claims & Expiry: Review standard registered claims (issuer, subject, audience, issued time) and live expiration status.
- Verify Signature: Enter your HMAC secret key or RSA/ECDSA public key (PEM) to verify the token's cryptographic integrity.
- Quick Copy for APIs: Click "Copy Authorization: Bearer" or "Copy cURL Command" to use your token directly in API clients or terminals.
Glossary
- Header
- The first segment of a JWT specifying token type and signing algorithm (e.g. HS256, RS256, ES256).
- Payload
- The second segment of a JWT containing registered claims and application-specific identity or authorization data.
- Signature
- The third segment created by cryptographic hashing or signing of the header and payload using a secret or private key.
- Standard Claims (RFC 7519)
- Standard registered claim names including sub (subject), iss (issuer), aud (audience), exp (expiration), nbf (not before), iat (issued at), and jti (JWT ID).
- HS256 vs. RS256 vs. ES256
- HS256 uses symmetric HMAC-SHA256 with a shared secret; RS256 uses asymmetric RSA; ES256 uses elliptic curve cryptography (ECDSA P-256) for compact, high-performance signatures.