Cron Expression Parser
Parse 5/6-field cron expressions and list the next 5 fire times
Supported Syntax
* any value; plain numbers; a-b range; a-b/n stepped range; */n step from minimum; comma-separated lists; month abbreviations JAN-DEC; weekday abbreviations SUN-SAT; L last day of month; both 0 and 7 mean Sunday in the week field; when day and week are both non-*, an OR match applies (either satisfying triggers execution).
How to Use
Cron expressions are widely used in Linux crontab, Quartz, and Spring Scheduled for recurring tasks. This tool supports the classic 5-field format (min hour day month week) and the 6-field format (sec min hour day month week), and prints the next 5 fire times from now so you can verify an expression quickly.
Supported syntax: * any value; plain numbers; a-b range; a-b/n stepped range; */n step from minimum; comma-separated lists; month abbreviations JAN-DEC; weekday abbreviations SUN-SAT; L last day of month; when day and week are both non-*, they match on an "OR" basis (either satisfying triggers execution).
FAQ
What is the difference between 5-field and 6-field formats?
The 5-field format is "min hour day month week" with minute granularity; the 6-field format adds a "second" field at the front for second granularity. Toggle the field checkboxes to switch modes (5-field is the default).
How are day and week matched when both are set?
When neither day nor week is *, Unix cron treats them as an OR: execution triggers if either the day or the weekday condition is met. If one of them is *, an AND is applied instead.
What does L mean?
L applies only to the day field and means the last day of the month. Since months vary in length, the tool computes the actual last day dynamically (including February in leap years).