Cron Parser

Explain a five-field cron expression, or an @macro, in UTC.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

Each field is read as minute, hour, day of month, month, and day of week. A macro is expanded to the same kind of description.

The page does not install a job or contact a server. An expression it does not understand is reported on the page.

How to use it

  1. Paste five cron fields or an @macro such as @daily.
  2. Explain the expression.
  3. Read the UTC description. Nothing is scheduled.

Limitations

Five fields labeled, or a macro expanded first

Macros become five fields, and names of months do not

Five fields are labeled, or a macro is expanded to five fields. The recognized macros are yearly, annually, monthly, weekly, daily, and hourly, written with the leading at-sign. Yearly and annually both become minute 0, hour 0, day-of-month 1, month 1, and day-of-week star. Monthly, weekly, daily, and hourly expand to the usual midnight or first-day forms. A macro this list does not contain, including reboot, is not expanded. It is parsed as fields and will fail the five-field count.

Without a macro, the paste is split on whitespace and must produce exactly five fields: minute, hour, day of month, month, and day of week. A sixth field for seconds is rejected. The page then checks each field. A star is allowed. A question mark is allowed as a whole field. Lists of numbers, ranges, and steps are allowed when the numbers fall inside the field’s range: minutes 0 through 59, hours 0 through 23, day of month 1 through 31, month 1 through 12, and day of week 0 through 7. A step has to be a positive whole number. A month name or a day name such as MON is rejected, because the checker wants digits. The result reprints each field with its label. It does not compute the next time the expression would fire.

The UTC sentence is a label, not a conversion

The page adds a line that times are described in UTC. It does not shift the fields into another zone, and it does not apply daylight-saving rules. Day-of-week 7 is inside the allowed range. The page does not explain that some systems treat 7 as Sunday. It only checks the number. Quartz-style seconds, years, and special characters beyond this subset fail or are misread as ordinary fields. Stay inside the five-field subset.

What you do not get

There is no calendar of upcoming runs, no description like “every weekday at noon” generated from an arbitrary expression, and no check that day-of-month and day-of-week are a combination your scheduler accepts. The labeled fields are the whole answer. Use them to see that a macro expanded the way you expected, or that a numeric expression sits inside range.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.