JWT Expiry Editor
Edit iat, nbf and exp claims on a JWT and re-sign it without touching JSON by hand.
JWT Expiry Editor
Claims
Updated token
Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
Saved on this device
Your inputs and history are stored locally.
Not saved
This page forgets your work when you leave it.
About this tool
Load a JWT, edit its iat, nbf and exp claims with date pickers, and re-encode the token. Use the quick +15m / +1h / +1d buttons to extend an expiry, then re-sign with HS256, HS384 or HS512, or strip the signature entirely for local testing. Everything runs in the browser.Questions
- The signature no longer verifies after editing — is that a bug?
- No. Changing any claim changes the signed data. Re-sign with the same secret and algorithm the issuer used, or the token will be rejected.
- Can it sign with RS256 or ES256?
- Not yet. This tool focuses on HMAC secrets for quick testing; use the JWT Encode tool for PEM-based algorithms.