0 0 * * 0
Open in the generator
Sunday is day 0 in the day-of-week field, and most implementations accept 7 as well. @weekly is an alias for this exact expression.
Sunday night is a popular slot for heavier weekly work such as full backups, index rebuilds and report generation, when weekday traffic is lowest.
Field by field
| Value | Field | Meaning |
|---|---|---|
| 0 | Minute 0–59 | at minute 0 |
| 0 | Hour 0–23 | at 00:00 |
| * | Day of month 1–31 | every day of the month |
| * | Month 1–12 or JAN–DEC | every month |
| 0 | Day of week 0–7 or SUN–SAT (0 and 7 are Sunday) | on Sunday |
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
30 2 * * SUNSunday at 02:30 · try it0 0 * * 1every Monday at midnight · see page0 10 * * 6,0weekends at 10:00 · see page
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
Should I write 0 or 7 for Sunday?
Use 0. It works everywhere; 7 is widely but not universally accepted, and a range like 1-7 may be rejected.