How to use JWT Decoder and Claims Inspector
- Paste a three-section token into JSON Web Token.
- Read the labelled header and payload fields. Open Technical details if you need the decoded JSON.
- The decoded claims update as you edit the token. Read the signature-verification warning and clear the token when you finish.
Example: JWT Decoder and Claims Inspector
Read the example subject and issuer from a sample token with no exp claim.
Options
- JSON Web Token
- Paste a signed three-section token. Whitespace is ignored, so a token copied across two lines still reads. The decoder reads the token in this browser and makes no network request of its own.
Supported inputs and limits
- One token up to 20,000 characters.
- The tool reads three-section values; five sections are refused as encrypted tokens, and other counts are reported.
- Sections must be base64url, and the first two must decode to JSON objects.
- The signature is labeled present or absent and remains unverified: no key is collected.
- Expiry comparisons use the device clock and do not establish whether a server will accept the token.
More details
UTC/local labels describe stored claims.
The tool does not store or log submitted tokens.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
The claims worth reading first
The registered claims tell you who issued the token, who it is for and when it stops being valid. iss names the issuer, aud names the service the token is meant for, exp is the expiry as a Unix timestamp in seconds, nbf is the time it becomes valid, iat is when it was issued, and jti identifies the token itself. A scope claim carries permissions, and the server still has to enforce them.
Sources
Questions about JWT Decoder and Claims Inspector
Does this tool verify the signature?
No. Checking a signature needs the issuer's key, and this page never asks for one. The output says the signature is unverified and shows an approximate size when that section is not empty.
Can I trust the claims I read here?
Treat them as text the token carries, not as facts. The header and payload need no key to write, so anyone can build a payload with a tidy issuer and a future expiry. Only a party holding the issuer's key and applying the issuer's rules can confirm a token.
Why does it say the token is expired?
The exp claim is compared with your device clock, so a wrong clock gives a wrong verdict. A token can also look current and still be refused for an audience mismatch or a revocation.
Why was my token refused?
Five sections means an encrypted token, which is not read here. Any other count means a copy problem, and the first two sections must each be base64url text that decodes to a JSON object.