JWT Inspector

The JWT Inspector lays out a token’s claims in a readable table, expands timestamp claims into dates, and warns when a token is expired or not yet valid. It is for developers debugging authentication who want claims in a clear, annotated form.

Raw JWT claims are terse and timestamps are unreadable epochs. Inspecting them locally turns the token into an annotated table without sending the token anywhere.

1. Paste the JWT you want to inspect.
2. The claims appear in a table, with timestamps expanded to dates.
3. Check the validity warnings for expiry or not-yet-valid status.
4. Review each claim to confirm the token is as expected.

• Claims shown in a readable table
• Timestamp claims expanded to dates
• Expiry and not-yet-valid warnings
• Runs locally — JWT Inspector

• Debugging why a token is being rejected as expired
• Confirming the audience and issuer claims of a token
• Reading human-readable dates for issued-at and expiry
• Inspecting scopes granted by an identity provider

• Always validate a token’s signature server-side; this tool is for reading, not verifying.
• Check both expiry and not-before when a token behaves unexpectedly.
• Treat any pasted token as a live secret and avoid sharing it.

• Assuming inspection verifies the token; it reads claims but does not check the signature.
• Overlooking the not-before claim, which can make a valid-looking token unusable yet.
• Trusting claims from an unverified token in application logic.