Cron Expression Parser
Parses a standard 5-field cron expression, shows each field separately and works out the next run times. Every calculation runs in your browser.
Results
Enter a cron expression and press "Parse".
Enter a valid 5-field cron expression — e.g. 0 9 * * 1-5.
Field breakdown
- Minute
- —
- Hour
- —
- Day of month
- —
- Month
- —
- Day of week
- —
Next 5 runs
Times are shown in your browser's local time zone.
Frequently Asked Questions
What are the five fields of a cron expression?
A standard cron expression has five fields, left to right: minute (0-59), hour (0-23), day of month (1-31), month (1-12) and day of week (0-6, 0 = Sunday). Each field can hold a star (*), a single value, a range (1-5), a list (1,3,5) or a step (*/15).
Which cron format does a Kubernetes CronJob use?
A Kubernetes CronJob uses standard 5-field Unix cron syntax in its schedule field. There is no seconds field. The time zone defaults to that of the kube-controller-manager; an IANA time zone can be set via the spec.timeZone field.
What happens when day-of-month and day-of-week are both restricted?
When neither field is a star, standard cron combines them with OR logic: the job runs when the day of month OR the day of week matches. This is a common misunderstanding and can cause a job to run more often than expected.
What does */15 mean?
The slash is a step value. In the minute field, */15 means "start at 0, every 15 minutes" — that is 0, 15, 30 and 45. */5 means every five units, and 10-30/5 matches between 10 and 30 in steps of five.
Why are the next run times shown in local time?
This tool computes the next runs in your browser's local time zone so they are easy to read. When a CronJob actually fires in production depends on the cluster's time zone or spec.timeZone — do not conflate the two.