Build a Cron Schedule Without Memorizing the Syntax

Writing cron shouldn't require the man page

You know exactly what you want — "run this every weekday at 6:30pm" — but turning that sentence into 30 18 * * 1-5 means recalling field order, zero-based weekdays, and step syntax from memory. Guess wrong and the job either never fires or fires far too often. A generator flips the problem around: you describe the schedule in plain controls and it produces the exact expression.

How a cron expression is built

Every standard cron schedule is five fields in a fixed order — minute, hour, day-of-month, month, day-of-week. Each field is built from four operators:

• * means "every" value in that field.
• , lists specific values, like 1,15.
• - gives a range, like 1-5 for Monday to Friday.
• / adds a step, like */10 for every ten units.

When you assemble a schedule with a builder, you are really choosing values for these five fields; the tool just handles the punctuation so you never fat-finger a comma or forget a field.

A quick reference of common schedules

These cover the vast majority of real jobs:

*/5 * * * *       # every 5 minutes
0 * * * *         # every hour, on the hour
0 0 * * *         # every day at midnight
30 18 * * 1-5     # 18:30 on weekdays
0 9 * * 1         # 09:00 every Monday
0 3 1 * *         # 03:00 on the 1st of each month
0 0 * * 0         # midnight every Sunday

Instead of adapting one of these by hand, open the Cron Expression Generator, pick your minutes, hours, days and months from the controls, and copy the finished expression. Everything is computed in your browser, so no schedule or config leaves your machine.

A practical walkthrough

Say you want a cache-warming job every 15 minutes during business hours (9am to 5pm) on weekdays. Broken into fields:

• Minute: every 15 -> */15
• Hour: 9 through 17 -> 9-17
• Day of month: any -> *
• Month: any -> *
• Day of week: Mon–Fri -> 1-5

*/15 9-17 * * 1-5

That single line runs your task at :00, :15, :30 and :45 past every hour from 9am to 5pm, Monday through Friday. Paste it into your crontab, GitHub Actions schedule, or a Kubernetes CronJob and you are done.

Tips and pitfalls

• Always pin the minute. Leaving it as * makes the job run every minute of the matching hour. If you mean "once at 9am", write 0 9 * * *, not * 9 * * *.
• Mind the time zone. Most schedulers evaluate cron in the host's zone (frequently UTC). Convert your intended local time to that zone before generating, or your job will drift by hours.
• Avoid the day-of-month + day-of-week trap. Restricting both fields makes them combine with OR in standard cron, which rarely does what people expect. Leave one as * unless you truly want either-or behavior.
• Verify before you ship. Generating is only half the job. Drop the result into the Cron Expression Parser to read it back in plain English and preview the next runs.

If your job also needs to reason about absolute moments — say, comparing a run against a logged event — the Unix Timestamp Converter pairs nicely for turning epoch values into readable dates.

Conclusion

You do not need to memorize crontab syntax to schedule reliable jobs. Describe the cadence in plain terms, let the generator assemble the five fields, then round-trip the result through a parser to confirm it. Pin your minute, watch the time zone, and steer clear of the day-of-month/day-of-week overlap, and your scheduled tasks will fire exactly when you expect.