What cron format does this use?

It uses the standard 5-field Unix format: minute, hour, day-of-month, month, and day-of-week. This is what crontab, most CI systems, and Kubernetes CronJobs expect, so the output drops straight in.

How are the fields ordered?

Left to right the fields are minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday). An asterisk means every value for that field.

Is the human description accurate?

Yes. The description is generated from the actual field values, so it always reflects the expression shown. If you tweak the preset, the wording updates to match.

Does it support step and range syntax?

Yes. Presets like every 15 minutes use step syntax such as */15, and business-hours uses a range like 9-17 in the hour field. Both are valid standard cron and widely supported.

Will these work in Kubernetes and GitHub Actions?

Yes. Both use the same 5-field cron syntax. Note that some platforms run in UTC, so confirm your scheduler's timezone before relying on a specific local hour.

Cron Expression Generator

What this tool does

The Cron Expression Generator produces valid 5-field cron expressions for the schedules people actually need — hourly, every few minutes, daily at a time, weekly on a day, monthly on a date, and weekday business hours — each paired with a clear English description. It turns “I think the fields go minute, hour, day…” into a copy-paste-ready schedule.

How it works

A cron expression has five space-separated fields: minute, hour, day-of-month, month, and day-of-week. The generator builds each preset by filling the relevant fields and leaving the rest as * (every value). For example, daily-at-time sets a minute and hour with * for the date fields; every-15-minutes uses the step form */15 in the minute field; business-hours uses the range 9-17 in the hour field and 1-5 (Mon–Fri) in day-of-week. The human-readable line is derived directly from those field values, so it always matches the expression.

All generation happens locally in your browser.

Tips and notes

The five fields are minute, hour, day-of-month, month, day-of-week (0 = Sunday).
*/n means “every n units”; a range like 9-17 means inclusive 9 through 17.
Most cloud schedulers run in UTC — verify the timezone before trusting a local hour.
The same syntax works in crontab, GitHub Actions, and Kubernetes CronJob.