ToolBark
Developer

Cron Expression Generator

Build cron schedules visually and get plain-English explanations instantly

Quick Presets

Configure each field

Minute

All values (*)

Hour

All values (*)

Day (Month)

All values (*)

Month

All values (*)

Day (Week)

All values (*)

Generated Expression

* * * * *
*Minute
*Hour
*Day (Month)
*Month
*Day (Week)

Human-readable schedule

Every minute.

Syntax Reference

SymbolMeaningExample
*Any / every value* = every minute / hour / …
*/nEvery nth value*/15 = every 15 minutes
a-bRange from a to b1-5 = Mon through Fri
a,b,cList of values0,12,18 = midnight, noon, 6 PM

Field order: minute (0–59) · hour (0–23) · day-of-month (1–31) · month (1–12) · day-of-week (0–6, Sun=0)

About

A cron expression generator lets you build the five-field cron syntax used by crontab, GitHub Actions, AWS EventBridge, and virtually every Unix scheduler — without memorising the format. Choose minute, hour, day-of-month, month, and day-of-week using intuitive selectors, then copy the finished expression and read the plain-English explanation to confirm it runs exactly when you expect.

FAQ
What do the five fields in a cron expression mean?+

Reading left to right: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–6, where 0 is Sunday). For example, "0 9 * * 1" means "at 9:00 AM every Monday".

How do I run a job every 15 minutes?+

Set the minute field to */15 and leave the rest as *. The full expression is "*/15 * * * *". The */n syntax means "every nth value" — so */15 fires at :00, :15, :30, and :45 past each hour.

Can I specify multiple specific values in one field?+

Yes. Separate values with commas: "0,30" in the minute field fires at the top and half-past of every hour. The generator's Specific mode lets you tick multiple checkboxes and it builds the comma-separated list for you.

What is the difference between day-of-month and day-of-week?+

Day-of-month targets a calendar date (e.g. the 1st), while day-of-week targets a recurring weekday (e.g. every Monday). If both are set to non-wildcard values, most schedulers fire the job when either condition is true — so use only one at a time unless you specifically want that OR behaviour.

Related tools