0 10 * * 6,0
Open in the generator
Saturday is 6 and Sunday is 0, so the list 6,0 covers the weekend. SAT,SUN works in most implementations too. Avoid the range 6-7: it depends on 7 being accepted as Sunday and on ranges being allowed to include it, which is not portable.
For the complementary schedule, weekdays only, use 1-5.
Field by field
| Value | Field | Meaning |
|---|---|---|
| 0 | Minute 0–59 | at minute 0 |
| 10 | Hour 0–23 | at 10:00 |
| * | Day of month 1–31 | every day of the month |
| * | Month 1–12 or JAN–DEC | every month |
| 6,0 | Day of week 0–7 or SUN–SAT (0 and 7 are Sunday) | on Saturday, 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
0 10 * * SAT,SUNthe same using names · try it0 9 * * 1-5weekdays only at 09:00 · see page0 0 * * 6Saturday at midnight · 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
Why does 0 10 * * 6-7 fail on my system?
Not every cron accepts 7 for Sunday, and some reject ranges that wrap past Saturday. Write 6,0 instead.