JWT Decoder
Paste a JSON Web Token to read its header and payload, with iat, nbf and exp shown as real dates and a live expiry countdown. Decoding happens in your browser, so the token never leaves your machine.
What's inside a JWT
A JWT is three Base64URL strings joined by dots: header.payload.signature.
- Header: the signing algorithm (
alg, such as HS256 or RS256) and the token type. - Payload: the claims. Registered ones include
sub(who the token is about),iat(issued at),exp(expires) andnbf(not valid before), all in seconds since 1970. - Signature: proof the first two parts weren't changed, made with a secret or private key.
Decoding is not verifying
Anyone can decode a JWT: the payload is encoded, not encrypted. So never put passwords or other secrets in one. What makes a token trustworthy is the signature, and checking it needs the secret (HS256) or the public key (RS256, ES256).
That check belongs on your server, with a maintained library that also enforces exp, pins the expected alg and rejects alg: none. This page deliberately doesn't ask for your key.
Is it safe to paste a token here?
The decoding runs in your browser with atob and JSON.parse: nothing is uploaded, logged or stored. Even so, a live token is a password until it expires. Prefer pasting expired or test tokens, and revoke any production token you've shared somewhere you shouldn't have.