PRACTICAL GUIDE

Read JWT Claims Without Mistaking Decoding for Verification

Inspect a three-part JWT’s header, payload and UTC claim dates without uploading the token.

Recognize the three parts

A compact signed JWT normally contains header, payload and signature segments separated by dots. The first two segments can be read without a signing key. Encrypted tokens have a different structure and cannot be read by this decoder.

Treat every claim as untrusted

The decoder deliberately marks the signature as unverified. A readable subject, role or expiration is not evidence that a server signed it. Authentication code must verify the token using trusted keys and the expected algorithm, issuer and audience.

Read dates in UTC

NumericDate claims use seconds since the Unix epoch. This tool displays supported iat, nbf and exp numbers as UTC timestamps. It does not apply a clock-skew allowance or decide whether your service should accept the token.

Use test data while debugging

Live access tokens can authorize account actions. Avoid putting them into screenshots, shared chats or logs. This page processes text locally, but browser extensions and any enabled page scripts are another reason to prefer redacted test data or offline tooling.

Put it into practice