Cron expression for once a week
0 0 * * 0At 00:00, on Sunday.
Cron has no “every 7 days” step. Pick a weekday instead: this runs every Sunday at 00:00, like @weekly.
Try it and tweak it
Change any field below and the preview updates. Set the time zone to match your server.
✓ Valid cron
At 00:00, on Sunday.
Next 10 runs
Calculating in your browser…
Times are computed in your browser for the selected zone and are informational. The server that runs the job uses its own zone (often UTC) and cron flavour, so verify there.
Same schedule in other dialects
Unix crontab
0 0 * * SUNQuartz
0 0 0 ? * SUNSpring @Scheduled
0 0 0 ? * SUNAWS EventBridge
cron(0 0 ? * SUN *)Variations
0 6 * * 1 | Weekly on Monday at 06:00 |
0 0 */7 * * | Not weekly: runs on the 1st, 8th, 15th, 22nd, 29th and resets each month |
In other schedulers
| crontab line | 0 0 * * 0 /path/to/command |
| Quartz | 0 0 0 ? * SUN |
| Spring | @Scheduled(cron = "0 0 0 ? * SUN") |
| AWS EventBridge | cron(0 0 ? * SUN *) |
| GitHub Actions | - cron: '0 0 * * 0' (UTC) |
| Kubernetes | schedule: "0 0 * * 0" |
Questions
What is the cron expression for every week (weekly)?
0 0 * * 0. At 00:00, on Sunday.
How do I write it in Quartz or Spring?
Add a seconds field and use "?" for the unused day field: 0 0 0 ? * SUN. In Spring: @Scheduled(cron = "0 0 0 ? * SUN").
What is the AWS EventBridge version?
cron(0 0 ? * SUN *). AWS uses six fields with a year at the end and needs "?" in one of the day fields.
Which time zone will it use?
The time zone of the machine or service running cron. GitHub Actions and Vercel use UTC; Kubernetes uses spec.timeZone if set. The preview above lets you pick a zone.