Cron Expression Parser
Understand any cron schedule in plain English, with the next eight run times.
The five fields, left to right
A standard cron expression has five whitespace-separated fields:
┌───────── minute 0–59
│ ┌─────── hour 0–23
│ │ ┌───── day of month 1–31
│ │ │ ┌─── month 1–12 (or jan–dec)
│ │ │ │ ┌─ day of week 0–6 (Sunday = 0, or sun–sat)
│ │ │ │ │
0 9 * * 1-5
That example reads "at 09:00, Monday through Friday". Each field accepts * (every value), a number, a range a-b, a step */n, and comma-separated lists combining any of these — so 0,30 9-17 * * 1-5 runs every half hour during business hours on weekdays.
The day-of-month / day-of-week quirk
This is the part that surprises everyone. If both the day-of-month and day-of-week fields are restricted, standard Vixie cron runs the job when either matches — an OR, not an AND. So 0 0 13 * 5 does not mean "Friday the 13th"; it means "every 13th of the month, plus every Friday". To get Friday the 13th you need a guard in the command itself. Some implementations (notably Quartz) use AND instead, which is one reason crontabs are not portable.
Steps and ranges
*/15 in the minute field means every 15 minutes starting at 0: 00, 15, 30, 45. 10-50/20 means 10, 30, 50. A step on a single value is usually interpreted as "from that value to the maximum" in Vixie cron, though implementations differ — verify on your platform if the schedule is critical.
Timezones and DST
Cron uses the system timezone. During a DST transition, jobs scheduled in the skipped hour may not run at all, and jobs in the repeated hour may run twice. For anything billing-related or idempotency-sensitive, schedule in UTC and design the job to tolerate duplicate invocation.
Beyond five fields
Quartz (Java) adds a seconds field at the front, plus ? for "no specific value" and L/W for last-day constructs. AWS EventBridge and Kubernetes CronJob also use non-standard extensions. Always check which dialect the specific scheduler expects — a schedule that parses is not necessarily a schedule that runs when you think.
Frequently asked questions
What does */5 mean?
*/5 runs at minutes 0, 5, 10 … 55 — that is, twelve times an hour, not "every five minutes from now".Is Sunday 0 or 7?
sun name is unambiguous and preferable in a shared crontab.Why does my job run at the wrong time?
/etc/timezone or set CRON_TZ; scheduling in UTC avoids the problem entirely.