About this decoder
Pikkola, tool 32. Written 19 November 2026
A decoder is only useful when it tells you what it cannot tell you.
Why another one
A token shows up when something else has already gone wrong: a request came back 401, a webhook signature was rejected, a session ended an hour early. What you need in that moment is not a wall of settings but the payload in front of you, the times in a form you can compare with a clock, and a straight answer about the signature.
Three parts, one line
A signed JWT is three base64url strings joined by dots. The header says which algorithm signed it. The payload is a JSON object of claims about somebody. The signature is the result of running that algorithm over the first two parts, exactly as they appear, with a key. Because base64url uses only characters that survive a URL, the whole thing can sit in a header or a query string without escaping.
Reading is not trusting
Anyone can write a JWT. The only thing that separates a token from a text file is whether the signature checks out against a key you decided to trust. So the page keeps those two jobs apart: the panels above show what the token says, and the signature panel shows only what can be computed. A token that decodes perfectly and fails the check is the common case, not an edge case.
The three parts get a colour each, in the ribbon and in the panels, because the most frequent mistake with a token is looking at the payload while believing you looked at the signature.
Times in three clocks
exp, nbf and iat are seconds since 1970 in UTC, with no timezone attached. Written down, they look like any other eight digit number, and a token that expired four minutes ago looks exactly like one that expires tomorrow. They are shown as KST, UTC and your own clock, with how long is left or how long ago, and a small bar places now between the issue and the expiry.
alg none, and the other notes
The header is part of the token, and a server that reads the algorithm out of the header and then trusts it can be walked backwards: rewrite the payload, set alg to none, drop the signature. The page names that case first, then the smaller ones: no exp, no aud, an HS256 secret whose strength cannot be judged from here, an email address sitting in plain view.
What it does not do
It does not decide that a token is valid. A matching signature means the key is right and nothing changed after signing; it says nothing about whether the issuer is honest or the claims are true. It does not fetch a JWKS: there is no network call from this page at all, by policy, so the key has to be pasted. It does not handle JWE, the five part encrypted form. It does not generate keys, and the demo secret is a demo secret.
Privacy
A token is a credential while it is valid, so it matters where it goes. Here it stays in the textarea, in the memory of the page, and nowhere else: the content security policy sets connect-src 'none', which tells the browser to refuse every outbound request from this page. There is no analytics, no font service and no upload. The two settings kept between visits are the theme and the language.
For the curious
The parts are exposed as window.PikkolaJWT, so a result can be checked from the console: PikkolaJWT.parseToken(PikkolaJWT.state.parsed.token). No framework, no build step, one script.
Say something
A bug report is most useful with the token that failed, or a stripped version of it, and what you expected. Write to [email protected].