JWT Decoder

Encoded Token
HEADER: Algo & Token Type
Loading...
PAYLOAD: Data
Loading...
SIGNATURE
Signature info will appear here
100% Client-Side • Zero Data Sent to Servers

Online JWT Decoder & Claims Inspector

Inspect JSON Web Token headers, payloads, and cryptographic signatures in real time directly in your browser.

Local Processing & Data Privacy

All formatting, parsing, decoding, and validation executes entirely within your browser using modern Web APIs and JavaScript. Your tokens, JSON payloads, regex inputs, and queries never leave your computer.

About this Tool

JSON Web Tokens (RFC 7519) are standard compact URL-safe tokens commonly used for authentication headers, OAuth 2.0 access tokens, and OpenID Connect ID tokens. A typical JWT consists of three base64url-encoded parts separated by periods: the Header (specifying algorithm and token type), the Payload (containing claims like sub, exp, iss, and aud), and the Signature.

This tool parses the raw JWT string, base64url-decodes the JSON structures, and highlights token status including expiration date, issued-at timestamps, and custom claims. Because debugging authentication tokens involves sensitive identifiers and credentials, this utility executes entirely client-side without logging or transmitting token contents to any remote server.

How to Use

  1. 1Paste your token: Copy your bearer token or raw JWT from an HTTP Authorization header, session cookie, or OAuth response into the left editor.
  2. 2Review Header & Payload: The parsed algorithm, token type, and decoded claims JSON appear immediately in the right pane.
  3. 3Check Expiration & Claims: Inspect standard claims: exp (expiration), iat (issued at), nbf (not before), iss (issuer), and aud (audience) to diagnose token rejections.
  4. 4Share or debug: Use the generated share link if you need to collaborate with a teammate (only URL query parameters are shared, no backend persistence).

Key Features

  • •Real-time syntax highlighting for Header, Payload, and Signature components
  • •Automatic calculation and display of token expiration (exp) and validity status
  • •RFC 7519 standard claim verification: sub, iss, aud, iat, nbf
  • •100% private in-browser decoding: secret keys and bearer tokens are never transmitted

Frequently Asked Questions

Is my JWT token sent to your backend server?

No. All decoding and parsing takes place entirely within your browser using client-side JavaScript. Your tokens, secrets, and authorization headers never touch our servers.

Does this tool verify the cryptographic signature?

This tool performs structural decoding and claim inspection. Because verifying signatures requires the server-side secret key or public certificate, signature validation should be conducted by your authorization server or backend gateway.

Why is my JWT being rejected by my backend API?

Common causes include an expired timestamp (exp), a clock skew issue before not-before (nbf), an audience mismatch (aud), or an unexpected signing algorithm (alg: HS256 vs RS256).

What is base64url encoding in JWT?

Base64url is a variant of Base64 where '+' is replaced by '-', '/' is replaced by '_', and trailing '=' padding characters are removed to make the token URL-safe.