Nifty Dev Tools
  1. Home
  2. Cron Expression Explainer
Convert

Cron Expression Explainer

We never upload what you paste ✨

Type a cron expression to see what it means, field by field, and when it runs next in your time zone. Classic crontab, Quartz and Spring.

Read as crontab (5 fields: minute, hour, day of month, month, day of week)

What it means

Every 15 minutes from 09:00 through 17:45, Monday through Friday

  • Minute0–59*/15every 15 minutes: 0, 15, 30, and 45
  • Hour0–239-179 through 17
  • Day of month1–31*every day
  • Month1–12 or JAN–DEC*every month
  • Day of week0–7 or SUN–SAT (0, 7 = Sun)1-5Monday through Friday
Next 10 runs…
  1. …………
  2. …………
  3. …………
  4. …………
  5. …………
  6. …………
  7. …………
  8. …………
  9. …………
  10. …………

Cron uses the time zone of the machine it runs on; servers and cloud schedulers often use UTC.

What is a cron expression?

A cron expression is a short line of five fields that tells a scheduler when to run a job: minute, hour, day of the month, month and day of the week, separated by spaces. A * means “every”, so 30 2 * * 1 reads “At 02:30, on Mondays”. The name comes from cron, the Unix program that runs scheduled jobs; the file that lists them is the crontab (cron table). Java schedulers like Quartz and Spring use the same idea with a seconds field in front.

How to use it

  1. Type or paste an expression, or press one of the common schedules to start from one.
  2. What it means says it in plain English, then field by field: what you wrote and which values it matches.
  3. Next 10 runs lists when it runs next, with the date, the time and how long until then. Pick the time zone: your own (Local), UTC, or any other. The tool remembers the zone and the format.
  4. Format is Auto by default: 5 fields are crontab, 6 or 7 fields with a ? are Quartz, and 6 without one are Spring. Pick one yourself if Auto guesses wrong. If something's off, the message says which field and why, and the problem is underlined in red.

The five fields

FieldAllowed valuesExample
Minute0–5930
Hour0–232
Day of month1–311,15
Month1–12 or JAN–DECJAN-MAR
Day of week0–7 or SUN–SAT (0 and 7 are both Sunday, 1 = Monday)MON-FRI

Each field takes one value, or a combination of these:

CharacterMeaningExample and what it does
*every value* in the hour field: every hour
,a list1,15: the 1st and the 15th
-a range, both ends included9-17: 9 through 17
/a step: every nth value of * or of a range*/15 in the minute field: 0, 15, 30, 45
namesthree-letter month and day names, in any casemon-fri, JAN,JUL

Common cron expressions

The meaning and the next runs below are what this tool shows, worked out from Friday 20 November 2026, 10:00 UTC.

ExpressionWhat it meansNext runs (UTC)
* * * * *Every minuteFri 20 Nov 10:01, Fri 20 Nov 10:02, Fri 20 Nov 10:03
*/5 * * * *Every 5 minutesFri 20 Nov 10:05, Fri 20 Nov 10:10, Fri 20 Nov 10:15
*/15 * * * *Every 15 minutesFri 20 Nov 10:15, Fri 20 Nov 10:30, Fri 20 Nov 10:45
0 * * * *Every hour, on the hourFri 20 Nov 11:00, Fri 20 Nov 12:00, Fri 20 Nov 13:00
0 */2 * * *Every 2 hours, on the hourFri 20 Nov 12:00, Fri 20 Nov 14:00, Fri 20 Nov 16:00
0 0 * * *At 00:00, every daySat 21 Nov 00:00, Sun 22 Nov 00:00, Mon 23 Nov 00:00
0 9,17 * * *At 09:00 and 17:00, every dayFri 20 Nov 17:00, Sat 21 Nov 09:00, Sat 21 Nov 17:00
0 9 * * 1-5At 09:00, Monday through FridayMon 23 Nov 09:00, Tue 24 Nov 09:00, Wed 25 Nov 09:00
*/15 9-17 * * 1-5Every 15 minutes from 09:00 through 17:45, Monday through FridayFri 20 Nov 10:15, Fri 20 Nov 10:30, Fri 20 Nov 10:45
0 22 * * 5At 22:00, on FridaysFri 20 Nov 22:00, Fri 27 Nov 22:00, Fri 4 Dec 22:00
0 0 * * 0At 00:00, on SundaysSun 22 Nov 00:00, Sun 29 Nov 00:00, Sun 6 Dec 00:00
0 0 1 * *At 00:00, on the 1st of the monthTue 1 Dec 00:00, Fri 1 Jan 2027 00:00, Mon 1 Feb 2027 00:00
30 4 1,15 * *At 04:30, on the 1st and 15th of the monthTue 1 Dec 04:30, Tue 15 Dec 04:30, Fri 1 Jan 2027 04:30
0 0 1 1 *At 00:00, on January 1stFri 1 Jan 2027 00:00, Sat 1 Jan 2028 00:00, Mon 1 Jan 2029 00:00

Shortcuts

Most crons (cronie, Vixie cron and its family on Linux and macOS) also take a word instead of the five fields:

