Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenFill in five fields or click a preset, then copy a cron expression with a short summary beside it.
Click hourly, daily, weekdays or monthly to fill all five fields.
Type *, numbers, ranges, lists or */n steps into any box.
Check the plain description under the expression.
Copy it into crontab, CI or a Kubernetes CronJob.
A backup script should run every weekday at 9:30 and you cannot remember whether the hour or the minute comes first. Cron Generator gives each of the five fields its own labelled box, so the order is never in doubt.
Five presets fill the fields in one click: every minute, hourly, daily at 9:00, weekdays at 9:00 and monthly on the 1st. After that, edit any field directly. Each box takes normal cron syntax, so * for every value, a single number, a range like 1-5, a list like 1,15 or a step like */10 all work. The expression updates as you type, and a short summary underneath describes it; 0 9 * * *, for instance, reads 'At 9:00'. Copy, Download and Clear buttons sit above the form.
The summary is a reading aid, not a validator. Values are not range-checked, so 75 in the minute box still produces an expression that crontab will reject. Day of week uses 0 for Sunday, and when both day of month and day of week are set, most cron implementations run the job when either one matches. To confirm the real run times in your server's timezone, paste the result into the cron calendar preview, which also flags out-of-range values. If you only need a standard schedule, the ready-made schedules page is faster.
The expression is assembled from the form in your browser. No job is scheduled and nothing is sent to a server.
Follow-up: Cron Explainer · Cron Calendar
Keyboard shortcut
Produce cron strings for workers and batch scripts.
Draft expressions before pasting into CI or orchestrators.
Translate a spoken cadence into minute and hour fields.
Answers for this tool. For site-wide help, open the FAQ hub.
0. Monday is 1 and Saturday is 6. Many cron implementations also accept 7 for Sunday and three-letter names like MON, but 0 to 6 works everywhere.
No. The generator writes the classic five fields used by crontab, Kubernetes CronJobs and GitHub Actions. Quartz and Spring schedulers expect a leading seconds field, so add 0 at the front when targeting those.
GitHub evaluates schedules in UTC and may delay scheduled runs when its runners are busy, so a job set for 0 9 * * * can start some minutes after 09:00 UTC. Nothing in the expression changes that.