Cron job every weekend (Saturday and Sunday)
0 0 * * 0,6 At 12:00 AM, only on Sunday and Saturday
Typical use: heavy jobs moved off business days. Try it below — change any field and see the next runs in your timezone.
At 12:00 AM, only on Sunday and Saturday
Valid
- 1Sat, Oct 3, 2026, 12:00 AM
- 2Sun, Oct 4, 2026, 12:00 AM
- 3Sat, Oct 10, 2026, 12:00 AM
- 4Sun, Oct 11, 2026, 12:00 AM
- 5Sat, Oct 17, 2026, 12:00 AM
- 6Sun, Oct 18, 2026, 12:00 AM
- 7Sat, Oct 24, 2026, 12:00 AM
- 8Sun, Oct 25, 2026, 12:00 AM
- 9Sat, Oct 31, 2026, 12:00 AM
- 10Sun, Nov 1, 2026, 12:00 AM
Field by field
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute 0 |
| Hour | 0 | hour 0 |
| Day of month | * | every day |
| Month | * | every month |
| Day of week | 0,6 | days Sunday, Saturday |
The same schedule on every platform
The five fields mean the same thing everywhere, but each scheduler wraps them differently — and AWS and Quartz number weekdays from 1 (Sunday), not 0.
0 0 * * 0,6 /path/to/script.sh >> /var/log/job.log 2>&1spec:
schedule: "0 0 * * 0,6"GitHub ActionsRuns in UTC.
on:
schedule:
- cron: '0 0 * * 0,6'AWS EventBridgeEventBridge weekdays are 1–7 (1 = Sunday) and one day field must be ?.
cron(0 0 ? * 1,7 *)Quartz (Java)Seconds first; weekdays 1–7 with 1 = Sunday.
0 0 0 ? * 1,7Spring @ScheduledSpring adds a seconds field but keeps Unix weekday numbers.
@Scheduled(cron = "0 0 0 * * 0,6")[TimerTrigger("0 0 0 * * 0,6")]Running a job every weekend (Saturday and Sunday)
What is the cron expression for every weekend (Saturday and Sunday)?
0 0 * * 0,6. In plain English: at 12:00 AM, only on Sunday and Saturday. It works in standard 5-field cron — Linux crontab, Kubernetes and GitHub Actions.How do I schedule a job every weekend (Saturday and Sunday) in AWS EventBridge?
Use
cron(0 0 ? * 1,7 *). EventBridge needs six fields (a year at the end), a ? in one of the day fields, and numbers weekdays 1–7 starting on Sunday.What timezone does "0 0 * * 0,6" run in?
Cron uses the server's timezone. Kubernetes CronJobs default to the controller's timezone (set
spec.timeZone on 1.27+), GitHub Actions and AWS EventBridge rules always use UTC. Use the timezone picker above to see the next runs in your own time.