Decode JWT headers and payloads, inspect exp and nbf claims, and copy token sections locally in your browser.
Paste a token to inspect it locally.
{
"alg": "HS256",
"typ": "JWT"
}{
"sub": "usr_8f3a2b1c",
"name": "Alex Chen",
"iat": 1746053200,
"exp": 1746056800,
"scope": "api:read"
}signature
Separates header, payload, and signature with readable JSON output.
Highlights expiration and not-before claims against your current browser time.
Clearly distinguishes inspection from cryptographic signature verification.
Token text is decoded locally without a server round trip.
Shows common header fields such as alg, typ, kid, and custom metadata.
Copy decoded JSON into tests, bug reports, or auth debugging notes.
No. It decodes and inspects JWT segments only. Signature verification requires a trusted secret or public key and should happen in your app or identity provider.
No. The token is parsed in your browser and is not sent to ZPTools servers.
The tool highlights exp and nbf timing, displays the algorithm from the header, and preserves every custom claim in the decoded payload.