0 0 * * 6,0
Cron reads this as: at 00:00, on day-of-week Saturday and Sunday.
Next 5 runs
These times are in your browser's local time zone. Cron itself uses the server's zone, which on most cloud hosts is UTC. If the difference matters here, see time zones & DST.
- Calculating…
When to use this schedule
This runs at midnight on Saturday and on Sunday. Weekends are a good window for heavy maintenance such as full reindexes, schema migrations and large backfills, or anything else that needs a quiet system and users who will tolerate some disruption.
What to watch out for
Sunday is 0 and Saturday is 6, so the weekend is 6,0. That looks backwards and is easy to mistype as 0-6, which quietly turns a weekend job into a daily one. SAT,SUN is harder to get wrong. A long-running weekend job also has to finish before Monday morning. If it might not, give it a hard timeout rather than letting it run into the working week.
The crontab line
0 0 * * 6,0 /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1Send the output to a log you will read. By default cron mails it, and on a host with no mail transport that mail is silently dropped. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
0 0 * * SAT,SUN | Same schedule, using names |
0 2 * * 6 | Saturday only, at 02:00 |
0 0 * * 1-5 | Weekdays instead |
Build your own
If this page doesn't cover the schedule you need, compose it field by field in the visual builder, or paste an expression you already have into the explainer for a per-field breakdown. The examples library has sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.