Open JWT Decoder
Decodes the token and tells you what is wrong with it.
Paste a cron expression and get it in plain English, with the next runs worked out. Parsed here on the server, so it answers instantly and nothing is sent to a model.
How many future firing times to list.
⌘↵ to run
STANDING BY
This panel has nothing to do yet.
Put some text into 01 and it lands here. The sample works too, if you would rather not think of anything.
How your text is processed. Pressing Explain schedule sends your text to NexKit's servers, where it is parsed and answered outright. No AI model is involved and nothing is passed to any third party. NexKit does not store what you submit, and there are no accounts to link it to.
Five fields, or a shorthand like @daily.
Three, five or ten upcoming firing times.
One sentence in English, then the actual dates it will fire.
No. A cron expression has exactly one correct reading, so it is parsed on our server rather than described by a model. Nothing is sent to any AI provider, and the result comes back in milliseconds.
UTC. Cron itself has no timezone — the schedule fires according to the clock of whatever machine runs it, so a job set for 03:00 runs at 03:00 local time there, and daylight saving moves it twice a year.
Almost always the day fields. When both day-of-month and day-of-week are restricted, cron fires when EITHER matches, not both. "0 0 13 * 5" means the 13th of the month OR any Friday — not Friday the 13th. The tool warns when your expression has this shape.