The Tripartite Anatomy of a JSON Web Token
A JSON Web Token consists of three base64url-encoded components separated by dots: . The Header specifies the cryptographic algorithm (e.g., HS256, RS256); the Payload contains identity claims (e.g., subject, issuer, expiration, scopes); and the Signature guarantees that the message has not been altered in transit.
Critical Claims to Inspect
When debugging authentication sessions, always inspect standard claims: - (Subject): The unique user ID identifier. - (Issuer): The trusted authentication authority (e.g., Auth0, Firebase, Keycloak). - (Expiration): The Unix timestamp when the token ceases to be valid. - (Not Before): The earliest time the token may be processed.
1// Safe client-side Base64Url decoding of JWT payloads2export function parseJwtPayload(token: string) {3 const base64Url = token.split('.')[1];4 const base64 = base64Url.replace(/-/g, '+').replace(/_/g, '/');5 const jsonPayload = decodeURIComponent(6 atob(base64)7 .split('')8 .map((c) => '%' + ('00' + c.charCodeAt(0).toString(16)).slice(-2))9 .join('')10 );11 return JSON.parse(jsonPayload);12}The Security Risk of Online Decoders
Transmitting production bearer tokens containing confidential user emails and tenant scopes to unverified online decoders poses a serious data leak risk. The TechTools JWT Debugger executes 100% locally in your browser sandbox, ensuring your authentication tokens remain completely confidential.
Put This Guide into Practice with Free Online Tools
100% in-browser processing, zero data retention, and instant execution.
JWT Debugger & Decoder
Decode and inspect JSON Web Tokens (JWT) headers, payloads, and expiration claims securely.
Base64 Encoder & Decoder
Encode text or binary data into Base64 format or decode Base64 strings with UTF-8 support.
Hash Generator (MD5, SHA-256, SHA-512)
Generate cryptographic checksums and hashes including SHA-256, SHA-512, SHA-1, and MD5.