Cron Expression Helper

Build and validate standard 5-field cron expressions. Runs entirely in your browser.

Valid. minute 0, hour 9, day-of-month any, month any, day-of-week 1,2,3,4,5
Next 5 runs (your local time)
2026/10/28 09:00:00
2026/10/29 09:00:00
2026/10/30 09:00:00
2026/10/31 09:00:00
2026/11/1 09:00:00
Fields: minute hour day-of-month month day-of-week · "*" any · "," list · "-" range · "/" step · weekday 0 or 7 = Sunday

Runs are computed in your local timezone. Exact scheduler behavior may vary by cron implementation.

Build and decode five-field cron expressions with a plain-English explanation and a preview of the next run times, so a schedule mistake shows up before it reaches a server.

Reading the five fields

The fields are minute, hour, day of month, month and day of week, in that order. Each accepts a value, a range with a hyphen, a list separated by commas, or a step written with a slash. The expression 0 9 * * 1-5 means nine in the morning, Monday through Friday.

Sunday is both 0 and 7, which is a legacy inconsistency rather than a feature. Stars mean every value. The string */15 in the minute field means every fifteen minutes starting at zero.

The day-of-month and day-of-week trap

In classic cron, when both the day-of-month and day-of-week fields are restricted rather than starred, the job runs when either one matches. That is an OR, not an AND, and it surprises almost everyone.

So 0 0 13 * 5 does not mean the thirteenth of the month when it falls on a Friday. It means every thirteenth of the month, plus every Friday. If you need a specific combination, express it inside the script instead of the schedule.

Timezones and daylight saving

Cron runs in the timezone of the machine or the scheduler, which is frequently UTC on servers and local time on a laptop. A job that fires at nine in the morning in one environment fires at five in the afternoon in the other.

Daylight-saving transitions create two specific problems: a job scheduled in the skipped hour does not run that day, and a job scheduled in the repeated hour runs twice. Anything with a real-world deadline should be written against UTC and adjusted inside the job.

Frequently asked questions

Does this support six-field cron with seconds?
It targets the standard five-field form used by most Unix cron implementations and cloud schedulers. Quartz-style six-field expressions with a leading seconds field are a different format.
What does the next-runs preview use for a timezone?
Your browser's local timezone. If the job will run on a UTC server, mentally subtract the offset when checking.
Why did my job run at the wrong hour after a DST change?
Because the schedule is interpreted in local time and the local offset changed. Pin the schedule to UTC to make it stable year-round.