WHAT IT DOES
Find out when that schedule actually fires.
Paste a five-field cron expression to get a plain-English description of the schedule and a list of its next executions in your local timezone. Reading the upcoming run times is the fastest way to catch an expression that is subtly wrong, such as one that fires every minute for an hour instead of once.
Why use it?
Use it to catch schedules that are valid but run at the wrong times, particularly when copying cron expressions between systems.
How to use this tool
- Paste a five-field schedule and choose Explain. For example, 0 9 * * 1-5 means 09:00 on weekdays.
- Choose Next runs and inspect several occurrences in the browser's local timezone.
- Compare that timezone and cron dialect with the scheduler you will deploy to. This page does not create a job, and a six-field schedule with seconds is not interchangeable with a five-field one.
Details and limitations
- Standard five-field syntax is supported: minute, hour, day of month, month, and day of week.
- Ranges, lists, steps, and wildcards are parsed, including forms such as */15 and 1-5.
- Upcoming runs are calculated in the browser's local timezone, not the server's.
- Invalid field values and out-of-range numbers are reported explicitly rather than being ignored.