The cron expression for every weekend is 0 0 * * 0,6. Runs on Saturday and Sunday only — useful for heavier maintenance that would disrupt a weekday. Preview the next runs in your timezone.
Paste an expression or choose a starting schedule below.
Select a field to edit it.
Schedule summary
Build a schedule
Run time in UTC. Change the timezone in Upcoming runs.
Valid changes update the expression above immediately.
Upcoming runs
The next 50 runs, shown in the schedule timezone and your local time.
About 0 0 * * 0,6
0 0 * * 0,6 — Runs on Saturday and Sunday only — useful for heavier maintenance that would disrupt a weekday.
Cron reads the five fields as minute hour day month weekday. For this schedule that breaks down as:
| Field | Position | Matches |
|---|---|---|
0 | minute | 0 |
0 | hour | 0 |
* | day of month | every day |
* | month | every month |
0,6 | day of week | Sunday, Saturday |
New to cron? Read the syntax reference or the FAQ.
Use it in crontab or GitHub Actions
The snippets below use UTC. The crontab timezone setting requires a compatible daemon such as Cronie. GitHub Actions defaults to UTC and accepts a timezone on each schedule. For other timezones, Kubernetes, EventBridge Scheduler, or Vercel, use the export menu in the calculator above.
crontab
# At 12:00 AM, only on Sunday and Saturday # CRON_TZ requires a cron implementation that supports it, such as Cronie. CRON_TZ=UTC 0 0 * * 0,6 /path/to/command
GitHub Actions workflow
# At 12:00 AM, only on Sunday and Saturday
on:
schedule:
- cron: '0 0 * * 0,6'
timezone: "UTC"