Debug an access token
Inspect token claims while troubleshooting login sessions or API authorization.
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkJ1aWxkT25MYWJzIiwiaWF0IjoxNzEwMDAwMDAwLCJleHAiOjE3MTAwMDM2MDB9.signatureSecurity
Decode JWT headers and payloads locally to debug auth flows without exposing tokens.
This tool runs locally in your browser. Your input is not sent to a backend or paid API.
Decode JWT headers and payloads locally. Signature verification is not performed.
How to use
Follow this workflow to complete the task locally without leaving the page.
Paste a JWT into the token input.
Click Decode JWT to parse the header and payload.
Review the decoded JSON and common claims such as issuer, subject, and expiration.
Remember that decoding does not verify the token signature.
Examples
Use these examples to understand common workflows and expected input formats.
Inspect token claims while troubleshooting login sessions or API authorization.
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkJ1aWxkT25MYWJzIiwiaWF0IjoxNzEwMDAwMDAwLCJleHAiOjE3MTAwMDM2MDB9.signatureDecode payload timestamps to confirm whether a token is expired or issued unexpectedly.
Inspect exp, iat, nbf, iss, aud, and sub fields.FAQ
Answers to common questions about behavior, privacy, and practical usage.
No. It decodes the JWT header and payload so you can inspect claims. It does not verify signatures or prove that a token is trusted.
Decoding runs locally in your browser. Still, avoid sharing production secrets or tokens in screenshots, chat logs, or public issue trackers.
JWT claims such as exp, iat, and nbf commonly use Unix seconds. The decoder converts those fields to readable dates when possible.
The tool decodes the first two JWT segments: the header and payload. The third segment is the signature and is shown but not validated.