What the JWT Decoder does
The JWT Decoder shows what is inside a JSON Web Token. Paste a token and see its header, which says how it was signed, and its payload, which holds claims such as the user ID, roles and expiry. Time claims are turned into readable dates, and the tool warns you if the token has already expired. Tokens are decoded in your browser and never sent anywhere.
How to use it
- Paste the token into the Token box. A
Bearerprefix is removed for you. - Read the decoded header and payload on the right.
- Check the Expires, Issued and Not valid before lines, shown as dates.
- Copy the decoded JSON if you need it for a bug report or documentation.
Example
Your app suddenly logs users out. Copy the token from the browser’s storage and paste it here: the payload shows "exp": 1760003600, which the decoder displays as 9 October 2025, and the status line says the token has expired. The problem is token renewal, not the login form.
Decoding is not verifying
A JWT is three Base64URL parts separated by dots: header, payload and signature. Anyone can read the first two, which is why tokens should never contain secrets. This tool decodes them but does not check the signature, because that needs the secret or public key used to sign the token. Your server must always verify the signature before trusting anything in the payload.
Tokens with five parts are encrypted (JWE). Their payload cannot be read without the key, and the decoder tells you so.
Questions people ask
Is it safe to paste a real token?
The token stays in your browser, so this page does not leak it. Still treat live tokens like passwords and avoid sharing screenshots of them.
Why does it say the token expired when it still works?
Your device clock may be off, or the server may allow some leeway after the expiry time.
What are iat, exp and nbf?
Issued at, expires at and not valid before. All three are Unix timestamps in seconds.
Can it create or sign tokens?
No. It only reads them.