Inspect a JSON Web Token's header and payload, and check its expiry, without sending a live credential to anyone's server.

What a JWT actually is

A JWT is three base64url segments joined by dots: a header describing the algorithm, a payload of claims, and a signature. Decoding shows the first two. The signature is not verified here, and it cannot be without the key.

That distinction matters: decoding proves nothing about authenticity. A token can be decoded successfully and still be forged, expired, or signed with a key the issuer later rotated.

The claims worth checking

exp is the expiry as a Unix timestamp in seconds. nbf is the earliest time the token is valid. iat is when it was issued. aud identifies the intended audience, and iss the issuer.

A token with a valid signature but the wrong aud is a real vulnerability: a token minted for one service gets accepted by another. Checking exp and aud server-side is mandatory, and neither check can be skipped by trusting the client.

Why not paste tokens into a website

A JWT is a bearer credential. Anyone holding it can act as that user until it expires. Pasting one into an unknown decoder means handing a working session to whoever operates that site, and their logs.

There is no technical reason to send it: base64url decoding is a few lines of JavaScript. This tool runs entirely in the page, so the token stays where it is.

The alg none trap

Early JWT libraries accepted a token whose header declared alg none, meaning no signature, and treated it as valid. That let anyone forge tokens by editing the payload and setting alg to none.

Modern libraries reject none by default, and a server should pin the expected algorithm rather than reading it from the token header. If a service accepts the algorithm the client claims, it is still vulnerable.

Frequently asked questions

Does this verify the signature?
No. Verification needs the signing key or public key, which this tool never receives. Decoding only shows what the token claims.
Why does the payload look like garbage?
JWT segments use base64url, which replaces plus and slash with hyphen and underscore and drops padding. Standard Base64 decoders choke on that.
Is my token transmitted?
No. Decoding happens in the page and nothing is stored. Still, treat any token you paste anywhere as potentially exposed and prefer a short-lived one.