Cron expression generator.
Paste a 5-field cron expression to read it in plain English, or customize the schedule below.
No uploads. Nothing saved.
Format: minute (0–59) · hour (0–23) · day (1–31) · month (1–12) · weekday (0–6, 0 = Sun)
Build and read 5-field cron expressions in plain English
Pick a schedule by minutes, hours, weekdays or day of the month, or paste any 5-field crontab string to read what it means in plain English.
- Pick schedules by minutes, hour, day, weekday or month
- Translate 5-field cron expressions into plain English
- Validates ranges, macros and calendar dates instantly
Common questions
What are the 5 fields in a standard cron expression?
From left to right: Minute (0–59), Hour (0–23), Day of month (1–31), Month (1–12 or JAN–DEC), and Day of week (0–6 or SUN–SAT, where both 0 and 7 mean Sunday). Six-field expressions with a leading seconds column are non-standard and rejected here.
Why does setting both Day of Month and Day of Week behave unexpectedly?
In standard POSIX and Vixie cron (including Linux crontab, GitHub Actions, and Cloudflare Cron Triggers), restricting both Day of Month and Day of Week matches when EITHER field is true (OR, not AND). For example, 0 9 15 * 1 runs on the 15th of every month AND on every Monday.
Which time zone do cron schedules use?
GitHub Actions and Cloudflare Cron Triggers evaluate schedules in UTC, whereas Linux crontab uses the server's local system time zone.
What happens on February 31 or shorter months?
Impossible calendar dates like February 31 are flagged immediately because they never run, and schedules on day 29–31 skip shorter months.