Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenBreak a cron line into labelled fields so you can see which value controls what.
A bare schedule or a whole crontab line both work.
The first five whitespace-separated values are taken.
Each value is shown next to its field name.
Open Cron Calendar for a sentence and upcoming run times.
Someone put 15 */4 1,15 * * into a deploy config, and you need to know which number is the hour before you approve it. Field order in cron is easy to misremember. Cron Explainer lines up each value with its field name.
Paste an expression and the output lists the first five whitespace-separated fields with their names: minute, hour, day-of-month, month and day-of-week. Anything after the fifth field, such as the command at the end of a crontab line, is ignored, so you can paste a full line from crontab -l. Fewer than five fields produces an error asking for the complete format. The output can be copied or downloaded.
This tool labels the fields; it does not translate them into a sentence or check the values. A six-field Quartz expression with a leading seconds field will be mislabelled, because the seconds value lands in the minute slot. Reading is still quick once each part is named: 15 */4 1,15 * * means minute 15 of every fourth hour on the 1st and 15th of each month. For a full plain-English description and the next run times, open the cron schedule preview with timezones. To write a new schedule, the visual cron builder has one box per field.
The split happens in your browser as you type, and the expression is not sent anywhere.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
The explainer assumes the classic five-field order. Quartz and Spring expressions put seconds first, so every label is shifted by one. Drop the seconds field before pasting.
Every fourth hour starting from 0, so 00:00, 04:00, 08:00, 12:00, 16:00 and 20:00. A step counts from the start of the field range unless you give a range before the slash, such as 1-23/4.
Yes. Only the first five fields are read, so the command, its arguments and any output redirection at the end are ignored.