JWT Expiry Checker

Decode a JWT and inspect its expiry status, time remaining or elapsed, issued-at, not-before, and registered claim details without signature verification.

JWT Token

Status

—

Time Remaining

—

Lifetime

—

Algorithm

—

Issued At (iat)

—

Expires At (exp)

—

Not Before (nbf)

—

Subject (sub)

—

Issuer (iss)

—

JWT ID (jti)

—

This tool decodes the JWT payload locally in your browser to inspect time-related claims. It does not verify signatures or validate claim logic.

About this tool

JWT Expiry helps developers, security engineers, and QA testers decode a JWT and inspect its expiry status, time remaining, issued-at, not-before, subject, issuer, and algorithm claims without signature verification. Use it for debugging expired tokens, verifying claim values, and searchable workflows like JWT expiry checker or JWT token expiration.

Use cases

Paste a JWT from an API response, log entry, or browser storage to quickly see whether it has expired and how long ago or how much time remains.
Check the iat, exp, and nbf claim values in a token during integration testing or incident investigation without writing a custom decode script.
Verify that a token's subject, issuer, and algorithm fields match expectations before escalating an authentication failure or debugging a 401 response.
Copy the expiry ISO timestamp or relative time into a bug report, support ticket, or incident note without needing a JWT library or REPL session.

FAQ

What is JWT Expiry used for?

Use JWT Expiry to decode a JWT and inspect its expiry status, time remaining or elapsed, issued-at timestamp, not-before claim, subject, issuer, algorithm, and other registered claims without signature verification.

Does this tool verify the JWT signature?

No. JWT Expiry decodes the header and payload to read claim values but does not verify the signature. Use a proper JWT library with the signing key to validate authenticity in production workflows.

What claims does it show?

It shows exp, iat, nbf as ISO timestamps with relative descriptions, plus subject, issuer, JWT ID, and algorithm from the header. Non-standard claims in the payload are not displayed but can be read using the related JWT Codec tool.

Why does an expired token still show a past exp timestamp?

Expiry is based on the current time at the moment you check the token. The exp claim stores the intended expiry as a Unix timestamp, and the tool compares it to now. A past exp value means the token expired at that moment.