0 0 * * 0
Cron reads this as: at 00:00, on day-of-week Sunday.
Next 5 runs
Computed in your browser's local time zone. Cron itself evaluates against the server's zone, which on most cloud hosts is UTC — see time zones & DST if that distinction matters here.
- Calculating…
When to use this schedule
The conventional weekly slot, and the expression behind the @weekly shorthand. Used for weekly full backups, log archival, and rolling up a completed week's data.
What to watch out for
Sunday can be written as 0 or 7 in standard cron, but only 0 is accepted everywhere — Quartz, for instance, numbers Sunday as 1 and reads 7 as Saturday. Use 0, or better SUN, if the expression might travel. Midnight on Sunday is the start of Sunday, so a "weekly" job here is summarising Monday through Saturday plus nothing of Sunday itself.
The crontab line
0 0 * * 0 /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1
Redirect the output somewhere you will actually read it — by default cron mails it, and on a host with no mail transport that means it is discarded. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
@weekly | Shorthand for the same schedule |
0 0 * * SUN | Same schedule, using names |
0 4 * * 0 | Sunday at 04:00 |
Build your own
Need something this page does not cover? 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 collects sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.