Cron Expression Simulator
Enter a cron expression (e.g. */15 9-18 * * 1-5) to get a plain-English explanation and a list of upcoming run times. Handy for checking a crontab entry or validating a GitHub Actions or Kubernetes CronJob schedule. Everything happens in your browser, and nothing you type is ever sent to a server. Need to convert a date/time as well? Check out the Unix Timestamp Converter too.
🔒 Runs in your browser · Your data is never sent to a server
Upcoming run times
Cron syntax reference
| Position | Field | Allowed values |
|---|---|---|
| 1st | Minute | 0-59 |
| 2nd | Hour | 0-23 |
| 3rd | Day of month | 1-31 |
| 4th | Month | 1-12 |
| 5th | Day of week | 0-7 (0 and 7 are Sunday) |
*means every value (every minute, every hour, ...),lists multiple values (e.g.1,15,30)-specifies a range (e.g.9-18)/specifies a step (e.g.*/15means every 15 units)
Notes
- Supports the standard 5-field format (minute hour day month weekday) and common aliases like
@daily. It does not support a 6-field seconds format, Quartz-styleL,W, or#, or named months/weekdays (mon, jan, etc.). - Upcoming run times are calculated using your device's local timezone.
- If the expression describes a date that never occurs (such as February 30th), the list of upcoming runs may come back empty.
Glossary
Cron expression
A format for describing a recurring schedule, used by Unix/Linux cron, GitHub Actions, Kubernetes CronJob, and more. It has five space-separated fields: minute, hour, day of month, month, and day of week.
Aliases (@daily, etc.)
Shorthand for common schedules: @yearly (Jan 1st at midnight), @monthly (1st of the month at midnight), @weekly (Sunday at midnight), @daily (every day at midnight), and @hourly (every hour on the hour).
Day-of-week values 0-7
0 is Sunday, 1 is Monday, ... 6 is Saturday. Many implementations also accept 7 as Sunday, and this tool treats 7 the same as 0.
AND/OR logic for day-of-month and day-of-week
When both the day-of-month and day-of-week fields are restricted (not *), cron matches a date if EITHER field matches (an OR condition, not AND). If either field starts with * (such as */2), Vixie cron / cronie uses AND instead (both must match). If only one is restricted, only that field's condition applies.
FAQ
In cron, is Sunday 0 or 7?
In standard cron, 0 is Sunday, and some implementations also accept 7. This tool treats both 0 and 7 as Sunday, with 1 to 6 as Monday to Saturday.
What happens if I set both day-of-month and day-of-week?
When both fields are something other than "*", the job runs if either condition matches (OR logic), not both. Watch out for unexpected runs.
Can I use it for GitHub Actions or Kubernetes schedules?
For 5-field expressions, yes. Note that GitHub Actions uses UTC, while this tool shows run times in your device's local time, so account for the time difference.
Share this page