JWT Decoder

JWT Decoder

This tool only decodes - it does not and cannot verify signatures. Decoding just reads what's already inside the token (it's plain base64url, not encryption). Verifying a signature is a different operation entirely - it requires the secret or public key the token was signed with, and that key lives only on the issuing server. It never reaches a browser-based tool like this one, so never treat a decoded payload as "proven authentic" without server-side verification.

What Is a JWT?

A JSON Web Token (JWT) is a compact, URL-safe way to represent claims (pieces of information) that need to be passed between two parties, most commonly used for authentication and authorization on the web. A JWT is a single string made of three parts separated by dots (.): header.payload.signature.

  • Header - a small JSON object describing the token type and the signing algorithm used, e.g. {"alg":"HS256","typ":"JWT"}.
  • Payload - a JSON object holding the actual claims: who the token is about, when it was issued, when it expires, and any custom data the issuer wants to include.
  • Signature - a cryptographic signature computed over the header and payload using a secret or private key, letting the server confirm the token hasn't been altered since it was issued.

Each of the three parts is encoded separately using base64url (a URL-safe variant of base64 that replaces + with - and / with _, and typically omits trailing = padding) before being joined with dots. That's why a JWT is plain text you can decode - the header and payload are never encrypted, only encoded.

Common JWT Claims Explained

sub (Subject)Identifies the principal the token is about - typically a user ID or username the token was issued for.
iat (Issued At)A Unix timestamp (seconds since 1970) marking exactly when the token was created by the issuer.
exp (Expiration)A Unix timestamp after which the token must be rejected, even if the signature is still valid - limits how long a stolen token stays useful. This tool flags an expired token with a red "Expired" badge next to the decoded exp value.
nbf (Not Before)A Unix timestamp before which the token must NOT be accepted yet, even if everything else checks out - used to issue a token that only becomes valid at a future time.
aud (Audience)Identifies the intended recipient(s) of the token, such as an API or application - services should reject tokens meant for someone else.

Decoding vs. Verifying: Why It Matters

It's easy to conflate "I can read this token" with "this token is genuine" - but they are two completely different operations. Decoding is simply reversing the base64url encoding to reveal the JSON that was already sitting inside the token in plain sight; anyone, including an attacker, can do this with no special knowledge at all. Verifying is cryptographically proving the signature was produced by the real issuer and that the header/payload haven't been tampered with since - and that requires the secret key (for symmetric algorithms like HS256) or the issuer's public key (for asymmetric algorithms like RS256), neither of which this tool, or any purely client-side tool, has or should ever have access to.

In practice, that means this JWT Decoder is safe to use for debugging and inspecting what claims a token carries, but a decoded payload should never be treated as trusted or authentic input for a security decision - that check must happen on the server, which holds the signing key.

Frequently Asked Questions

Can this tool verify my JWT's signature?

No — verifying a signature requires the secret or public key, which this browser-only tool never has access to; it only decodes and displays what's already inside the token.

Does this tool send my JWT to a server?

No. Everything is decoded entirely in your browser using JavaScript - your token, including any sensitive claims inside it, never leaves your device.

Why can I read the payload without any password?

Because the header and payload are only base64url-encoded, not encrypted - anyone can decode them, which is exactly what this tool does. Only the signature requires a secret key, and that's what makes the token trustworthy, not the payload itself. JWTs should never contain secret data in the payload.