Does this support 6-field cron (with seconds)?

Most schedulers use standard 5-field cron. Quartz-style 6- and 7-field formats vary by platform — check your target before pasting.

What timezone are the next-run previews in?

Your local browser timezone. Remember that many schedulers (crontab, most Kubernetes clusters) run in UTC by default.

Classic cron treats them as OR: the job runs when either field matches. Set one of them to * unless you truly want OR semantics.

Generators

Build cron expressions visually. See plain-English descriptions, preview the next 5 run times, or paste an existing expression to parse it.

Expression

Minute

Hour

Day (Month)

Month

Day (Week)

Paste an existing expression

Minute

Every

Hour

Every

Day of Month

Every

Month

Every

Day of Week

Every

Every minute

How to build a cron expression

Compose a cron expression field-by-field and preview the next run times in plain English.

Set each field
Edit minute, hour, day-of-month, month, and day-of-week. Use *, ranges, lists, and step values.
Read the human description
The expression translates to plain English automatically so you can catch mistakes fast.
Preview upcoming runs
See the next five scheduled executions to confirm the schedule matches your intent.
Copy the expression
Paste the cron string into crontab, Kubernetes CronJob, GitHub Actions, or your scheduler of choice.

? Does this support 6-field cron (with seconds)?: Most schedulers use standard 5-field cron. Quartz-style 6- and 7-field formats vary by platform — check your target before pasting.
? What timezone are the next-run previews in?: Your local browser timezone. Remember that many schedulers (crontab, most Kubernetes clusters) run in UTC by default.
? Why do day-of-month and day-of-week together behave oddly?: Classic cron treats them as OR: the job runs when either field matches. Set one of them to * unless you truly want OR semantics.