Paste a JSON Web Token to read its header and payload, with each standard claim explained and timestamps such as exp and iat shown as dates. The token is decoded locally and never sent anywhere or saved. This tool decodes only; it does not verify signatures.
Paste the token into Encoded token. A leading "Bearer " is removed for you.
Read the decoded Header and Payload, shown as formatted JSON.
Check Status to see whether the token is expired or not yet valid, and what the signing algorithm means.
Use the Claims table for each claim's meaning and the dates in your time zone and UTC.
The token is decoded in your browser and is never sent anywhere or saved. Still, treat live tokens like passwords and paste them only on a device you trust.
No. It only decodes. Anyone can create a token with any content, so don't trust the claims until your server has checked the signature with the right key.
A token with 5 parts is an encrypted JWE. Only its header is readable; the payload needs the decryption key.
Status shows "Expired" or "Expires" with a relative time, plus the token's lifetime when iat and exp are present. If there is no exp claim, the tool tells you the token never expires on its own.
The token is unsigned. Servers must reject it, and the tool flags it in red.