0 12 * * *
Open in the generator
Cron uses a 24-hour clock, so noon is hour 12 and midnight is hour 0; there is no AM or PM. To run at 12:30 write 30 12 * * *; for 6 PM write 0 18 * * *.
Noon jobs are a good fit for daily digests and mid-day data refreshes when the morning's data has settled but the working day is still in progress.
Field by field
| Value | Field | Meaning |
|---|---|---|
| 0 | Minute 0–59 | at minute 0 |
| 12 | Hour 0–23 | at 12:00 |
| * | Day of month 1–31 | every day of the month |
| * | Month 1–12 or JAN–DEC | every month |
| * | Day of week 0–7 or SUN–SAT (0 and 7 are Sunday) | every day of the week |
Next run times
Computed in your browser from the current time, so you can check the schedule against a clock you trust.
Your timezone (local)
- Needs JavaScript.
UTC (GitHub Actions, Kubernetes default)
Variations
0 9 * * *every day at 09:00 · try it0 18 * * *every day at 18:00 · try it0 12 * * 1-5weekdays at noon · try it
Where this expression works
- Linux and macOS crontab: as written; times follow the system timezone.
- Kubernetes CronJob: the same five fields; UTC unless
spec.timeZoneis set. - GitHub Actions: the same syntax in UTC, minimum interval five minutes, no
@shortcuts. - AWS EventBridge: a different six-field syntax; do not paste this expression unchanged.
Full platform comparison · Cron tutorial
FAQ
How do I write 12 AM in cron?
12 AM is midnight, hour 0: 0 0 * * *. 12 PM is noon, hour 12: 0 12 * * *.