Cron Generator
About this tool
One wrong field and the job fires at the wrong hour. Generate a five-field expression from controls, or translate a inherited crontab line into plain language. Remember that 0 0 * * * still follows the machine clock.
Features
- Compose five cron fields from controls
- Explain an existing expression
- Call out that timezone lives in the runtime, not the expression
How to use
- Set minute, hour, day, month, and weekday.
- Read the expression and the prose explanation.
- Copy into crontab, CI, or a Kubernetes CronJob.
- Confirm TZ on the target so UTC and local time do not surprise you.
When to use it
- A nightly backup should be midnight, and you want to confirm the five fields
- You inherited a crontab line nobody documented
- CI schedules drift from the server clock
Examples
- Every day at 09:30: minute 30, hour 9, rest *.
- 0 */6 * * * is minute 0 of every sixth hour.
FAQ
What does 0 0 * * * mean?
Midnight every day. Stars in day-of-week and day-of-month mean unrestricted. The clock still follows the host timezone.
Six-field cron with seconds?
This page focuses on five fields. Add seconds only if your scheduler documents it.
Why does production fire at another hour?
Cron stores no zone. Check TZ on Docker, CronJob, or the CI runner.
Weekdays only?
Set the weekday field to the range your implementation uses (often 1-5). Confirm whether 0 and 7 both mean Sunday.
Is the expression saved?
No. Generation stays in the browser.
Does this install crontab for me?
No. It only helps you write the five fields. Editing crontab and redirection still happens on the server.
Back to Time Tools Hub
Guides