← Every block

JWT Decoder

Decode a JSON Web Token: header, claims and expiry. The token stays in your browser.

Try one

Need to chain this with something else? Open in bode →

About JWT Decode

Three parts, separated by dots

A JWT is header.payload.signature. The first two are JSON, Base64url-encoded — which is why a token is readable by anyone who has it, no key required. The third is a signature over the first two.

The header says how it was signed (alg) and often which key was used (kid). The payload holds the claims.

Decoding is not verifying

Reading a token tells you what it says, not whether it is true. Anyone can mint one whose payload claims "admin": true, and it will decode perfectly here.

Checking needs the key. Paste it — an HMAC secret for HS256, a PEM or JWK public key for RS256, PS256 and ES256 — and the badge says whether the signature holds. Without one it reads not verified, which is an answer rather than a missing one.

Verification in a browser tells you the token is intact. Whether to act on it is still the server's question: it also has to check the issuer, the audience and the expiry against what it expects.

exp, iat and nbf are in seconds

The time claims are seconds since the Unix epoch, while most languages count milliseconds. A token that looks like it expires in 1970 is usually this mistake.

exp is expiry, iat is when it was issued, and nbf is the earliest it may be used. This block shows them as timestamps and tells you whether exp has passed.

Common questions

Is it safe to paste a token here?
The decoding happens in your browser and the token is never sent anywhere or saved. Treat any token you paste into any tool as one to rotate if it is still live and valuable — that is good practice regardless of where you paste it.
Can you check the signature?
Yes, with the key. HS256/384/512 take the shared secret; RS, PS and ES algorithms take a public key as PEM or JWK. It is checked in your browser with WebCrypto, and the key is held for the session only — never saved or shared.
What is the kid in the header?
A key id. It tells the verifier which of several published keys signed the token, which is how providers rotate keys without invalidating everything at once.