Format Code Now
/

JWT Decode

ED-35

Paste a JSON Web Token to read its header and payload as formatted JSON, with the dates in iat, nbf and exp turned into readable times. The signature is not verified.

Runs in your browser. Nothing is uploaded.

JWT (a Bearer prefix is fine)

Decoded

How to use it

  1. Paste the token. A leading "Bearer " is removed.
  2. Click Decode token for header, payload, times and signature together.
  3. Use Header only or Payload only for one part as JSON, or Check expiry for a one-line answer.
  4. Copy the result.

What is inside a JWT

A JWT has three Base64URL parts separated by dots: a header (for example the algorithm), a payload (claims such as sub, iat and exp) and a signature. Decoding the first two parts needs no key, which is why a token must never carry secrets. This tool decodes them locally, prints each as formatted JSON and converts the numeric dates to UTC times with a relative description.

What this does not prove

Decoding is not verifying. The signature is not checked here, because that needs the secret or public key, so a decoded token says nothing about who created it or whether it was altered. Check expiry compares the exp claim to the clock on your device, which may be wrong. Encrypted tokens (JWE) have a different structure and cannot be decoded. Claims are displayed as written and are not interpreted.

Error messages and what to do

MessageWhat it meansFix
A JWT has 2 or 3 parts separated by dotsThe text does not have the header.payload.signature shape.Paste the complete token, without extra words or line breaks.
The header (first part) is not valid Base64URL-encoded JSONThe first part does not decode to JSON.Check that the token was copied completely.
The payload (second part) is not valid Base64URL-encoded JSONThe second part does not decode to JSON.Check for a truncated or altered token.

Questions people ask

How do I decode a JWT?

Paste the token into the box and click Decode token. The first two dot-separated parts are Base64URL-decoded and shown as JSON. You do not need a secret key to read them, since only the signature depends on one.

Is it safe to paste a JWT here?

The decoding runs in your browser and the token is not sent anywhere. Still, treat live tokens like passwords: anyone who holds a valid token can use it, so prefer expired or test tokens when you can.

How can I tell if a JWT has expired?

Click Check expiry. The tool reads the exp claim, a Unix time in seconds, and compares it with the current time on your device. A token with no exp claim has no expiry in its payload, although the server may still limit it.

Does this verify the signature?

No. Verification needs the secret for HMAC algorithms or the public key for RSA and ECDSA, and this page does not take keys. A decoded payload can be forged by anyone, so do not trust it without verifying.

Why does it say the payload is not valid JSON?

The second part did not decode to JSON. That happens when the token is cut off, contains extra characters, or is not a JWT at all. Encrypted JWE tokens have five parts and show the same kind of error.

About this tool

Splits the token at the dots and decodes the first two parts from Base64URL into JSON. Header only and Payload only print one part as formatted JSON. Check expiry reads the exp, nbf and iat claims and compares exp with the clock of your device. The signature is not verified, because that needs the secret or public key, so a decoded token proves nothing about who issued it. Encrypted tokens (JWE) cannot be read, and claims are shown as written, not interpreted. The sample is an unsigned example, not a real credential.

Format Code Now: free, no ads, no accounts. Your input stays in your browser.