Cron weekends
0 0 * * 0,6At 00:00, only on Sunday and Saturday.
Next runs · UTC
- —
- —
- —
- —
- —
Calendar
September 2026 · UTC
0 runs
About this tool
0 0 * * 0,6 - Sunday and Saturday at midnight. Use this for maintenance jobs that should avoid the busy weekday window - index rebuilds, log archives, backup verification.The cron expression for every Saturday and Sunday
0 0 * * 0,6
The day-of-week list 0,6 selects Sunday (0) and Saturday (6). Equivalent name-alias form: 0 0 * * SAT,SUN.
See the dedicated guide for the full breakdown: Cron every week.
Paste it into the editor above to see the next runs on a calendar.
When to run a job every Saturday and Sunday
- Reports and notifications that should only go out every Saturday and Sunday.
- Maintenance windows and heavier batch jobs scheduled around when people are working.
- Reminders and check-ins tied to a weekly rhythm rather than a calendar date.
Run this cron anywhere
0 0 * * 0,6 is five-field cron syntax. It works as is in:
- Linux
crontab-0 0 * * 0,6 /path/to/script.sh - Vercel cron jobs - declare in
vercel.json. - node-cron, robfig/cron and Kubernetes CronJob.
AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields, so convert first:
- AWS EventBridge -
cron(minute hour day-of-month month ? year); see the AWS guide. - Quartz Scheduler - prepend a seconds field (
0) and replace one day field with?; see the Quartz guide.
Useful variations
0 3 * * 0,6- weekends at 03:00 (off-hours maintenance)0 0 * * SAT,SUN- name-alias form (equivalent)*/30 * * * 0,6- every 30 minutes on weekends
Gotchas when running every Saturday and Sunday
- Timezone and daylight saving - DST handling is scheduler-specific: Vixie/cronie can skip or double local matches; GitHub advances nonexistent local times; EventBridge Scheduler skips spring and runs once in the fall overlap. UTC-only Vercel and Cloudflare schedules are unaffected.
- Missed runs are not replayed - If the host or platform is unavailable at the scheduled minute, standard cron simply waits for the next match. Add a heartbeat or alert if a skipped run must be noticed.
- Day-of-week and day-of-month are OR-ed - In Vixie-style cron, restricting both fields runs the job when either matches. Keep day-of-month as
*when the weekday is the only restriction you want. - Sunday numbering varies by dialect - Vixie-style cron accepts 0 and 7 as Sunday. AWS EventBridge and Quartz use 1 for Sunday and 7 for Saturday; prefer weekday names when translating dialects.
Examples
- 0 18 * * *Every day at 18:00
- 0 */5 * * *Every 5 hours
- 0 18 * * 1-5Weekdays at 18:00
- 0 0 1 * *Once a month, on the 1st at midnight
Cheatsheet
Full cheatsheet| Field | Req. | Range | Wildcards |
|---|---|---|---|
| minute | yes | 0-59 | , - * / |
| hour | yes | 0-23 | , - * / |
| day of month | yes | 1-31 | , - * / |
| month | yes | 1-12 or JAN-DEC | , - * / |
| day of week | yes | 0-6 or names; some dialects use 0-7 or 1-7 — see Dialects | , - * / |
Frequently asked questions
Syntax
Why does 0,6 mean Sunday and Saturday?
In Vixie cron, 0 is Sunday and 6 is Saturday. The comma selects those two separate weekend days.
Day-of-week valuesCan I write weekends as SAT,SUN?
Yes. 0 0 * * SAT,SUN is the readable five-field form in schedulers that accept weekday names. Expression: 0 0 * * SAT,SUN
Should I use a wrapping range such as 6-0 for weekends?
No. Wrapping weekday ranges are not portable; use the explicit Vixie list 0,6 or the names SAT,SUN.
Timing
How do I run at 03:00 on weekends?
Use 0 3 * * 0,6. The hour changes to 3 while the weekend list remains Sunday and Saturday. Expression: 0 3 * * 0,6
How do I run hourly overnight on weekends?
Use 0 0-6 * * 0,6. It runs hourly from midnight through 06:00 on each Saturday and Sunday calendar date. Expression: 0 0-6 * * 0,6
Days and months
Can I combine weekends with day 1 of the month?
Yes, but Vixie treats the restricted fields as OR. 0 9 1 * 0,6 runs every weekend and every first day of the month. Expression: 0 9 1 * 0,6
How do I change a weekend schedule to Saturday only?
Use 0 0 * * 6 in Vixie cron. Removing Sunday value 0 leaves one Saturday midnight run. Expression: 0 0 * * 6
How do I change a weekend schedule to Sunday only?
Use 0 0 * * 0 in Vixie cron. This is also the schedule represented by its @weekly shortcut. Expression: 0 0 * * 0
Platforms
Does Quartz use 0,6 for weekends?
No. Quartz numbers Sunday as 1 and Saturday as 7, so use names for clarity: 0 0 0 ? * SAT,SUN. Expression: 0 0 0 ? * SAT,SUN
Debugging
Are weekends automatically safe quiet hours for deployments?
No. Confirm traffic and staffing patterns first, then add health checks and rollback automation; cron only chooses the start time.
Crontap
Can Crontap call an endpoint on weekends only?
Yes. Crontap can run 0 0 * * 0,6 in the selected IANA timezone and invoke an HTTP endpoint on Saturday and Sunday.
General
What is the cron expression for every Saturday and Sunday?
0 0 * * 0,6. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every Saturday and Sunday; AWS EventBridge and Quartz need the six-field form.
How can I verify this cron actually runs every Saturday and Sunday?
The editor above shows the next 30+ runs on a calendar in your local timezone, plus a plain-English description. If the calendar matches your intent, the cron is correct.
Does 0 0 * * 0,6 work on every platform?
Linux crontab, Vercel cron jobs, node-cron, robfig/cron, and Kubernetes CronJob accept the five-field form as is. AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields; see the AWS and Quartz guides for the conversion. Vercel's free Hobby plan caps the minimum frequency at once-per-day; the Pro plan removes that cap.
What happens if the previous run is still going when the next one fires?
Most schedulers will start the new run anyway, leading to overlap. To prevent this, wrap the command with flock -n /tmp/myjob.lock /path/to/script.sh on Linux, or set concurrencyPolicy: Forbid on Kubernetes CronJob. Vercel and EventBridge may overlap runs if the previous one is still executing; make the handler idempotent.
Write the cron here. Run it on Crontap.
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
1.9k+ teams · Free forever tier · No credit card