JWT Decoder

Decode JSON Web Tokens to inspect header, payload, claims, and expiration. Your token never leaves this browser tab.

PASTE JWTthree Base64URL parts separated by dots

How a JWT works in five seconds

A JWT is three Base64URL strings joined by dots: header.payload.signature. The header and payload are JSON — anyone can decode and read them. The signature is computed by the server from header + "." + payload + secret, so any tampering invalidates it.

When a client sends the token back (typically in Authorization: Bearer ...), the server re-computes the signature and compares. If it matches, the payload can be trusted — but only until exp says it cannot.

Never put secrets in a JWT

The payload is base64 — not encrypted. If your token's payload contains a password, a credit card number, or any private data, your users can read it with this tool. Put only identifiers and authorisation claims in there.

Privacy first

Decoding runs entirely in this browser tab. No network call. The token never leaves your machine, so production credentials stay safe even when you are debugging.

Common questions

What is a JWT?
A JSON Web Token is a compact, signed credential used for stateless authentication. It has three Base64URL-encoded parts joined by dots: header (algorithm), payload (claims), and signature. The signature is verified by the server; the payload is plain JSON anyone can read.
Is this tool verifying the signature?
No. Signature verification requires the secret (HS256) or public key (RS256/ES256), neither of which should ever leave your server. This tool only decodes the header and payload so you can inspect what claims a token carries.
Are JWTs encrypted?
A standard JWT (JWS) is signed, not encrypted. The payload is Base64URL-encoded JSON that anyone with the token can read. If you need confidentiality, use JWE (JSON Web Encryption) — but you almost certainly do not, since JWTs are usually transmitted over HTTPS already.
My token is too short — only two parts. Why?
A two-part token (header.payload, no signature) is an unsigned JWT (alg: none). It is valid syntactically but unsafe in production — anyone can forge one. Most servers reject alg: none by default since the 2015 vulnerability disclosure.
What do the standard claims mean?
iss = issuer, sub = subject (usually user ID), aud = audience, exp = expiration time, nbf = not-before time, iat = issued-at, jti = JWT ID for revocation. All times are Unix seconds. Custom claims are anything else.
Is my token safe in this tool?
Yes. Decoding happens entirely in your browser. No network calls, no logging. You can paste production tokens without leaking anything. Just remember the token itself, if intercepted by someone else, lets them impersonate you until expiry.