Cron Expression Explainer
Crontab lines are compact to the point of being cryptic: five space-separated fields of numbers, stars, commas and slashes decide when a job runs — and a single misplaced character can silently schedule it for the wrong night.
How to use
- Paste a 5-field cron expression, e.g. 0 9 * * 1.
- Read the plain-language schedule description.
- Optionally set a reference date and time for the forecast.
- Check the next five run times in your local time zone.
Frequently asked questions
Which cron syntax is supported?
The standard 5-field form: minute (0-59), hour (0-23), day of month (1-31), month (1-12) and day of week (0-7, where both 0 and 7 mean Sunday). Each field accepts *, numbers, comma lists, a-b ranges and / steps such as */15 or 1-10/2. @daily-style macros and seconds-level cron are not supported.
What happens when both day-of-month and day-of-week are set?
Standard Vixie cron applies OR semantics: if neither field is a star, the job runs when either the day of month OR the weekday matches. So 0 0 1 * 1 fires on the 1st and on every Monday. A bare star does not restrict the schedule; a star step (such as */2) expands into concrete values and does restrict it (OR applies when both day fields are restricted).
How are the next run times calculated?
The engine walks the calendar minute by minute from your reference moment — now by default — and lists the first five matches, strictly after that moment. The forecast uses your browser time zone, so a server in UTC may trigger the same crontab line at different wall-clock times.
Why do my predicted times differ from the server?
Cron daemons fire in the server time zone, while this page shows your local time. If your job runs on a UTC server and you are in UTC+8, 0 9 * * * fires at 17:00 your time. Set the reference moment and compare accordingly.
Are @daily, @hourly or restart-style shortcuts supported?
No. The explainer intentionally covers the 5-field crontab syntax only, and it says so instead of guessing: typing @daily returns an explicit error asking for the expanded form (0 0 * * *). Seconds-level schedules are out of scope too.
Is my expression uploaded anywhere?
No. Parsing, description and the run-time forecast all happen locally in your browser. The expression never leaves your device.
Related tools
About this tool
Crontab lines are compact to the point of being cryptic: five space-separated fields of numbers, stars, commas and slashes decide when a job runs — and a single misplaced character can silently schedule it for the wrong night. This free cron expression explainer parses the standard 5-field syntax (minute, hour, day of month, month, day of week) and translates it into a plain-English sentence, so you can confirm at a glance that 0 9 * * 1 really means 09:00 every Monday. Lists, ranges and steps are all supported: 0,30, 1-15 and */15 each expand into explicit values, and day-of-week 7 is normalized to 0 (Sunday). Beyond the description, the tool predicts the next five execution times from a reference moment — the current time by default — using your browser time zone, which makes it easy to sanity-check a schedule before you deploy it. The day and weekday fields follow the standard Vixie cron rule when both are restricted, and the FAQ below spells out that OR semantics. Everything runs locally in your browser: paste nothing-sensitive anywhere, no account, no upload.