Times, not timestamps
exp, nbf and iat are seconds since 1970 in UTC, with no timezone attached. They are shown as KST, UTC and your own clock, next to how long is left, so a token that expired four minutes ago does not look valid.
Pikkola JWT, tool No. 32
Paste a token and its three parts fall apart side by side, with exp and iat turned into times you can read. Check an HS256 secret or an RS256 public key against the signature, and see what the payload quietly says about the person it belongs to. All of it runs in the page.
The decoder
The header, the payload and the signature are drawn in three colours, in the token and in the panels below it. Claims of time are read as moments, not as eight digit numbers, and the notes underneath say what a server ought to be checking.
This payload has no exp, nbf or iat claim.
| Claim | KST (UTC+9) | UTC | Your time | From now |
|---|
Nothing in the header or the payload stands out. What the claims say is still only what the issuer wrote.
The signature
A signature is a rectangle of bytes, so the only way to know it is right is to compute it. WebCrypto in this tab does that with a secret for HS256, or with a public key for RS256 and ES256. The key stays in the field you typed it into.
Read from the header aboveno token yet
Type the secret exactly as the issuer uses it. A demo secret is enough while you try the page; a production one is a credential.
Signed here with HMAC, dropped into the decoder above.
The demo secret pikkola-demo is written here on purpose. It is not a secret, and must never sign anything real.
Three steps, all of them local.
A match means the token was signed with this key. It does not mean the issuer can be trusted, that the claims are true, or that the token has not been replayed somewhere else.
The claims
Values on the left come from the token above. A claim that is missing says so, which is often the more interesting answer.
| Claim | In this token | What it means |
|---|---|---|
| iss | not present | Issuer |
| sub | not present | Subject |
| aud | not present | Audience |
| exp | not present | Expiration time |
| nbf | not present | Not before |
| iat | not present | Issued at |
| jti | not present | JWT ID |
A JWT is signed, not encrypted. Everything in the payload is readable by anyone holding the token, so a user's name, their email address or an internal role is visible in a proxy log, a browser history and a screenshot.
Why this one
exp, nbf and iat are seconds since 1970 in UTC, with no timezone attached. They are shown as KST, UTC and your own clock, next to how long is left, so a token that expired four minutes ago does not look valid.
Many decoders only show you the payload and call it verified because the text looked fine. This one imports the key with WebCrypto and compares the signature, and it says plainly when alg none means there is nothing to compare.
No exp, a missing aud, an HS256 secret, an email address sitting in the payload: each one is named with the reason it matters, in the place where you are looking at the token.
The token, the secret and the public key live in the fields above and in the memory of the page. The content security policy sets connect-src to none, so the browser will not let this page call anywhere, even by mistake. Reload and everything is gone; two preferences, the theme and the language, are kept in local storage.
Read the privacy noteQuestions
No. A signed JWT is encoded and signed, not encrypted. Anyone holding the token can read the header and the payload with a decoder like this one. Only a JWE, which has five parts instead of three, carries an encrypted payload. Treat a JWT as a postcard with a seal on the back.
That the header and the payload were signed with a particular key, and have not changed since. It does not prove that the issuer is honest, that the claims are true, or that the token has not been replayed. Those are the receiving server's checks.
exp, nbf and iat are NumericDate values: seconds since 1 January 1970 UTC, with no timezone. This page converts them to KST, UTC and your local time, and says how long is left or how long ago they passed.
Yes. A signature is checked with the public key, which the issuer publishes as a JWKS endpoint or a PEM file. The private key never leaves the issuer. Paste the public key in PEM or JWK form and the check runs in this tab.
A token with alg none has no signature at all. If a server trusts the header to choose how it verifies, an attacker can rewrite the payload, set alg to none and drop the signature. A server should accept a fixed list of algorithms and reject none outright.
No. Decoding and verification are JavaScript functions on this page, and the content security policy sets connect-src to none, so the browser refuses every outbound request. There is no server side to this tool.
A token is a credential while it is valid. This page sends it nowhere, but a token pasted into any web page is one accident away from a log or a shared screen. Where you can, use a test token, or one that has already expired.
HS256, HS384 and HS512 with a shared secret; RS256, RS384 and RS512 with an RSA public key; PS256, PS384 and PS512 with RSA PSS; and ES256, ES384 and ES512 with an EC public key. EdDSA is checked where the browser supports it. Decoding works for every algorithm, including ones this page cannot verify.