ToolHub
โฒ๏ธ

Cron Expression Parser

Explain cron schedules in plain English + next runs.

โ„น๏ธ
Runs at minute 0, 15, 30, 45, past hour 9, 10, 11, 12, 13, 14, 15, 16, 17, on mon, tue, wed, thu, fri, every month

Next runs

Mon, Sep 7, 2026, 09:00next
Mon, Sep 7, 2026, 09:15in 2627 min
Mon, Sep 7, 2026, 09:30in 2642 min
Mon, Sep 7, 2026, 09:45in 2657 min
Mon, Sep 7, 2026, 10:00in 2672 min
Mon, Sep 7, 2026, 10:15in 2687 min
Field breakdown
minute:        0, 15, 30, 45
hour:          9, 10, 11, 12, 13, 14, 15, 16, 17
day of month:  1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31
month:         1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
day of week:   1, 2, 3, 4, 5

Supports *, lists 1,3,5, ranges 9-17, steps */15 and names (MON, JAN). When both day-of-month and day-of-week are restricted, either may match (standard Vixie cron behavior).

About the Cron Expression Parser

Turn a five-field cron expression into plain English plus a schedule of upcoming runs. The tool explains minute, hour, day-of-month, month and day-of-week ranges, lists the next six execution times with countdowns, and follows standard Vixie cron behavior when both day fields are restricted.

How to use the Cron Expression Parser

  1. Type or paste a cron expression such as */15 9-17 * * 1-5.
  2. Read the Runs sentence describing the schedule in words.
  3. Check the Next runs table for the following six fire times with minutes-until countdowns.
  4. Use the Field breakdown box to verify exactly which values each field expands to.

Cron Expression Parser FAQ

Which syntax is supported?

Standard five-field crontab syntax: * any value, comma lists like 1,3,5, ranges like 9-17, steps like */15, and month or weekday names such as JAN and MON.

What happens when both day fields are set?

Following Vixie cron convention, if day-of-month and day-of-week are both restricted, a date matching either one runs the job โ€” the parser mirrors this in its next-run calculation.

Why do I see an error about 5 fields?

The parser expects exactly minute, hour, day-of-month, month and day-of-week separated by spaces; six-field or second-granularity schedules are out of scope.