Cron expressions
Read and write cron expressions
Settings
Syntax: values, lists (1,15), ranges (1-5), steps (*/10), names (JAN, MON) and macros (@daily, @hourly…).
Common presets
Result
In plain words
At 09:00 AM, Monday through Friday
Next runs
About this tool
This tool helps you write and check a cron expression, the kind you put in a crontab, a scheduled CI job or a server task. Instead of guessing whether 0 9 * * 1-5 really runs every weekday morning, you get a plain-language sentence and the dates of the upcoming runs right away.
It supports the standard five-field syntax: minute, hour, day of month, month and day of week, with values, lists, ranges, steps, names such as JAN or MON, and macros such as @daily or @hourly. You can type the whole expression, build it field by field or start from a common preset, then show 5 or 10 runs in local time.
How to use it
- Type an expression into “Cron expression” or click one of the “Common presets”.
- Adjust each value under “Field by field” if needed, within the allowed values shown.
- Read the explanation under “In plain words” and check the “Next runs”, choosing 5 or 10.
- Click the copy button next to the field to grab the expression.
Frequently asked questions
Are 6-field expressions with seconds supported?
No. The tool follows the standard five-field cron format used by crontab and most schedulers. A Quartz or Spring expression with a seconds or year field is flagged as invalid, along with the number of fields found.
Which time zone are the next runs calculated in?
Your browser’s time zone, shown above the list. If your server or platform runs jobs in UTC, as many do, the actual times may differ, so shift the expression accordingly.
What happens if I set both day of month and day of week?
As in cron, when both fields are restricted the job runs when either one matches. So 0 0 13 * 5 runs on every 13th of the month and every Friday, not only on Friday the 13th. The plain-language sentence spells this out.
Is my expression sent anywhere?
No. Parsing, the description and the run dates are all computed in your browser. The expression you enter and the number of runs shown are only saved locally, so they are still there on your next visit.