Cron Expression Generator — Build a Cron Schedule Visually

Common schedules

One click fills in every field — then fine-tune below.

Build each field

Minute

Hour

Day of month

Month

Day of week

Cron field reference

Field	Allowed values	Every	Step	Range
Minute	0–59	`*`	`*/15`	`0-30`
Hour	0–23	`*`	`*/2`	`9-17`
Day of month	1–31	`*`	`*/2`	`1-15`
Month	1–12	`*`	—	`1-6`
Day of week	0–6 (0 = Sunday)	`*`	—	`1-5`

Already have an expression and want it explained? Use the companion Cron Expression Parser to paste any 5-field schedule and get the same plain-English breakdown and upcoming run times. Note: when both day-of-month and day-of-week are restricted, standard cron fires when either matches.

How it works

Point-and-click the schedule you want; this tool writes correct cron syntax and shows you exactly when it will fire.

Pick a preset or build each field

Start from a common schedule, or set every / a specific value / a step / a range for the minute, hour, day, month and weekday fields.

Copy the cron expression

The 5-field string updates live as you change the controls. Copy it with one click, ready to paste into crontab, CI or a scheduler.

Confirm before you ship

Read the plain-English summary and preview the next run times in your time zone so the schedule does exactly what you intended.

🔒

Private by design.Everything happens right here in your browser. Your files are never uploaded — we never see them.

Frequently Asked Questions

What is a cron expression? ▼

It's a 5-field string that describes a repeating schedule: minute hour day-of-month month day-of-week. For example 0 9 * * 1-5 runs at 09:00 on weekdays.

What do the every, specific, step and range options do? ▼

Every uses * (all values). Specific picks a single value like 9. Step produces */N — every N units. Range produces A-B, an inclusive span such as 9-17.

What order are the fields in the output? ▼

Always minute, hour, day-of-month, month, day-of-week — the order used by standard Unix/Vixie cron and by most schedulers (crontab, GitHub Actions, Kubernetes CronJobs).

Which time zone are the next run times in? ▼

They're computed in your device's local time zone, shown above the list. Your server may run cron in UTC or another zone, so double-check where the job actually executes.

I already have an expression — can I explain it instead? ▼

Yes. Use the companion Cron Expression Parser to paste an existing schedule and get the same plain-English breakdown and next run times.

Is anything I build sent to a server? ▼

No. The expression, the description and the next-run calculations are generated entirely in your browser with plain JavaScript. Nothing is uploaded or stored — we never see it.