JWT Decoder

JWT Decoder

Paste a JSON Web Token (JWT) to decode its header and payload and inspect the claims inside.

Important: this tool only decodes the token — it does not verify the signature. A decoded token is not proof it is valid or trustworthy. Verifying a signature requires the secret key (or public key), which this tool never asks for.

Header


    

Payload


    

Signature

Decoding happens locally in your browser — your token is never sent to a server. Never paste a real production token with sensitive data into any online tool you do not trust.

About the JWT Decoder

Decodes a JSON Web Token (JWT) into readable JSON, showing its header (signing algorithm and token type), payload (claims such as user ID, issuer, and expiry), and the raw signature segment.

How to use

  1. Paste the full JWT — three Base64URL segments joined by dots (`header.payload.signature`) — into the input box.
  2. The tool splits the token at the dots and Base64URL-decodes the first two segments into formatted JSON.
  3. Read the header and payload claims, and check whether the token's expiry (`exp`) claim has passed.

Key features

  • Instantly reveals what a token contains for debugging login and API issues, including standard claims (`sub`, `iss`, `aud`, `iat`, `exp`) and custom claims.
  • Decoding runs in the browser, so the token is never sent to a server — important because a real token is a secret until it expires.

Frequently asked questions

Does decoding verify the token?

No. Decoding only reads the contents; verifying the signature needs the issuer's secret (HS256) or public key (RS256/ES256).

Is the payload encrypted?

No. The payload is only Base64URL-encoded, so anyone holding the token can read it — never put sensitive data in a JWT.

What if the token has more than three parts?

A token with five parts is a JWE (encrypted) token, which a plain JWT decoder cannot read.

Free to use, no signup needed. This tool runs entirely in your browser — your data never leaves your device.