A standard Linux crontab expression has five fields, in this order: minute, hour, day of month, month, and day of week. Read each field against the values it allows, then confirm the syntax and calendar rules in the scheduler where the job will run: Spring and Quartz use different six-field forms, and cron dialects are not fully interchangeable.
How do I read a cron expression?
Start with the five-field format used by standard Linux crontab. The command to run comes after the schedule; it is not one of the five time fields.
As an Amazon Associate I earn from qualifying purchases.
| Position | Field | Standard Linux crontab values |
|---|---|---|
| 1 | Minute | 0–59 |
| 2 | Hour | 0–23 |
| 3 | Day of month | 1–31 |
| 4 | Month | 1–12, or month names |
| 5 | Day of week | 0–7, where 0 or 7 is Sunday, or weekday names |
The field order and ranges are defined in the Linux crontab(5) manual. To decode an expression, mark off its fields from left to right and interpret each one separately.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For example, 30 8 * * 1-5 means minute 30, hour 8, every day of the month, every month, and weekdays 1 through 5: 08:30 on weekdays in standard Linux crontab. It describes matching calendar fields; it does not guarantee a run regardless of daemon status, host time, or system conditions. System crontab files may include an additional user field before the command, so distinguish those from a user’s crontab.
#1 Best Overall
What do the asterisk, comma, hyphen, and slash mean in cron?
These operators combine with the allowed values of their field. The examples below use standard Linux crontab syntax.
| Syntax | Meaning | Example |
|---|---|---|
* |
Every allowed value in that field | * in the minute field selects every minute. |
, |
A list of values | 0,30 in the minute field selects minute 0 and minute 30. |
- |
An inclusive range | 9-17 in the hour field selects hours 9 through 17. |
/ |
A step through values | */15 in minutes selects 0, 15, 30, and 45; 0-23/2 selects every other hour from 0 through 23. |
Linux crontab also permits month and weekday names, such as jan-mar or mon,wed,fri. Names can make schedules easier to inspect and can help avoid weekday-number mismatches when moving an expression between some schedulers.
Combined example: 0,30 9-17 * * 1-5 selects minute 0 and 30 during hours 9 through 17, on weekdays, in standard Linux crontab. Check the expression against the exact scheduler and version you will deploy; accepting the same punctuation does not mean two systems interpret every field the same way.
What does */5 * * * * mean?
In standard Linux crontab, the first field is minutes, so */5 selects minutes 0, 5, 10, 15, and so on through 55. The four remaining asterisks select every allowed hour, day of month, month, and day of week. The schedule therefore matches every five minutes, as evaluated by the crontab scheduler.
This is a field pattern, not a general-purpose timer that waits five minutes after the previous run finishes. Standard Linux crontab entries are examined once per minute. If a run takes longer than expected or a system is unavailable, the expression itself does not establish how missed or overlapping work is handled.
How do I schedule a cron job every day at midnight?
For standard Linux crontab, use 0 0 * * *: minute 0, hour 0, every day of the month, every month, and every day of the week. Put the command after the schedule, separated by whitespace. This identifies midnight according to the scheduler’s applicable time context; the expression alone does not settle time-zone or daylight-saving behavior across implementations.
What happens when both day-of-month and day-of-week are set?
In standard Linux crontab, the minute, hour, and month must match. When both day-of-month and day-of-week are restricted (neither is simply an unrestricted wildcard), either day field matching can trigger the entry. In that case, do not read the expression as requiring both calendar-day conditions simultaneously.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThis rule is specific to the crontab behavior documented by the Linux manual. If a schedule targets another implementation, consult that scheduler’s reference rather than assuming the same day-field logic.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why does my cron expression work in Spring but not Quartz?
Field count is a useful first diagnostic. Standard Linux crontab has five time fields, while Spring and Quartz use six fields with seconds first. Quartz also documents an optional year field. An expression copied between systems can therefore shift every field’s meaning or fail validation.
| Scheduler or reference | Expression shape | Portability issue |
|---|---|---|
| Standard Linux crontab | Five fields: minute, hour, day of month, month, weekday | Sunday may be 0 or 7; day-of-month/day-of-week matching follows crontab rules. |
| Spring Framework | Six fields, with seconds first | Numeric weekday convention follows crontab, including Sunday as 0 or 7. |
| Quartz | Six fields, with seconds first, plus an optional year field in the documented format | Numeric weekday numbering differs from Spring and crontab; Quartz also supports additional constructs. |
These formats and conventions are described in the Spring Framework scheduling reference and the Quartz.NET 4.x cron expression reference. When moving a schedule between Spring and Quartz, weekday names such as MON can avoid the specific mismatch caused by different numeric weekday numbering. They do not guarantee that every other part of the expression is portable.
Quartz-only constructs to recognize
Quartz’s documented grammar includes constructs that should not be treated as universal cron syntax. In Quartz, ? means no specific value in a day field; the reference also documents L, W, and # for additional day-related scheduling patterns. Quartz describes * as selecting all values, - as a range, , as additional values, and / as increments. Use these special forms only when the target Quartz implementation and version support them.
How to check an expression before using it
- Identify the scheduler and version first; do not infer the dialect from the word “cron.”
- Count the time fields. Five often indicates a Unix-style format and six may indicate seconds first, but confirm the documented format rather than relying on field count alone.
- Read each field in its documented position and check allowed ranges, weekday numbering, and day-of-month/day-of-week rules.
- Validate the expression in the exact scheduler where it will run. Syntax validation does not establish that the command, environment, permissions, daemon, or host state will allow successful execution.
The references cited here do not establish one universal rule for daylight-saving transitions. Exact behavior depends on the implementation, time zone, and version, so check the target scheduler’s documentation when a job’s timing around clock changes matters.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
