Skip to content

Decode a JWT

Decode a JSON Web Token's (JWT) header and payload to inspect its content, directly in your browser.

Processed on your device. Nothing is sent to any server.
Decoding does not mean verifying. This tool shows the token's content, but does not check the signature or its cryptographic validity.

A JWT has three dot-separated parts: header, payload and signature. This tool decodes the first two (which are Base64URL-encoded, not encrypted) to show their content as readable JSON.

Use cases

  • Debugging an authentication token during development.
  • Checking what claims a JWT contains.
  • Verifying a token's expiration date.

How it works

  1. 1

    Paste the token

    Copy the full JWT (with its three dot-separated parts).

  2. 2

    Review the content

    The header and payload are shown decoded and formatted.

Technical details

  • It splits the token at the dots into header, payload and signature, and decodes the first two from Base64URL to JSON. An encrypted JWT (JWE, five parts) can't be read this way.
  • It doesn't verify the signature or expiry: anyone can craft a token that looks like this. Checking validity requires verifying the signature with the issuer's key.
  • Standard dates (exp, iat, nbf) appear as seconds since 1970 (Unix time); convert them with the Unix timestamp converter to see the real date.
  • The token never leaves the browser, but a session JWT is like a temporary password: don't paste it into tools whose handling you don't know.

Frequently asked questions

Does this tool verify whether the token is authentic?

No. Decoding only shows the token's content; it does not check the signature or whether the token was issued by a trusted source. For that you need to verify the signature with the corresponding secret or public key.

Is a JWT's content encrypted?

No, a standard JWT's (JWS) header and payload are only Base64URL-encoded, not encrypted: anyone can read them without needing any key.

← Developer