Free · works in the browser
JWT decoder: online JSON Web Token analysis
Paste a token: we’ll show the header and payload and the iat, nbf and exp times in plain language, and verify the signature with your secret or public key.
- Claims and expiry in plain language
- HS, RS, PS, ES signatures
- The token isn’t sent to the server
We’ll show the header and payload and the iat, nbf and exp times in plain language, and verify the signature with your key: a secret for HS, a PEM public key or JWK for RS, PS and ES
What a JWT is
JWT (JSON Web Token) is a compact token format for authorization and data exchange between services. It consists of three parts separated by dots: header.payload.signature. The first two parts are JSON encoded in Base64URL, so they’re easy to read. The third is the signature, which confirms the token hasn’t been forged.
- Header: the signature algorithm (
alg) and token type (typ), sometimes the key identifierkid. - Payload: the payload: standard fields (
iss,sub,aud,exp,iat,nbf,jti) and any custom data. - Signature: the signature over the header and payload with the issuer’s secret or private key.
What the decoder shows
- Header and Payload: decoded JSON with highlighting.
- Claims breakdown: readable names of fields and values.
- Validity period —
exp,nbf,iatas a date and time, plus the status: the token is valid, expired or not yet valid. - Highlighting of token parts by color, as is customary for JWT.
- Privacy: the token is processed only in the browser and isn’t sent anywhere.
Is the signature verified
No. This is a decoder: it shows the token’s contents but doesn’t verify the cryptographic signature. Verifying a signature needs the issuer’s key or certificate (a secret for HMAC or a public key for RSA/ECDSA/GOST), and the token itself shouldn’t end up on third-party sites. That’s why decoding and verification are usually kept apart. If you work with GOST signatures, use our GOST electronic signature and verification service.
Questions
Frequently asked questions about JWT
Didn’t find the answer? Write to us; an expert replies within 15 minutes on average. About CryptoPro and signing in the account, see the knowledge base.
Is my token sent anywhere?
No. JWT parsing runs in JavaScript entirely in your browser: the token isn’t sent to the server or saved anywhere. Still, don’t paste production tokens into unverified sites: they give access to your data.
Can a JWT be “decrypted”?
A regular JWT isn’t encrypted but encoded in Base64URL, so its contents (header and payload) can always be read without a key. Secrecy comes not from encryption but from the signature: the data can’t be changed unnoticed. There’s also an encrypted variant (JWE), whose contents can’t be read without the key.
How do I tell that a token has expired?
The field exp is the expiry time (Unix time in seconds). The decoder converts it to a date and shows the status right away: “valid”, “expired” or “not yet valid” (for the field nbf).
Does the tool verify the signature?
No, it only decodes. Signature verification requires the issuer’s key and is done separately, so as not to pass secrets and tokens to third-party services.
What if the token won’t parse?
Make sure it’s really a JWT: three parts separated by dots, the first two being Base64URL of JSON. SAML, opaque tokens and simple API keys don’t fit this format.
Free tools
More for signatures
A certificate in half a minute. Marking in Truemark is just as simple
Sign up and get your first codes in 5 minutes. 7 days of full access free, no card required.
Or leave a request
We’ll answer about volumes, pricing and getting started. Leave your phone or email and your question in the request form.