Cron every sunday: 0 0 * * 0

Copy-paste

0 0 * * 0 /path/to/command

Cron syntax in one table

Field	Allowed values
Minute	0–59
Hour	0–23
Day of month	1–31
Month	1–12 or JAN–DEC
Day of week	0–6 or SUN–SAT (7 is also Sunday)

* means every value, a-b a range, a,b,c a list and */n every n-th value. Shortcuts @hourly, @daily, @weekly, @monthly and @yearly also work.

Other schedules

Every minute — * * * * *
Every 5 minutes — */5 * * * *
Every 10 minutes — */10 * * * *
Every 15 minutes — */15 * * * *
Every 30 minutes — */30 * * * *
Every hour — 0 * * * *
Every 6 hours — 0 */6 * * *
Every day at midnight — 0 0 * * *
Every day at 9 am — 0 9 * * *
Weekdays at 9 am — 0 9 * * 1-5
On the first day of every month — 0 0 1 * *

Questions

Which time zone does cron use?

The server’s time zone, usually UTC on cloud servers. 09:30 IST is 04:00 UTC, so a job meant for 9:30 am in India is written 0 4 * * * on a UTC server. Pick the zone above to check.

What if I set both day of month and day of week?

Classic cron runs the job when either matches, not both. 0 12 15 * 1 runs at noon on the 15th and also every Monday.

How do I run a job every 30 seconds?

Standard cron cannot go below one minute. Use two entries, one with sleep 30 before the command, or a scheduler that supports seconds.

Does this work for GitHub Actions, Kubernetes and cPanel cron jobs?

Yes, they all use the same 5-field format. GitHub Actions always runs in UTC; Kubernetes CronJobs can set a timeZone field.

Cron expression: every sunday