JWT nbf (Not Before) Claim Checker
Check the JWT nbf claim. See the "not before" time as a readable UTC date and find out why a fresh token is rejected as not yet valid.
Part of the free JWT Decoder. Runs in your browser — nothing is uploaded.
JWT nbf (Not Before) Claim Checker
The nbf claim marks the earliest moment a token may be accepted. If a client uses a token seconds after issuance and your server clock is slightly behind, validation fails with "token not yet valid". Decode it to see the exact times.
Worked example: A token that becomes valid one hour after issue
JWT
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyXzMiLCJpYXQiOjE3NjcyMjU2MDAsIm5iZiI6MTc2NzIyOTIwMCwiZXhwIjoxNzY3MzE1NjAwfQ.c2lnbmF0dXJl
Decoded with times
// HEADER
{
"alg": "HS256",
"typ": "JWT"
}
// PAYLOAD
{
"sub": "user_3",
"iat": 1767225600,
"nbf": 1767229200,
"exp": 1767315600
}
// CLAIM TIMES (UTC)
iat: 2026-01-01 00:00:00 UTC
nbf: 2026-01-01 01:00:00 UTC
exp: 2026-01-02 01:00:00 UTCPractical tip
Allow 30–60 seconds of clock leeway when validating nbf, exp and iat. Most JWT libraries have a clockTolerance option for this.
How to use this JWT Decoder
- 1Use the live tool above — it runs entirely in your browser and never uploads your data.
- 2Paste the sample from the worked example, or use your own input.
- 3Copy the result, then adapt the same steps in your editor, script, or pipeline.
JWT nbf (Not Before) Claim Checker FAQs
Why is my new JWT rejected as not yet valid?
Usually clock skew: the validating server's clock is behind the issuer's, so nbf or iat looks like it is in the future. Sync clocks with NTP and add small leeway.
Is nbf the same as iat?
No. iat is when the token was issued. nbf is when it starts being valid, which can be later than iat for delayed activation.
More JWT Decoder pages
- Decode a JWT Token OnlineDecode a JWT token online to read its header and payload claims. Paste the token and see readable JSON instantly. Runs in your browser, nothing is uploaded.
- JWT Expiration CheckerCheck when a JWT expires. Paste the token to read the exp claim as a human-readable UTC date and see if your access token is still valid.
- Decode a JWT Without the SecretYou can decode a JWT without the secret because the header and payload are only Base64URL encoded. Paste a token to read it. Verification needs the key.
- JWT Payload ViewerView the JWT payload and its claims such as iss, aud and sub. Paste a token to inspect who issued it, who it is for and what scopes it carries.
- Decode an Auth0 JWTDecode Auth0 ID tokens and access tokens to inspect claims like iss, aud, scope and custom namespaced claims. Free, local and private.
- Decode a Firebase ID TokenDecode a Firebase Authentication ID token to inspect uid, email, auth_time and sign-in provider claims. Free browser-based Firebase JWT decoder.
- Decode an AWS Cognito JWTDecode AWS Cognito ID and access tokens. Inspect token_use, cognito:groups, client_id and username claims. Free local JWT decoder.
- JWT Header and Algorithm CheckerCheck a JWT header for the alg, typ and kid fields. Find out whether a token is signed with HS256 or RS256 and which key ID to verify with.
- JWT Claims Explained With a Live DecoderLearn what every registered JWT claim means: iss, sub, aud, exp, nbf, iat and jti. Paste a token to see each claim decoded.