Cron Expression Parser

The parser breaks down the input cron expression string into individual field tokens (seconds, minutes, hours, day of month, month, day of week, and optional year). It evaluates special operators such as wildcards (*), step increments (/), ranges (-), lists (,), and Quartz directives (L, W, ?, #). It then compiles these rules into natural language sentences describing the exact trigger schedule.

Yes! The parser inspects the number of whitespace-separated fields in your expression. Expressions with 5 fields are categorized as standard Linux Crontab syntax. Expressions with 6 fields are treated as Quartz Cron syntax (starting with seconds), and expressions with 7 fields are categorized as Quartz + Year syntax. You can also manually override the format selector if needed.

In Quartz scheduler, the question mark (?) represents 'no specific value' and is used in either the Day of Month or Day of Week field. Quartz requires that when one of the day fields is explicitly set, the other must be set to '?' to prevent scheduling conflicts.

These are Quartz-specific directives: 'L' stands for 'Last' (e.g. last day of month or last Friday '5L'). 'W' stands for 'Nearest Weekday' to a given day of the month (e.g. '15W' runs on the nearest Mon-Fri to the 15th). '#' specifies the Nth occurrence of a weekday in a month (e.g. '2#1' represents the 1st Monday).

Our client-side cron engine uses backtracking algorithms to iterate through dates in your target timezone. It matches every minute/hour/day rule against real calendar dates for the selected month and highlights every trigger date with interactive timestamp previews.

Yes, 100%. All parsing, validation, English translation, and calendar execution calculations occur entirely inside your browser's local JavaScript engine. No cron expressions or server configurations are transmitted to remote servers.