Cron parser
Plain-English explanation and the next runs, computed locally.
Plain-English explanation and the next runs, computed locally.
Guides for the expressions everyone ends up needing:
Five space-separated fields — minute, hour, day of month, month, day of week — each accepting
exact values, ranges (1-5), lists (1,15), steps (*/10),
and names (mon, jan). This parser implements standard (POSIX/Vixie)
cron semantics, including the surprising rule that a restricted day-of-month and day-of-week
combine with OR, and previews upcoming fire times in your local timezone.
Everything runs in your browser — nothing to install, nothing sent anywhere. For the inverse direction (English to cron), start from a nearby example chip and adjust.
Left to right: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC), day of week (0–7 or SUN–SAT, where 0 and 7 are both Sunday). * means "every".
Classic cron quirk: when day-of-month AND day-of-week are both restricted, the job runs when EITHER matches. That expression fires every Friday and on the 13th of every month — not only Friday the 13th.
Your browser’s local timezone — the same clock crond would use on a server set to your timezone. Remember production servers often run UTC.
Yes — @yearly, @monthly, @weekly, @daily, @midnight, @hourly aliases, plus steps (*/5, 1-30/2), ranges (mon-fri), lists (1,15) and names (JAN, SUN).