Cron Expression Builder & Parser
Write a cron expression, or build one from presets and the five fields, and see what it means in plain words together with its next run times. The tool uses a clearly documented 5-field dialect (minute, hour, day of month, month, day of week) and tells you exactly what is wrong when an expression is invalid. Everything runs in your browser.
Result
In plain words
Field by field
| Field | Value | Meaning |
|---|
Next run times
| # | In the chosen time zone | UTC |
|---|
Times that do not exist because clocks jump forward are skipped; a repeated time runs once.
Examples
Common schedules and what they mean:
| Expression | Meaning |
|---|---|
* * * * * | Every minute |
*/5 * * * * | Every 5 minutes |
0 * * * * | At the start of every hour |
0 9 * * 1-5 | Weekdays at 09:00 |
30 2 1 * * | At 02:30 on the 1st of every month |
0 0 * * 0 | Every Sunday at midnight |
0 0 1 1 * | Every 1 January at midnight |
0 8,20 * * * | Every day at 08:00 and 20:00 |
Formula & Methodology
This tool uses the classic 5-field cron dialect: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or names) and day of week (0–7 or names, where 0 and 7 are Sunday). Each field accepts a star, numbers, lists, ranges and steps. When both day of month and day of week are restricted, a day matches if either one matches, as in Vixie cron.
min hour dom mon dow| Syntax | Meaning |
|---|---|
* | Any value in the field |
5,10,15 | A list of values |
1-5 | A range, inclusive |
*/15 | A step through the whole field |
10-30/5 | A step within a range |
JAN, MON | Month and weekday names, in any case |
@daily | Shortcuts: @yearly, @monthly, @weekly, @daily, @midnight, @hourly |
Run times are calculated on the wall clock of the time zone you choose, including daylight saving time. This dialect is a common subset: cron systems differ, so check your scheduler’s documentation for extras such as seconds, years, L, W or #.
Notes and limitations
- Only 5-field expressions and the shortcuts @yearly, @annually, @monthly, @weekly, @daily, @midnight and @hourly are accepted. Seconds and year fields, ?, L, W, # and @reboot are reported as unsupported.
- Ranges cannot wrap around (22-2 is invalid); write 22-23,0-2 instead.
- A day-of-month and a day-of-week that are both restricted combine with “or”. If either field starts with a star, both must match.
- Cloud schedulers (such as Kubernetes, GitHub Actions or AWS) may use UTC, other fields or different rules. Match the time zone and dialect to your system.
- Run times assume the browser’s time-zone database. Wall-clock times skipped by a clock change do not run, and repeated times run once.
How to Use
- Type a cron expression, or choose a common schedule to start from.
- Edit the five fields if you prefer to build the expression piece by piece; the expression updates as you type.
- Read the plain-language summary and the field-by-field table. If the expression is invalid, the message names the field and value.
- Choose the time zone and the number of runs to preview the next run times.
- Copy the expression.
Frequently Asked Questions
What do the five fields of a cron expression mean?
From left to right: minute, hour, day of the month, month and day of the week. A star means every value; for example 0 9 * * 1-5 means minute 0 of hour 9 on every weekday (Monday to Friday).
What does */5 mean?
A step: every 5 units starting from the first value of the field. In the minute field */5 means at minutes 0, 5, 10 and so on up to 55.
Why does my day-of-month and day-of-week schedule run more often than I expected?
In standard cron, when both fields are restricted, a day matches if either field matches. So 0 0 13 * 5 runs on the 13th and on every Friday. To run only on Friday the 13th, use a scheduler that supports AND, or check the day inside your job.
Which time zone does cron use?
It depends on the system: many servers use UTC, others the server’s local time. This tool lets you choose the zone to preview run times; pick the one your scheduler uses.
Is my expression sent anywhere?
No. Parsing and the run-time calculation happen in your browser and nothing you enter is uploaded or sent to analytics.
Last updated: