Explain a cron expression in plain English or build one field by field, and see the next run times in any time zone
Paste a cron expression to read it in plain English and see exactly when it runs next, in your time zone or your server’s. Or switch to Build and make one field by field.
How to use it
Type a cron expression (5 fields, 6 with seconds first, Quartz’s 7 with a year, or an EventBridge cron(...)) or pick a preset. Read as: Any cron tells the kinds apart; pick Quartz when 1 means Sunday. Read the sentence and the field-by-field breakdown. To make or change a schedule without writing cron, choose Build: each field gets a row, and the expression follows. Pick the server’s time zone to see the next 10 runs as it will see them. Read what deserves a second look, and copy the same schedule for Linux cron, Kubernetes, GitHub Actions, Quartz, Spring, EventBridge or a systemd timer.
Examples
Business hours, every 15 minutes
*/15 9-17 * * 1-5
Every 15 minutes, between 09:00 and 17:59, Monday through Friday
Macro
@weekly
0 0 * * 0 → At 00:00, only on Sunday
Cron syntax
| Symbol | Meaning | Example |
|---|---|---|
* | Every value | * in hour = every hour |
, | List | 1,15 = the 1st and the 15th |
- | Range | 1-5 in day of week = Monday to Friday |
/ | Step | */10 in minute = every 10 minutes |
? | No value: the other day field decides (Quartz, EventBridge; Spring reads it as *) | 0 0 12 ? * MON = noon on Mondays |
L, # | Last, nth (Quartz, Spring, EventBridge) | 5#3 = third Friday |
W, LW, L-n | Weekday nearest a day, last weekday, n days before the last (Quartz, Spring, EventBridge) | 15W = the weekday nearest the 15th |
┌──────── minute (0–59) │ ┌────── hour (0–23) │ │ ┌──── day of month (1–31) │ │ │ ┌── month (1–12) │ │ │ │ ┌ day of week (0–7, Sunday = 0 or 7) * * * * *
Quartz, Spring, EventBridge and the others
| Scheduler | Fields | Sunday |
|---|---|---|
Linux cron, Kubernetes, GitHub Actions | minute hour day month weekday | 0 or 7 |
Spring @Scheduled | second minute hour day month weekday | 0 or 7 |
Quartz | second minute hour day month weekday [year] | 1 |
AWS EventBridge | cron(minute hour day month weekday year) | 1 |
Sources: Quartz: CronTrigger tutorial, AWS: cron expressions, GitHub Actions: schedule, systemd.time: calendar events
Worth a second look
Build a schedule field by field
Day of month and day of week together
Questions
- Which time zone does cron use?
The time zone of the machine or service running it. GitHub Actions and AWS EventBridge rules use UTC; a Kubernetes CronJob without a timeZone uses its controller’s zone, often UTC. Pick the zone above to see the run times as the scheduler will. - How do I write a cron expression for every weekday at 9:00?
Choose Build, set Minute to "At these minutes" 0, Hour to "At these hours" 9, and Day of week to "Between" Mon and Fri. The expression is 0 9 * * 1-5; the preset "Weekdays at 9:00" gives the same. - Does it support seconds?
Yes. With 6 fields, the first one is seconds, as in Quartz, Spring and node-cron. - Why does 0 0 12 ? * 2 run on Monday here?
The ? makes it a Quartz expression, and Quartz counts the day of week from 1 = Sunday, so 2 is Monday. In Linux cron 2 is Tuesday. Pick Linux cron under Read as to read the numbers the cron way. - What happens during daylight saving changes?
In zones with DST, a run at a skipped time (e.g. 02:30 on the spring-forward night) may not happen, and one in the repeated hour may happen twice, depending on the scheduler. The next-run list shows the real times in the chosen zone.