Developer tool
Cron Expression Explainer
Cron expression explainer: read a five-field cron schedule in plain language, with lists, ranges and steps, and check each field's range. Nothing is uploaded.
Your file never leaves your device.
Runs locally in your browser
Your text is not uploaded.
Simple steps
How it works
- 01
Enter a five-field cron expression.
- 02
Review the field-by-field explanation.
- 03
Copy the schedule summary or adjust the expression.
The five fields
A cron expression has five fields separated by spaces: minute (0–59), hour (0–23), day of month (1–31), month (1–12) and day of week (0–7, where both 0 and 7 mean Sunday). * means every value, a-b a range, a,b,c a list, and */n or a-b/n a step.
For example, 30 2 * * 1-5 runs at 02:30 from Monday to Friday, and */15 9-17 * * * runs every 15 minutes from 09:00 to 17:45.
When both day fields are set
In the standard cron used by most Linux systems, if both the day of month and the day of week are restricted, the job runs when either one matches. 0 9 1 * 1 runs at 09:00 on the 1st of every month and also on every Monday. Many people expect both to have to match, so check this case carefully.
What the explainer does not cover
Month and weekday names (JAN, MON), shortcuts such as @daily and @reboot, and extensions such as L, W, # or a seconds field, used by Quartz and some cloud schedulers, are not accepted.
A schedule runs in the time zone of the server or service that executes it, often UTC. Around daylight-saving changes, a job set for a time that is skipped or repeated, such as 02:30, may not run or may run twice, depending on the scheduler.
Good to know
Frequently asked questions
Which cron format is used?
The explainer reads minute, hour, day of month, month, and day of week fields.
Are lists and steps supported?
The explanation recognizes wildcard, comma-separated list, range, and step syntax.
Does it include seconds?
No. This tool expects the common five-field cron format without a seconds field.
Which timezone does cron use?
The expression has no timezone by itself. Actual timezone behavior depends on the scheduler where it runs.
Is the expression sent to a server?
No. Validation and explanation run locally in your browser.