⏰ Cron Next Run Calculator
minute hour day-of-month month day-of-week (day-of-week: 0=Sun...6=Sat, 7 also means Sunday)
Enter a valid cron expression
Parses a standard 5-field cron expression (minute, hour, day-of-month, month, day-of-week) and calculates several of its upcoming run times. Useful for double-checking a cron expression before deploying it.
How to use
- Enter a cron expression as "minute hour day month weekday" (e.g. 0 9 * * 1-5 is 9 AM on weekdays).
- You can also pick a common expression from the preset buttons.
- Choose UTC or this browser's time zone to match your server; the next five run times are shown in both UTC and your local time.
How the calculation works
This tool reads a five-field cron expression (minute hour day month weekday) and checks each minute from now onwards to find the next five times it matches. Supported syntax • * (every), 5 (a value), 1-5 (a range), 1,15 (a list), */15 (every 15), 5/20 (from 5, every 20) • Months as JAN–DEC and weekdays as SUN–SAT • 0 and 7 both mean Sunday in the weekday field When both day of month and day of week are set, a day matching either one counts, as in standard cron. Out-of-range values (such as minute 75), a step of zero (*/0) and unreadable text are reported as errors. You can choose whether the expression is interpreted in UTC or in this browser's time zone.
Worked example
0 9 * * 1-5 (in UTC) Runs at 09:00 UTC on weekdays (Monday–Friday) — 18:00 in Japan The same expression in the browser's time zone (Japan) 09:00 JST on weekdays → 00:00 UTC 0 0 13 * FRI Runs at midnight on the 13th of every month and every Friday (not only Friday the 13th) 0 0 30 2 * February 30 does not exist, so no run times are shown.
Things to be aware of
- Some cron implementations (such as Quartz) use six or seven fields with seconds or years. This tool supports the standard five-field form.
- In regions with daylight saving time, some local times are skipped or occur twice on the changeover days.
- GitHub Actions schedules run in UTC.
FAQ
What happens if both day-of-month and day-of-week are set?
Following standard cron behavior, if either field isn't "*", a match on EITHER field is enough (an OR condition, not AND).
What timezone are the times shown in?
You can calculate the expression in UTC or in this browser's time zone. Many cloud servers run on UTC, so UTC is the default; switch if your server's clock is set to your local time. Results are shown in both UTC and your local time.
Are step values (*/15) and ranges (1-5) supported?
Yes — comma-separated lists, hyphenated ranges, and slash step values are all supported.