Pick minute, hour, day, month and weekday one by one and the expression writes itself. Paste an old cron back in to take it apart again. The next five run times are computed in plain JavaScript - no libraries, no server.
Everything stays in this browser on your device. Nothing is uploaded and there's no account. Only your most recent expressions are saved locally; switching browsers or clearing site data will lose them. Use Clear my data in the footer to delete them for good.
Each field has four forms: any, a list of values, a continuous range, or a step. Day and weekday also offer "not specified", written as a question mark in crontab.
* * * * *Saved only on this device. Tap one to load it back into the builder.
| Input | Standard five fields "minute hour day month weekday", with *, ?, comma lists, hyphen ranges and slash steps; JAN / MON style abbreviations accepted for month and weekday |
|---|---|
| Output | Five-field crontab expression, a plain-language reading and the next five run times, shown in local time and UTC side by side |
| Key values | Minute 0–59, hour 0–23, day 1–31, month 1–12, weekday 0–7; day and weekday combine with OR when both are restricted |
| Processing | Plain JavaScript in your browser, no third-party libraries; the last 8 expressions saved to this device's localStorage, never uploaded |
| Limits | Scans up to 4 years ahead for matching times; history keeps 8 expressions |
| Known edges | Impossible dates such as February 30 never produce a run time; Quartz L, W and # syntax, seconds and year fields are not supported |
Yes. This page produces the standard five fields - minute, hour, day, month, weekday - which Linux, macOS and most cloud schedulers accept. Quartz and Spring add a seconds field at the front and sometimes a year field at the end, so pasting five fields there shifts everything by one column.
Standard cron uses OR: the job fires whenever either field matches. For example 0 0 1 * 1 means the 1st of the month or any Monday, not the first Monday of the month. The next-run calculation here follows the same rule and warns you when both fields are restricted.
This page calculates in your device's current time zone and also prints each time in UTC. Most servers log in UTC, so compare the UTC line rather than doing mental time-zone maths. Around a daylight-saving switch you may also see a one-hour shift.
No. Generation, parsing and scheduling all run in your browser. Only your most recent expressions are saved to this device's localStorage so you can pick up where you left off. No requests are sent, there is no account, and Clear my data in the footer removes everything.