Claim inspection

Inspect JWT Claims and Metadata

Review a token’s claims, timing fields, and header values in one clear decode-only inspection view.

Tool focus

JWT claim inspection

Best for claim review when your main goal is understanding what a token says rather than verifying it.

Input

Paste the full token

Paste a JWT here to inspect timing claims, header details, and payload values.

Ready

Timing Hints

Issued AtNot present
Not BeforeNot present
Expires AtNot present

Use these timestamps as inspection hints, not trust verification.

Decoded header

Decode a JWT to inspect the header.

Decoded header and payload will appear here.

Decoded payload

Decode a JWT to inspect the payload.

Decoded header and payload will appear here.

Algorithm

Unknown

Declared in the header as `alg`.

Token Type

Unknown

Usually `JWT`, but not always present.

Signature

Waiting

Presence only. This page does not verify it.

Decode-only mode

Inspect claims fast without pretending to verify trust.

This tool decodes JWT structure for debugging and review. It does not verify the signature, issuer, audience, or signing key.

Header.Payload.Signature

Why inspect JWT metadata?

JWT issues often come down to claims and timing. A token may be structurally valid but still fail because it is expired, not yet valid, or missing the fields your application expects. An inspection-focused page helps you review those details quickly.

Inspection is useful when you need to:

Check whether a token looks expired.

Review auth metadata without verifying the signature yet.

Understand why a token might be rejected by an app.

Timing claims are often the key

Fields like exp, iat, and nbf can explain a surprising number of auth problems. If a token is expired, issued unexpectedly, or not yet valid, your app may reject it even when the rest of the claims look correct.

Header values still matter

The header can also reveal important context, such as the declared algorithm and token type. Those fields help you understand what kind of token you are looking at and whether it matches your application expectations.

Decode first, verify separately

Inspection is a useful early step because it is quick and low friction. Once you understand the token contents, you can move into separate verification workflows if you need to confirm trust, issuer configuration, or signing keys.