This cron expression generator turns a schedule into a five-field cron line, explains any cron line in plain English and lists the next ten times it will run. Type an expression, or pick a preset such as every 15 minutes or weekly on Monday at 08:30, and press Explain. The run times are shown in your own time zone.
Cron is the classic scheduler on Linux and Unix systems, and the same five-field syntax is used by many job runners, cloud schedulers and CI tools. The syntax is short, which also makes it easy to get wrong. A quick read-back in words and a list of real dates is the fastest way to catch a mistake before a job runs at the wrong hour.
The five fields of a cron expression
A standard crontab entry has five time fields, read from left to right: minute, hour, day of month, month and day of week [1]. The allowed values are 0 to 59 for the minute, 0 to 23 for the hour, 1 to 31 for the day of month, 1 to 12 for the month and 0 to 7 for the day of week, where both 0 and 7 mean Sunday [1].
| Field | Allowed values | Example |
|---|---|---|
| Minute | 0-59 | 30 |
| Hour | 0-23 | 8 |
| Day of month | 1-31 | 1,15 |
| Month | 1-12 or JAN-DEC | */3 |
| Day of week | 0-7 or SUN-SAT | MON-FRI |
Cron syntax: stars, lists, ranges and steps
- Asterisk (*) means every value in the field [1].
- Range (8-11) is inclusive, so it covers 8, 9, 10 and 11 [1].
- List (1,2,5,9) is a set of numbers or ranges separated by commas [1].
- Step (*/2 or 0-23/2) skips values inside the range [1].
- Names such as MON-FRI or JAN-MAR are the first three letters of the day or month, in any case [1].
How to use the cron expression generator
- Type a five-field expression in the first box, or choose a preset.
- For a preset, fill in the numbers it asks for and press "Use this preset".
- Press Explain to read the plain-English meaning.
- Check the list of the next ten runs. Each line shows the weekday, date and time in your time zone.
- Copy the expression into your crontab, scheduler or pipeline file.
Day of month and day of week together
One rule surprises many people. When both the day-of-month and the day-of-week fields are restricted, the job runs when either one matches [1]. The entry 30 4 1,15 * 5 runs at 04:30 on the 1st and the 15th of each month and also on every Friday [1]. If you want "the first Friday", cron alone cannot say it, and you need a check inside the script.
Next run times and time zones
The next-run list uses a JavaScript cron parser that evaluates the schedule in a given time zone and handles daylight-saving changes [3]. This tool uses the time zone your browser reports and prints it under the list. A server may run in UTC while you sit in another zone, so compare the zone of the machine that runs the job with the zone shown here. A job set for 02:30 can also be skipped or repeated on the night the clocks change.
Plain-English explanation
The explanation comes from the cRonstrue library, which converts a cron expression into a readable sentence [2]. It accepts five, six and seven fields, but this page asks for five so that the text, the run list and standard crontab all agree. Times are written on a 24-hour clock to avoid AM and PM confusion.
Worked examples
| Expression | Meaning |
|---|---|
| */15 * * * * | Every 15 minutes |
| 0 9 * * 1-5 | At 09:00 on Monday to Friday |
| 30 8 * * MON | At 08:30 every Monday |
| 0 0 1 * * | At 00:00 on day 1 of the month |
| 0 */2 * * * | At minute 0 of every second hour |
Common cron mistakes
- Using six fields with seconds in a system that expects five. The page flags a wrong field count.
- Writing */5 in the hour field when you meant every five minutes. The minute field is the first one.
- Forgetting that day 0 and day 7 are both Sunday [1].
- Assuming the server time zone matches yours.
- Setting a day of month and a weekday at once and expecting both to be required.
Choosing a preset
The presets cover the schedules people ask for most. "Every N minutes" fills only the minute field with a step, so 15 gives */15 * * * *. "Every N hours" runs at the minute you choose every N hours from midnight, so 2 and minute 30 give 30 */2 * * *. "Hourly" runs at one minute past every hour. "Daily" needs an hour and a minute. "Weekly" adds a weekday name, and "Monthly" adds a day of the month from 1 to 31. A preset only writes the expression for you; you can edit the result by hand before you press Explain.
Months with fewer days need care. A monthly job on day 31 does not run in a month with only 30 days, and day 29, 30 and 31 are skipped in some years. For a job that must run once every month, pick a day from 1 to 28.
Testing a schedule before you rely on it
- Read the plain-English line aloud and compare it with what you wanted.
- Look at the first run in the list. If it is hours later than you expect, check the hour field and the time zone.
- Count the runs inside one day or week to be sure the frequency is right.
- Add a note to your crontab with the intended meaning, because a bare expression is hard to read months later.
What next
Use this often? Add Cron Express to your Home screen.
Frequently asked questions
What is a cron expression generator?
A cron expression generator builds a cron schedule line from simple choices, such as every 15 minutes or weekly on Monday. This one also explains the line in words and lists the next ten run times.
How many fields does a cron expression have?
A standard crontab entry has five: minute, hour, day of month, month and day of week. Some tools add a seconds or year field, but this page works with five.
What does */5 mean in cron?
It means every fifth value in that field. In the minute field, */5 runs at minutes 0, 5, 10 and so on up to 55.
Which time zone do the run times use?
The time zone reported by your browser, shown under the list. If your server uses another zone, the real run times differ.
What happens when day of month and weekday are both set?
The job runs when either field matches, not only when both match. This surprises many people.
Was this tool helpful?
What went wrong?
We only receive the reason you pick, never what you typed into the tool.
Thanks for your feedback.