Decode JWT tokens to view header, payload, and signature info
Yes, completely free. Debug as many tokens as you need — ideal for developers troubleshooting authentication flows, API integrations, and SSO implementations.
No. All decoding happens locally in your browser. Your tokens — which may contain sensitive user data, API credentials, or session information — never leave your device. This is critical for security: you should never paste real production tokens into an online service.
A JWT (JSON Web Token) contains three parts: (1) Header — specifies the signing algorithm (HS256, RS256, ES256, etc.) and token type. (2) Payload — contains registered claims like iss (issuer), sub (subject), aud (audience), exp (expiration time as Unix timestamp), iat (issued-at time), plus any custom claims your application adds (user ID, roles, permissions, tenant ID). (3) Signature — the cryptographic signature that verifies the token has not been tampered with. This tool decodes the header and payload for inspection; signature verification requires the secret key or public key, which you should keep secure. Use the Unix timestamp converter on our site to translate exp/iat values into human-readable dates.