Cron Expression Parser

Paste a cron expression into this cron expression parser to see what each field resolves to, when it runs next, and how it covers the week.

What the cron expression parser tells you

A generator answers "what should I write?". The parser answers "what will this actually do?". That matters when you inherit a crontab, a CI schedule, a Helm chart or an event rule. It labels every field, lists the values each field resolves to, shows the next runs in the time zone you pick and draws a week-by-hour heatmap so a surprising schedule stands out.

Cron calculator: find the next run times

A cron calculator answers one practical question: given this expression, when does it run next? Paste the expression, choose a time zone, and the parser lists the upcoming runs in that zone, so you can check a schedule without waiting for it to fire. The calculation follows the same rules as the other tools, including daylight saving transitions.

Reading an expression

Read left to right. The minute field decides when inside the hour the job can run, the hour field which hours are eligible, and day-of-month, month and day-of-week narrow the calendar. Small changes matter: */5 * * * * runs every five minutes, while 5 * * * * runs once an hour at minute 5.

SymbolMeaningExample
*Every value in the field* * * * * every minute
,A list of values0 9,17 * * * at 9:00 and 17:00
-An inclusive range0 9 * * 1-5 weekdays at 9:00
/A step*/15 * * * * every 15 minutes

The symbols ?, L, W and # exist only on some platforms (AWS EventBridge and Quartz). Choose the platform in the validator to see them handled correctly.

Frequently asked questions

Each field of the expression, the values it resolves to, a plain-English sentence, the next run times in your time zone and a weekly heatmap of when it fires. It also reports how the expression is read on other platforms.
The parser explains what an expression does. The validator checks whether a particular platform accepts it and why not.
When both day-of-month and day-of-week are restricted, classic Linux cron runs when either one matches. Linux and Kubernetes behave this way, while Quartz, AWS EventBridge and Vercel do not accept two restricted day fields at all. The parser warns when an expression falls in this case.
On Linux and many other implementations 7 means Sunday, as does 0. On AWS EventBridge and Quartz the days are numbered 1 to 7 with 1 as Sunday, so 7 is Saturday. Use names such as SUN where the platform allows them to avoid the confusion.

Related tools