Skip to content
ScanAnt

JWT decoder online

Paste a JSON Web Token to read its header and payload, see when it was issued and when it expires, and get warnings about common problems. The token is decoded in your browser and never leaves it.

Runs in your browser
Decoded in your browser. Nothing is sent or stored.

How it works and what to look for

What a JWT contains

A JSON Web Token is three base64url parts separated by dots: a header (algorithm and type), a payload (claims such as the user id, role and expiry) and a signature. The first two parts are only encoded, not encrypted. Anyone who holds the token can read them, which is exactly what this tool does.

Decoding is not verifying

Reading a token proves nothing about whether it is genuine. To verify it, a server checks the signature with a key. For HS256 that key is a shared secret, and a short or guessable secret can be cracked offline, which this page cannot test. Never trust claims you have not verified on the server.

Warnings worth acting on

An algorithm of none means the token is unsigned and must be rejected. A missing exp claim means the token never expires, and very long lifetimes widen the window if one leaks. Claims named like password, secret or api_key should not be in a token at all, because the payload is readable by everyone who sees it.

Where to store and send tokens

Keep access tokens short-lived and rotate refresh tokens. Prefer an HttpOnly cookie over localStorage, since any script injected into the page can read localStorage. Send tokens only over HTTPS and never put them in URLs, where they end up in logs and browser history.

Questions

Is it safe to paste my JWT here?

The decoding runs in your browser with JavaScript and the token is never sent to any server or saved. Still, treat a live production token like a password: paste only tokens you are comfortable exposing, or expired and test ones.

Can this tool verify the signature?

No. Verifying needs the secret or public key, and it should happen on your server. This page only decodes and flags suspicious details.

Why does my token show as expired?

The exp claim is a Unix timestamp in seconds. If it is in the past, the token should be rejected and the client has to sign in or refresh again.

Are JWTs encrypted?

A normal signed JWT (JWS) is not encrypted, only encoded. Do not store secrets or personal data in the payload.

What is alg none?

It marks a token without a signature. A server that accepts it lets anyone forge tokens, so libraries must reject it unless explicitly configured otherwise.

Related security checks

Scan your whole site for free

One tool checks one thing. The free scan reads your public pages the way a visitor sees them and reports headers, exposed keys, outdated libraries and more. No signup.

Scan your whole site free →