What it does
Type a cron expression and get a plain-English description, the next 10 (or 25, 50) run times, and a breakdown of every field. Run times are calculated by this page’s own scheduler in local time, UTC or any IANA time zone, so you can check a server’s schedule from anywhere.
Supported syntax: *, lists (1,15), ranges (1-5), steps (*/10, 5-50/15, 10/20), month and weekday names (JAN, MON-FRI), the macros @hourly, @daily, @weekly, @monthly and @yearly, and the extensions L, W, LW, 5L and MON#2. When both day-of-month and day-of-week are restricted, a day matches if either matches, as in classic cron. In zones with daylight saving time, wall-clock times that do not exist are skipped and repeated times run once.
Unix cron, Hangfire and Quartz.NET
- Unix cron has 5 fields: minute, hour, day of month, month, day of week (0 or 7 = Sunday).
- Hangfire (which uses the Cronos library) and NCrontab accept the same 5 fields, plus an optional seconds field in front (6 fields).
- Quartz.NET always starts with seconds, adds an optional year field (6 or 7 fields), numbers weekdays 1-7 with 1 = Sunday, and requires
?in either day-of-month or day-of-week.
Format detection is automatic: 7 fields or a ? selects Quartz numbering. Here ? is treated like *. You can also choose the format yourself.
Privacy
The description comes from the open-source cronstrue library; everything runs in your browser and nothing is uploaded.