Skip to content
Dispatching · New York Metro
(347) 262-9435
Free tool · No sign-up

Cron Expression Explainer

Type a cron expression and read it back as a sentence, with the next several run times worked out so you can see whether it fires when you think it does. Handles ranges, steps, lists, and the day-of-month/day-of-week overlap that trips almost everyone. Build one from menus if you would rather not remember the field order.

minute hour day month weekday
In plain English

At 09:00 on weekdays.

Next 6 runsUTC · local
  1. 2026-08-17 09:00:00 UTCAug 17, 2026, 09:00:00 AM UTC· in 2 days
  2. 2026-08-18 09:00:00 UTCAug 18, 2026, 09:00:00 AM UTC· in 3 days
  3. 2026-08-19 09:00:00 UTCAug 19, 2026, 09:00:00 AM UTC· in 4 days
  4. 2026-08-20 09:00:00 UTCAug 20, 2026, 09:00:00 AM UTC· in 5 days
  5. 2026-08-21 09:00:00 UTCAug 21, 2026, 09:00:00 AM UTC· in 6 days
  6. 2026-08-24 09:00:00 UTCAug 24, 2026, 09:00:00 AM UTC· next week
Field reference
Minute
0–59
Hour
0–23
Day of month
1–31
Month
1–12JAN–DEC
Day of week
0–6SUN–SAT, 7 = Sun

Operators: * any, a-b range, a,b,c list, and a slash for steps — a wildcard or range followed by /n takes every nth value.

Method & assumptions
  • Standard 5-field cron: minute, hour, day-of-month, month, day-of-week. Seconds and the non-standard 6th field are not parsed.
  • When both day-of-month and day-of-week are restricted, the job fires when EITHER matches — the Vixie-cron rule, which surprises almost everyone.
  • Times are computed in UTC, because a cron line carries no zone of its own, then shown in UTC and your local time side by side.
  • Everything runs in your browser. The expression is never sent anywhere.
Plate Other tools
Free diagnosticsSame-day dispatchNamed techniciansDone or free
Need it built, not just checked

We write the software
behind tools like these

Anyone writing a crontab or a scheduled job and wanting to be sure of the timing before it ships.

Or call and speak to someone who does the work(347) 262-9435inquiries@jcitsystems.com