Cron Expression Builder
At 09:00 from Monday through Friday
Standard 5-field cron: minute hour day-of-month month day-of-week. Month names (JAN–DEC) and day names (MON–SUN) work in any case. Seconds, L, W, # and @macros are not supported.
What this cron expression builder does
This tool checks a standard five-field cron expression, describes the schedule in words and lists the next five times it would fire. You can type the whole expression or edit each field. It is meant for crontab entries and for schedulers that use the same syntax, such as Kubernetes CronJobs and GitHub Actions schedules. Syntax it does not support is reported as invalid rather than guessed at.
Building a schedule
- Pick a preset under the expression (Every 5 minutes, Hourly, Daily at 09:00 and so on) or type an expression. The default, 0 9 * * 1-5, is 09:00 on weekdays.
- Edit the Minute, Hour, Day of month, Month and Day of week boxes. Each shows its range; an empty box counts as *. The expression and the boxes stay in sync.
- If the expression is not valid, a message appears a moment after you stop typing and says which field is wrong; the result keeps the last valid schedule, dimmed.
- Read the schedule in words and the next 5 runs, shown in your browser's timezone. Copy next to the expression copies the expression only; Copy runs copies the run times; Reset restores the default.
How the fields and next run times are calculated
The five fields are minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC) and day of week (0–6 or SUN–SAT, with 0 or 7 = Sunday). Each accepts *, a number or name, a range a-b, a step */n or a-b/n, and comma-separated lists such as 0,30 or MON,WED,FRI. Steps count from the start of the range and restart in each hour or day: */7 in the minute field fires at :56 and then at :00.
For the run list, the tool starts at the next whole minute and checks each minute in local time until five match or about four years have been searched. Minute, hour and month must all match. If day of month and day of week are both restricted, a day matches when either field matches; if one of them is *, only the other is checked. On the day clocks go forward, times in the skipped hour are not listed; on the day they go back, the repeated hour is listed once.
This is the POSIX five-field format, also used by Vixie cron and cronie (crontab(5)), which also add macros such as @daily. Quartz puts a seconds field first, allows an optional year, numbers weekdays 1–7 from Sunday and adds ?, L, W and #. AWS EventBridge rules use six fields, minute to year, with Quartz-style characters, and run in UTC.
Worked example: every 15 minutes during working hours
Expression: */15 9-17 * * 1-5. Reference time: Friday 16 October 2026, 17:40 local time.
Fields expand to minutes 0, 15, 30, 45; hours 9 to 17; days of week 1 to 5 (Monday to Friday). Hour 17 covers 17:00–17:59, so 17:45 still matches.
The search starts at 17:41. Saturday and Sunday fail the weekday field, so the list is: Fri 16 Oct 2026 17:45, then Mon 19 Oct 2026 09:00, 09:15, 09:30 and 09:45. To stop at 17:00, use two entries: */15 9-16 * * 1-5 and 0 17 * * 1-5.
What this builder does not handle
- ?, L, W, #, macros such as @daily, full names (MONDAY) and start/step forms such as 5/15 are rejected. Write 5-59/15 instead.
- There are no seconds or year fields, so six- and seven-field expressions are rejected.
- There is no timezone setting. Servers often run cron in UTC, and GitHub Actions always does.
- cronie runs fixed-time jobs from a skipped daylight saving hour right after the change; this list omits them.
- An expression that never matches, such as 0 0 30 2 *, is marked Valid but lists no runs; 0 0 29 2 * may list fewer than five within the four-year search.
Cron questions
What is the cron expression for every 5 minutes, every hour or every day?
Every 5 minutes: */5 * * * *. Every hour on the hour: 0 * * * *. Every day at midnight: 0 0 * * *. Every day at 02:30: 30 2 * * *. Weekdays at 09:00: 0 9 * * 1-5. Every Sunday at 03:00: 0 3 * * 0. The 1st of every month at 00:00: 0 0 1 * *. Paste any of them above to check the next five run times.
Does */15 mean every 15 minutes from when the job is saved?
No. It means minutes 0, 15, 30 and 45 of every hour by the clock, regardless of when the crontab was installed.
Is Sunday 0 or 7?
POSIX uses 0 for Sunday and 6 for Saturday. Vixie cron and cronie also accept 7, and this tool accepts 7 and SUN for Sunday as well. Quartz and AWS EventBridge use 1–7 with 1 for Sunday, so the same number means a different day there.
Why does 0 9 1 * 1 run on Mondays that are not the 1st?
When day of month and day of week are both restricted, cron runs the job on days that match either field, so this expression runs at 09:00 on the 1st of every month and on every Monday. Standard cron has no way to require both. For the first Monday of the month, use 0 9 1-7 * * and test the weekday in the command: [ "$(date +\%u)" = 1 ] && your-command. In a crontab line, % must be written as \%.
How do I convert a Quartz, Spring or AWS EventBridge cron expression?
Drop the extra fields and replace ? with *. Quartz and Spring @Scheduled put a seconds field first, so Quartz 0 0 12 * * ? becomes 0 12 * * *. AWS cron(0 18 ? * MON-FRI *) also ends with a year field and becomes 0 18 * * 1-5 (in UTC). Check day-of-week numbers too: Quartz counts Sunday as 1.
How do I run a job every 90 minutes?
One expression cannot, because minute steps restart each hour. Use 0 */3 * * * for 00:00, 03:00 … 21:00 and 30 1-22/3 * * * for 01:30, 04:30 … 22:30.
Related tools
Related articles
- How to Read and Write Cron Expressions (5-Field POSIX)
Learn how to read, write, and debug 5-field POSIX cron expressions with a visual builder, plain-English explanations, and a live preview of the next runs.