How to use this tool
- Enter jwt token.
- Select Update result to view the result.
- Check the method and assumptions below before using the result.
Input reference and sample values
Use the units and choices shown for each field. Sample values are provided for practice, not as recommendations.
| Input | Format and units | Sample |
|---|---|---|
| JWT token | Keep the structure and separators shown in the sample. Line breaks are retained in this input. | eyJhbGciOiJub25lIn0.eyJzdWIiOiJleGFtcGxlIn0. |
Result for these sample inputs
{
"header": {
"alg": "none"
},
"payload": {
"sub": "example"
}
}UNVERIFIED CONTENT: these claims can be forged. This tool does not verify signatures, issuer, audience, expiration or authorization.
Select Try the example in the form to load these values and calculate them again. This replaces the current form inputs. Compare the result with the method and worked explanation below.
The method, explained
Split the compact token into header, payload and signature sections. Decode the first two base64url sections as UTF-8 JSON. No key lookup or signature verification is performed.
Using jwt token = eyJhbGciOiJub25lIn0.eyJzdWIiOiJleGFtcGxlIn0., the result is { "header": { "alg": "none" }, "payload": { "sub": "example" } }. Change these example inputs to match your task; use the method above to check each step.
What to keep in mind
Only three-part compact JWTs are supported. Tokens may contain sensitive data; processing stays local and the input is not included in a share URL.
Common questions
Does a decoded token prove a user is authenticated?
No. Anyone can construct a token payload. A trusted authentication system must verify the signature and all required claims before relying on it.
Is the token sent to a server?
No. Decoding runs locally without fetching a signing key or contacting the issuer.
Methodology maintained by ClarityKit. How these tools are built and checked.