ShortcutSame asWhat it means
@yearly or @annually0 0 1 1 *At 00:00, on January 1st
@monthly0 0 1 * *At 00:00, on the 1st of the month
@weekly0 0 * * 0At 00:00, on Sundays
@daily or @midnight0 0 * * *At 00:00, every day
@hourly0 * * * *Every hour, on the hour
@reboot(no fields)At startup: once each time cron starts (usually when the machine boots)

Day of month and day of week together

When both day fields are set, classic cron runs the job when either one matches, not both. 0 0 1 * 1 means “At 00:00, on the 1st of the month or on Mondays”: every Monday, plus the 1st of each month. It's a common surprise.

One more rule from the original cron code (cronie and Vixie cron still have it): a day field that starts with *, like */2, counts as “every day” for this rule, so then both fields must match. 0 0 */2 * 1 means “At 00:00, on every 2nd day of the month, starting on the 1st, if it's a Monday”. BusyBox's cron runs that on either one.

Spring always needs both (0 0 0 1 * MON is the 1st only when it's a Monday), and Quartz avoids the question: one of the two day fields must be ?.

crontab, Quartz and Spring

crontabQuartzSpring
Fields56 or 7: seconds first, optional year last6: seconds first
Day of week numbers0–7, 0 and 7 are Sunday1–7, 1 is Sunday0–7, 0 and 7 are Sunday
Both day fields seteither one matchesnot allowed: one of them must be ?both must match
L, W, #noyesyes
Ranges like FRI-MONnoyes, they wrap aroundno
Shortcuts@daily …, @rebootnone@daily … (no @reboot)

The extra Quartz and Spring characters, in the day fields:

ExpressionWhat it means
0 15 10 L * ?At 10:15, on the last day of the month
0 0 12 1W * ?At 12:00, on the weekday nearest the 1st of the month
0 0 12 ? * 6#3At 12:00, on the third Friday of the month
0 15 10 ? * 6LAt 10:15, on the last Friday of the month
0 0 12 ? * MON-FRIAt 12:00, Monday through Friday

Careful with numbers in the day of week: Quartz's 6 is Friday, Spring's 6 is Saturday. Names (FRI) mean the same everywhere.

Time zones and daylight saving

Cron runs in the time zone of the machine it runs on. Servers, containers and cloud schedulers often use UTC, so check which zone yours uses and pick it here.

Where clocks change for daylight saving, a time can be skipped or happen twice, and schedulers handle that differently. What each one really does, in New York in 2026 (this tool shows the same):

A daily job …crontab (cronie)QuartzSpring
at 02:30 on 8 March (clocks jump from 02:00 to 03:00)03:00 (UTC-04:00)no run that dayno run that day
at 01:30 on 1 November (clocks go back from 02:00 to 01:00)01:30 (UTC-04:00)01:30 (UTC-05:00)01:30 (UTC-04:00), 01:30 (UTC-05:00)

Jobs that run every hour or more often in cron (minute or hour field starting with *) skip the missing hour and run in both copies of the repeated one. If a job must run exactly once a day, schedule it outside 01:00–03:00 or run cron in UTC.

Common errors

  • 75 * * * *: “Minute is 0–59: 75 is too big.”
  • */5 * * *: “A cron expression has 5 fields (minute hour day month weekday), or 6–7 with seconds (Quartz, Spring). This one has 4.”
  • 0 0 12 * * MON as Quartz: “Quartz needs ? in exactly one of the two day fields: day of month or day of week. E.g. 0 0 12 ? * MON or 0 0 12 1 * ?”
  • 0 0 12 ? * MON as crontab: “? is Quartz and Spring syntax. In crontab, write * for “any”.”
  • 5/15 * * * * as crontab: “crontab needs * or a range before a step: write 5-59/15 (Quartz and Spring read 5/15 that way).”

FAQ

Why didn't my cron job run?

Check the time zone first: cron uses the machine's zone, often UTC, so 0 9 * * * may run at 09:00 UTC, not 09:00 where you are. Then check the day fields (with both set, cron runs on either one), and whether the time falls in a daylight-saving change. Beyond the schedule: the cron service must be running, the command needs full paths (cron starts with a minimal PATH), and in a crontab file % must be written \%.

What does */5 mean?

A step: every 5th value of the field, starting at its first value. In the minute field, */5 is 0, 5, 10 … 55, so every 5 minutes. 10-30/5 is 10, 15, 20, 25 and 30. A step that doesn't divide the range evenly restarts each hour: */25 runs at 0, 25 and 50, then again at 0.

Does @reboot work here?

It's explained, but it has no run times: @reboot runs once each time the cron service starts, which is usually when the machine boots. Not every cron has it; Spring and Quartz don't.

How do I run a job every 30 seconds?

Classic cron can't go below a minute. Quartz and Spring can: */30 * * * * ? (Quartz) or */30 * * * * * (Spring). With crontab, a common workaround is two jobs a minute, one of them starting with sleep 30;.

What's the difference between cron and crontab?

cron is the program that runs scheduled jobs; crontab is the table of jobs (edited with crontab -e), one per line: five schedule fields, then the command. You can paste a whole line here: the tool reads the schedule and shows the rest as the command.

Is my expression uploaded?

No. The tool reads it and works out the run times right here in your browser, with your browser's own time-zone data; we never upload, log or store your expression. Only the format and the time zone you pick are remembered, on this device. See the privacy page.