JWT Decoder

Decode JWT header and payload for inspection. Decode-only—does not verify signatures or authenticity.

How the JWT Decoder works

Paste a JSON Web Token to see its header and payload as formatted JSON. It only decodes: it does not verify the signature or check whether the token has expired.

  1. Paste the token into the input box. Use only the three-part string separated by dots, without a "Bearer " prefix.
  2. Click Decode JWT.
  3. Read the output: a JSON object with a "header" key and a "payload" key, indented for reading.
  4. Copy the result if you need it. Treat every claim as unverified.

How decoding works

A signed JWT has three parts separated by dots: header, payload and signature. The tool splits the token on the dots and requires exactly three parts. It decodes the header and payload from Base64URL (handling - and _ and missing = padding), reads them as UTF-8 text, and parses each as JSON. The signature part is ignored.

If something is wrong, the error names the problem and the part it is in: "Expected 3 segments separated by ".", found 5", "Invalid Base64URL in header", "Invalid UTF-8 in payload", or "Invalid JSON in payload".

Reading common claims

The header usually contains alg (the signing algorithm, such as HS256, RS256 or ES256) and typ ("JWT"). Common payload claims are iss (issuer), sub (subject, usually a user ID), aud (audience), exp (expiration time), nbf (not valid before), iat (issued at) and jti (token ID).

exp, nbf and iat are Unix timestamps in seconds and are shown as raw numbers. Paste them into the Epoch Converter to see the dates.

The decoded JSON is read with JavaScript numbers, so integers larger than 9,007,199,254,740,991 (for example a 19-digit numeric user ID) are rounded. When a header or payload contains one, a warning under the result lists the original digits.

Privacy

Decoding happens in your browser and the token is not sent anywhere. Even so, a JWT can be a live credential that grants access until it expires, so prefer test or expired tokens when you can.

Frequently asked questions

Why doesn't this tool verify the JWT signature?

Verifying a signature requires the secret key (for HS256) or the issuer's public key (for RS256 or ES256), which this tool does not ask for. Anyone can create a token with any payload, so always verify signatures on your server with a maintained JWT library before trusting the claims.

Is a JWT encrypted?

Usually not. Most JWTs are signed, not encrypted: the header and payload are only Base64URL-encoded, so anyone holding the token can read them. Do not put secrets in a JWT payload. Encrypted tokens (JWE) have five parts and are rejected by this decoder.

Does the decoder tell me if the token is expired?

No. It shows the exp claim as a number but does not compare it with the current time. Convert exp with the Epoch Converter; if that moment is in the past, the token has expired.

Why do I get "Invalid Base64URL in header"?

The first part of what you pasted is not valid Base64URL. The usual cause is a leading "Bearer " copied from an Authorization header, or stray quotes or spaces. Paste only the token itself, which typically starts with eyJ.

What does "Expected 3 segments" mean?

The input did not have exactly two dots. The token may have been cut off while copying, or it may be an encrypted JWE token, which has five parts and cannot be decoded without its key.

Is it safe to paste my JWT here?

The tool decodes in your browser and does not transmit the token. As a general habit, avoid pasting live production tokens into any website, because a leaked token can be used until it expires.

Similar Developer tools

3 related