Skip to content
Docs navigationBrowse tools →

Tool docs

JWT Debugger & Decoder

Decode, verify and security-check JWTs locally in the browser. Inspect claims with relative times, verify HS/RS/PS/ES/EdDSA signatures with Web Crypto, compare two tokens and generate test tokens — without sending tokens or keys anywhere.

Tool

Overview

01

JWT Debugger & Decoder

The JWT Debugger is useful when you need to inspect a token's structure, claims, and expiry at a glance. It keeps the workflow local and transparent, which matters when the token belongs to an internal system or production environment.

Guide

Common usage patterns

01

Decode and inspect safely

  • Paste a bearer token or raw JWT and let the tool split it into header, payload, and signature parts.
  • Inspect common claims like exp, iat, aud, or iss before debugging application behavior.
  • Copy decoded JSON when you need to compare claims or attach them to an issue.
  • Use the generator only for test fixtures and demos, never as proof that a production token is trustworthy.

Guide

Edge cases & common pitfalls

01

Decoding is not trust

  • A decoded token is only readable, not trustworthy: verify the signature, then check exp, nbf, iss and aud against what your server expects.
  • A valid signature on an expired token and an invalid signature are different failures — the Checks panel reports them separately.
  • Base64URL issues, missing segments, '=' padding or non-JSON payloads break decoding even if the string 'looks like a JWT'.
  • Use only public keys here. Never paste private keys, and treat any production token as sensitive.

Internals

How it works internally

01

Three-part split and Base64URL decoding

Birdor separates the token into header, payload, and signature, Base64URL-decodes the first two parts locally, and leaves the signature as-is. The tool is intentionally explicit about what it does not verify.