JWT Decoder
See what is inside a JSON Web Token and when it expires. Check an HS256 signature with your secret.
Paste a token to read it.
How to use this tool
- Paste the tokenWith or without the word Bearer. Line breaks from logs are ignored.
- Read the claimsStandard claims are explained, and exp, iat and nbf are shown as dates in the time zone you choose.
- Verify, if you have the secretFor HS256, HS384 and HS512, paste the secret and press Verify. Without it, the signature is reported as unchecked.
What problem does this solve?
A JWT is three Base64url blocks that mean nothing at a glance, and pasting a live token into a site that sends it to a server is exactly what you should not do. This decoder reads it on your device, shows every claim with dates you can read, says whether it has expired, and checks the signature only when you give it the secret.
Who needs this?
- Developers debugging an Authorization header or a login flow
- Anyone checking why a session expired or which user a token belongs to
- Security reviewers looking for alg none or missing expiry
You might also need
FAQ
Is it safe to paste a real token here?
The token is decoded in your browser and never sent anywhere, logged or put in the page address. Still treat live tokens like passwords: anyone holding one can use it until it expires.
Does decoding a JWT prove it is genuine?
No. Anyone can write a token; only the signature proves who made it. The page says Signature not checked until you verify it with the secret, and warns when alg is none.
Which signatures can it verify?
HS256, HS384 and HS512, using a secret you paste (plain text or Base64). RS256, ES256 and other public-key algorithms need a public key and are not checked here.