Debug JWTs in your browser safely

Decode claims, check expiry timelines, and verify cryptographic signatures on authentication tokens without handing active credentials to third-party servers.

Why pasting tokens into cloud debuggers is dangerous

A JSON Web Token (JWT) in your clipboard is not just text; it is an active bearer credential. Anyone who holds that string can make authorized API calls on behalf of the user or service account until the token reaches its expiration timestamp. Pasting an authorization header into a random online debugging website is functionally equivalent to pasting a session password into a public form.

Even reputable debugging websites can expose your organization to risk through client-side third-party scripts, browser extensions, browser history caching, or server access logs. If an engineer debugs a production issue by pasting an admin token into an external site, that credential must be treated as compromised. Debugging tokens purely in local browser memory avoids this security hole.

The anatomy of a JSON Web Token

A standard JWT consists of three Base64URL-encoded segments separated by periods: Header.Payload.Signature. Understanding each segment helps pinpoint authentication bugs quickly:

  • Header: Specifies the cryptographic algorithm (such as RS256 or HS256) and optional key identifiers (kid) used by verification middleware.
  • Payload: Contains authorization claims, including subject (sub), issuer (iss), audience (aud), and Unix epoch timestamps for issued-at (iat), not-before (nbf), and expiration (exp).
  • Signature: The cryptographic proof created by the signing party to guarantee the token has not been altered in transit.

Step-by-step: how to inspect and verify tokens locally

  1. Paste your token string into JWT Decoder. The tool decodes the Base64URL strings in local JavaScript without submitting any HTTP requests.
  2. Verify claim boundaries with JWT Expiration Checker. It computes human-readable timestamps, highlights whether the token has expired, and shows the remaining validity window.
  3. Confirm cryptographic integrity with JWT Verify. Supply your public certificate, JWKS URL, or HMAC secret to validate the digital signature on-device using Web Crypto.
  4. Inspect configuration defenses using JWT Security Inspector to check for known vulnerabilities, such as unsigned tokens (alg: none) or mismatched audience claims.

Common token validation pitfalls

When API requests return unexpected 401 Unauthorized or 403 Forbidden status codes, check these frequent discrepancies:

  • Clock skew: If your server clock differs slightly from the identity provider, tokens evaluated near issuance or expiration may fail. Check the nbf and exp margins.
  • Audience mismatches: Tokens issued for a frontend client ID often fail backend validation if the microservice expects an API-specific audience identifier.
  • Format alteration: Stripping the Bearer prefix before decoding prevents string offset errors.

To learn more about defensive authentication practices, read our guide on decoding JWTs safely without cloud debuggers or explore our JWT workflow hub.

Open JWT Decoder Verify JWT signature Explore JWT workflow