Cron Expression Builder and Validator
Build a cron schedule from the dropdowns and presets, or type an expression directly. The page describes it in plain English using the cronstrue library and lists the next five run times using cron-parser, in your browser's time zone.
Presets
Human-readable
Every minute
Next 5 run times (local time)
- 1 11/16/2026, 12:26:00 PM
- 2 11/16/2026, 12:27:00 PM
- 3 11/16/2026, 12:28:00 PM
- 4 11/16/2026, 12:29:00 PM
- 5 11/16/2026, 12:30:00 PM
Related Developer Tools
Runs in your browser: your files and text are not uploaded. Free, no account needed.
Last updated: · Reviewed by the QuickTooly Team
Cron syntax
The Five Fields
Standard Unix mode uses five fields separated by spaces: minute hour day-of-month month day-of-week.
- Minute: 0–59. Hour: 0–23. Day of month: 1–31.
- Month: 1–12 or JAN–DEC. Day of week: 0–7, where both 0 and 7 mean Sunday, or SUN–SAT.
*any value,,a list (1,15),-a range (9-17),/a step (*/15,0-30/10).Lin day of month means the last day;5Lin day of week means the last Friday.1#2means the second Monday.- Shortcuts such as
@dailyare accepted when typed, but the dropdowns do not follow them.
There is no seconds field in the builder. If you type six fields in Standard mode, both libraries read the first one as seconds, so */10 * * * * * means every 10 seconds. A standard Linux crontab does not accept that.
Worked Examples
0 9 * * 1-5: 09:00, Monday to Friday.*/15 9-17 * * 1-5: every 15 minutes from 09:00 to 17:45 on weekdays. The hour range includes 17, so the last run is 17:45, not 17:00.0 0 L * *: midnight on the last day of each month.0 0 * * 5L: midnight on the last Friday of each month.0 9 * JAN,JUL MON-FRI: 09:00 on weekdays in January and July.
Common Mistakes
- Day of month and day of week together: when both are restricted, the job runs when either matches.
30 2 1-7 * 1runs on days 1 to 7 and on every Monday, not only on the first Monday. Use30 2 * * 1#1if your scheduler supports#. - Time zone: the preview uses your browser's time zone. Many servers run cron in UTC.
- Dates that never occur:
0 0 31 2 *(31 February) shows the error "Invalid explicit day of month definition". - Unsupported extensions:
Land#work here but not in classic Vixie cron, which most Linux crontabs use. Check your scheduler's documentation. - Field count: Quartz and Spring expect a seconds field first. Pasting a five-field expression there shifts every field by one.
AWS EventBridge Mode
AWS mode adds a sixth field, Year. In EventBridge, either day of month or day of week must be ?, and day of week runs from 1 (Sunday) to 7 (Saturday), which is why the Mon–Fri preset becomes 2-6. EventBridge writes the schedule as cron(0 9 ? * 2-6 *); the builder gives you the part inside the brackets.
For the description and the run preview, the page converts the expression to Unix cron: ? becomes *, day of week moves from 1–7 to 0–6, and the Year field filters the next run times. So 0 9 ? * 2-6 * is described and previewed as 09:00, Monday to Friday. The preview is in your browser's time zone, while EventBridge schedules run in UTC unless you set a time zone on the schedule.
Cron schedules often sit in YAML files, such as GitHub Actions workflows or Kubernetes CronJobs; the YAML to JSON Converter helps check those files.
Cron Questions
Does the builder support a seconds field?
Not in the dropdowns. If you type six fields in Standard mode, the first is read as seconds, so */10 * * * * * runs every 10 seconds. A standard Linux crontab does not accept seconds.
Which time zone are the next run times in?
Your browser's local time zone. If the job runs on a server set to UTC, convert the times or set the time zone in your scheduler.
Why does 30 2 1-7 * 1 run on every Monday?
When both day of month and day of week are restricted, cron runs the job when either one matches. This expression runs at 02:30 on days 1 to 7 and on every Monday.