Free online tool

Decode a JWT header and payload

Inspect the Base64URL-encoded header and payload fields of a JSON Web Token. Decoding only displays token contents; it does not verify the signature or trust the claims.

Quick answer

Quick answer

A JSON Web Token has three parts, header, payload and signature, and this tool decodes the first two into readable JSON in your browser. It shows claims such as subject, issuer, audience, roles and expiry time for debugging login flows. Decoding is not verification: it does not check the signature, so never trust claims without verifying them properly.

Open the interactive JWT Decoder

The interactive tool loads in the page. Enable JavaScript to enter data, process content, and download results.

About this tool

About the JWT Decoder

Inspect the Base64URL-encoded header and payload fields of a JSON Web Token. Decoding only displays token contents; it does not verify the signature or trust the claims.

Detailed guide

How to get useful results from JWT Decoder

Decode JSON Web Tokens for debugging

JSON Web Tokens, or JWTs, are widely used for authentication and authorization in web apps, mobile apps, and APIs. Identity providers such as Auth0, Okta, Firebase, Microsoft Entra ID, and many custom backends issue JWTs containing user claims and session details. This free online JWT decoder splits a compact token and decodes its Base64URL header and payload into readable JSON. Developers and QA engineers worldwide use it to inspect claims such as subject, issuer, audience, roles, and expiration time while debugging login flows. Decoding runs locally in your browser without any token submission endpoint.

Decoding is not verification

A JWT has three parts: header, payload, and signature. Anyone can decode the header and payload because they are only encoded, not encrypted. Decoding does not prove that the token is genuine or unmodified. Applications must verify the signature with the correct secret or public key, and check claims such as exp for expiry, nbf for not-before time, iss for issuer, and aud for audience before trusting the token. Never make security decisions based on decoded claims alone, and never place sensitive personal data in a JWT payload.

Handling tokens safely

Treat access tokens and refresh tokens like passwords. Avoid pasting live production tokens into any online tool when you can use test or expired tokens instead, and never share tokens in chat, tickets, or screenshots. Timestamps in claims such as exp and iat are Unix epoch seconds; use the Epoch Timestamp tool to convert them into a readable date. If a token fails to decode, check that it contains three dot-separated segments and has not been truncated or wrapped across lines when copying it from logs or headers.

Decoded claims also help explain authorization problems. If a user cannot access a feature, check whether the expected role, scope, or audience claim is present and whether the token has expired. Comparing a working token with a failing one often reveals the issue quickly during integration with identity providers or third-party APIs.

Quick guide

How to use this tool

  1. 01Paste a JWT into the decoder.
  2. 02Inspect the decoded header and payload.
  3. 03Do not treat decoded claims as verified authentication.

Capabilities

Features and supported formats

  • Parses header and payload fields.
  • Runs locally without a token submission endpoint.
  • Clearly separates decoding from signature verification.

Supported formats

Input: compact JWT text. Output: decoded JSON header and payload.

Answers

Frequently asked questions

Does decoding verify a JWT signature?

No. The tool only decodes encoded segments. It does not verify a signature, check token expiry, or establish that the claims are authentic.

Should I paste a production token here?

Avoid sharing active credentials unnecessarily. Treat token contents as sensitive even when decoding is performed in the browser.

What is inside a JWT?

A JWT contains a header describing the algorithm, a payload with claims such as user ID and expiry, and a signature used to verify authenticity.

How do I check when a JWT expires?

Look at the exp claim in the decoded payload. It is a Unix timestamp in seconds, which you can convert with the Epoch Timestamp tool.