Build cron schedules visually, translate to plain English, and see the next 10 run times
| Character | Meaning | Example |
|---|---|---|
| * | Any/every value | * * * * * — every minute |
| , | List of values | 0,30 * * * * — at :00 and :30 |
| - | Range of values | 0 9-17 * * * — 9am to 5pm |
| / | Step values | */15 * * * * — every 15 minutes |
| L | Last (day-of-month/week) | 0 0 L * * — last day of month |
| ? | No specific value (Quartz) | Used in day fields when both not needed |
Yes. The builder validates your CRON expression client-side using a JavaScript cron parser, accurately computing the next 10 scheduled run times. This matches the behaviour of standard Linux cron daemons and popular scheduling libraries such as node-cron.
Standard Unix/Linux cron uses 5 fields: minute, hour, day-of-month, month, and day-of-week. A 6-field format (used by Quartz, Spring, and AWS EventBridge) prepends a seconds field. The builder supports both formats with a toggle, and the human-readable translation updates automatically.
Set minute to 0, hour to 9, and day-of-week to 1-5 (Monday through Friday). Leave day-of-month and month as *. Your expression is 0 9 * * 1-5 and the builder confirms it as: Every weekday at 9:00 AM.
A standard Unix cron expression has 5 fields: minute hour day-of-month month day-of-week. Each field can be a number, a range (1-5), a list (1,3,5), or a step (*/10). The 6-field variant adds a seconds field at the start.
* matches any value. , separates multiple values. - defines a range. / defines steps — e.g., */5 in the minute field means every 5 minutes. L means "last" (last day of month, or last Friday = 5L). W finds the nearest weekday. # specifies the Nth occurrence of a weekday (e.g., 2#3 = third Tuesday).
*, most implementations trigger when either condition is met (OR logic), not AND.0 in Unix cron but 7 is also accepted on many systems. Quartz uses 1=Sunday.Save history & custom presets — coming soon for logged-in users