Cron Expression Explainer

Explain five-field cron schedules with month or weekday names and common schedule macros.

On-device No sign-up Free to use

Explain controls

Showing an example. Edit to see your own.

?

Five fields in order: minute, hour, day of the month, month, day of the week.

?

Each run is printed in this browser's local time zone.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Read a weekday schedule for every quarter hour from 09:00 through 17:45.

The expression matches minutes 00, 15, 30 and 45 during hours 09 through 17, Monday through Friday. The next five matching times depend on the device’s current date and local time zone.

Loading the tool. Your result will appear here.

https://usefreetools.net/cron-expression-explainer · 20 November 2026

Was this helpful?

How to use Cron Expression Explainer

  1. Enter a five-field expression such as */15 9-17 * * 1-5, a supported shortcut such as @daily, or open Build an expression with controls.
  2. Choose three, five or eight runs to preview. The page uses this device’s current clock and time zone; there is no separate reference-time or zone selector.
  3. Read the field explanations, day-matching rule and next-run list. Compare the displayed zone and supported syntax with the cron service where you plan to use the expression.

Example: Cron Expression Explainer

Read a weekday schedule for every quarter hour from 09:00 through 17:45.

You add
Cron expression: */15 9-17 * * 1-5; Runs to preview: 5
You get
The expression matches minutes 00, 15, 30 and 45 during hours 09 through 17, Monday through Friday. The next five matching times depend on the device’s current date and local time zone.

Options

Expression syntax
The fields are minute, hour, day of the month, month and day of the week. Use numbers, ranges, steps or comma lists. JAN through DEC and SUN through SAT are accepted in their corresponding fields; Sunday can be 0 or 7.
Local preview
The preview scans forward from the device’s current minute and prints matches in its local time zone. Changing Runs to preview selects three, five or eight matches, searched over at most 366 days.
Guided builder
Open Build an expression with controls. For each field, choose every value, specific values, a range or every N values, then use the expression. Existing five-field validation applies. If both day fields are restricted, a match in either field runs the job.
Schedule shortcuts
@yearly and @annually expand to January 1 at midnight; @monthly to the first day of each month; @weekly to Sunday midnight; @daily and @midnight to each midnight; @hourly to minute zero. @reboot is unsupported.

Supported inputs and limits

  • Supports five numeric cron fields with *, ranges, steps and comma lists, three-letter month and weekday names, and the listed schedule shortcuts.
  • Seconds/year fields, @reboot, L, W, # and ? operators, Quartz and AWS dialects are unsupported.
  • The preview uses the device’s clock and local time zone and stops at the chosen number of matches or 366 days.
  • A rare valid schedule can have no match inside that window.
  • It does not connect to a server, read a crontab or confirm that a command is installed or running.
More details

Check the target scheduler’s time zone and daylight-saving rules separately.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Reading a cron line left to right

A cron line asks five questions in order: which minute, which hour, which day of the month, which month, and which day of the week. Each answer is a set, written as one number, a range, a list, or a step that walks through a range. The job runs on every minute that satisfies all five sets at once, with one exception: when both day fields are restricted, a match in either field is enough. That exception explains most schedules that fire more often than their author expected. Local time adds the second trap, since a server in another zone runs the same expression at a different hour.

Questions about Cron Expression Explainer

Why was my six-field expression refused?

A six-field expression adds seconds, which only some cron implementations accept. This page sticks to the five-field form so an explanation here matches a standard crontab. Remove the seconds field and paste it again.

How do the day-of-month and day-of-week fields combine?

In the usual cron rule, when both fields are restricted the job runs on days that match either one. The field table states which case applies, and it matters: 0 0 1 * 1 runs on the first of the month and on every Monday, not only on a Monday that is also the first.

Why do the preview times not match my server?

The preview uses this device’s local time zone. Your cron service may use another zone or implementation. Compare the displayed zone with its configuration before relying on a wall-clock time.

Does the preview handle daylight saving changes?

The preview walks through actual elapsed minutes and reads the browser’s local calendar fields, so local offsets can change during the search. A real cron service may handle repeated or skipped times differently. Check its documented behavior before scheduling a job near a clock change.

Can it explain @daily or @reboot?

It accepts @daily and @midnight as 0 0 * * *, as well as the other listed date-based shortcuts. It cannot predict @reboot because that depends on the scheduler starting.

Page updated · Project managed by Tony Hines · Report a problem with Cron Expression Explainer