Cron Expression Builder & Explainer
Cron syntax is terse and easy to get wrong. Type a schedule into the five field boxes, or paste one from a crontab or CI config, to see a short description and the next times it fires.
The five fields
A standard cron expression has five space-separated fields: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–6, where both 0 and 7 mean Sunday). Each field accepts a single value, a list (1,15), a range (9-17), a step (*/5) or * for every value.
A subtle rule: when both day-of-month and day-of-week are restricted, most implementations run when either matches, not both. 0 9 1 * 1 runs at 09:00 on the 1st of every month and every Monday.
Where cron syntax is used
Beyond the classic Unix crontab, the same five-field format drives Kubernetes CronJob resources, GitHub Actions schedule: triggers, GitLab pipeline schedules, Jenkins, Airflow DAG schedules and most cloud schedulers. Some systems (Quartz/Spring, AWS EventBridge) add a sixth seconds or year field and use ? — if your platform uses six or seven fields, check its documentation before copying a five-field expression.
Time zones
Cron runs in the time zone of the host or scheduler. GitHub Actions and Kubernetes default to UTC; a server crontab uses the system zone. A job meant for 02:00 local time can drift by an hour across daylight-saving changes, and jobs scheduled between 01:00 and 03:00 on DST transition nights may run twice or not at all. Scheduling in UTC avoids most surprises.
How to use it
- Type a value into each of the five field boxes (minute, hour, day of month, month, day of week), or paste or type a full expression into the main input.
- Read the plain-English description and the list of next run times to confirm it means what you intended.
- Try one of the presets (every minute, every hour, daily midnight, weekdays 9am, every 5 min, 1st of month and others) as a starting point and adjust.
Common expressions
A few schedules you will see everywhere:
*/5 * * * * every 5 minutes 0 * * * * at the top of every hour 0 2 * * * daily at 02:00 0 9 * * 1-5 weekdays at 09:00 0 0 1 * * first day of every month at midnight 30 23 * * 0 Sundays at 23:30
Remember that */5 in the minute field means minutes 0, 5, 10 … 55 — it is anchored to the hour, not to when the job was created.
Common use cases
- Writing or auditing
crontab -eentries for backups, log rotation and cleanup scripts. - Setting the
schedulefield of a Kubernetes CronJob or a GitHub Actions workflow. - Decoding an unfamiliar expression inherited from a legacy system before changing it.
- Checking that a reporting job really runs on business days only.
Reading the description and the next runs
The plain-English line is deliberately terse. 30 2 * * 1-5 is described as "Minute 30, hour 2, on day Monday to Friday", and */15 9-17 * * * as "Every 15 minutes, hour 9 to 17". Treat it as a sanity check and rely on the list of the next 10 run times, shown in your local time, to confirm the schedule really does what you meant.
Only five fields are accepted; anything else shows a warning. Month and day names such as jan and sun work in the next-run list, and 7 is read as Sunday, although the description line may show a bare 7. When both day-of-month and day-of-week are set, the next-run list uses the "either matches" rule, so 0 9 1 * 1 fires on the 1st and on every Monday.
Frequently asked questions
How do I run a job every 15 minutes?
Use */15 * * * *. It fires at minutes 0, 15, 30 and 45 of every hour.
Why does 0 0 31 * * not run every month?
Day 31 only exists in seven months. Cron does not clamp to the last day; for month-end jobs run on the 1st and process the previous month, or use L in implementations that support it.
Does cron support seconds?
Standard five-field cron does not; the smallest unit is one minute. Quartz, Spring and some cloud schedulers use a six-field format with seconds first.
Is 0 and 7 both Sunday?
Yes in most implementations (Vixie cron, Kubernetes). Some older systems accept only 0. Using SUN avoids the ambiguity where names are supported.
Are the next run times in UTC?
No. They are calculated in your browser's local time zone. If your job runs in UTC, subtract your offset yourself, or compare with the Timezone Converter.