ClockOrbit

Weekly

0 0 * * 6

Run once a week, Saturday at 00:00.

This preview is live: the table below shows the actual next run times for 0 0 * * 6 in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.

Next runs
valid
Upcoming runs
Sat, Nov 7 2026
00:00 UTC
in 11 hours
Fri, Nov 13 2026
00:00 UTC
in 6 days
Sat, Nov 14 2026
00:00 UTC
in 7 days
Fri, Nov 20 2026
00:00 UTC
in 13 days
Sat, Nov 21 2026
00:00 UTC
in 14 days
Fri, Nov 27 2026
00:00 UTC
in 20 days
Sat, Nov 28 2026
00:00 UTC
in 21 days
Fri, Dec 4 2026
00:00 UTC
in 27 days
Sat, Dec 5 2026
00:00 UTC
in 28 days
Fri, Dec 11 2026
00:00 UTC
in 34 days
Sat, Dec 12 2026
00:00 UTC
in 35 days
Fri, Dec 18 2026
00:00 UTC
in 41 days
Sat, Dec 19 2026
00:00 UTC
in 42 days
Fri, Dec 25 2026
00:00 UTC
in 48 days
Sat, Dec 26 2026
00:00 UTC
in 49 days
Fri, Jan 1 2027
00:00 UTC
in 55 days
Sat, Jan 2 2027
00:00 UTC
in 56 days
Fri, Jan 8 2027
00:00 UTC
in 62 days
Sat, Jan 9 2027
00:00 UTC
in 63 days
Fri, Jan 15 2027
00:00 UTC
in 69 days
Sat, Jan 16 2027
00:00 UTC
in 70 days
Fri, Jan 22 2027
00:00 UTC
in 76 days
Sat, Jan 23 2027
00:00 UTC
in 77 days
Fri, Jan 29 2027
00:00 UTC
in 83 days
Sat, Jan 30 2027
00:00 UTC
in 84 days

What 0 0 * * 6 means

0 0 * * 6 fires at the start of Saturday, day-of-week 6 in Unix. The weekend is the most popular window for disruptive maintenance, because production traffic on many business systems is at its lowest, so jobs that need an exclusive lock or a long quiet window run here.

Saturday-midnight is the front edge of that window: schema migrations, full-table rewrites, large data migrations, and anything you would never dare run during the week.

Field-by-field breakdown

Unix cron has five fields. Here is what each one is doing in this expression:

FieldValueMeaning
Minute0minute = 0
Hour0hour = 0
Day of month*every day-of-month
Month*every month
Day of week6day-of-week = 6

Every Saturday at midnight in every scheduler

The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target, the field count and day-of-week numbering differ between them.

SchedulerExpressionCopy
Unix / crontab0 0 * * 6
GitHub Actions0 0 * * 6
Kubernetes CronJob0 0 * * 6
Vercel Cron0 0 * * 6
Quartz0 0 0 ? * 6 *
Spring0 0 0 ? * 6
AWS EventBridge0 0 ? * 6 *

When you would use 0 0 * * 6

The gotcha worth knowing

Saturday is 6 and Sunday is 0 in Unix, but * * * * 6,0 (or 6,7) is the idiomatic "weekend" set. Writing * * * * 0-6 covers the whole week, not just the weekend.

People also search for

cron every saturday0 0 * * 6crontab saturday midnightcron weekend job

0 0 * * 6 FAQ

What does the cron expression 0 0 * * 6 mean?

0 0 * * 6 means: Run once a week, Saturday at 00:00. 0 0 * * 6 fires at the start of Saturday, day-of-week 6 in Unix. The weekend is the most popular window for disruptive maintenance, because production traffic on many business systems is at its lowest, so jobs that need an exclusive lock or a long quiet window run here.

How do I write "every saturday at midnight" in GitHub Actions?

Use 0 0 * * 6 in the schedule's cron field. Saturday is 6 and Sunday is 0 in Unix, but * * * * 6,0 (or 6,7) is the idiomatic "weekend" set. Writing * * * * 0-6 covers the whole week, not just the weekend.

How do I write "every saturday at midnight" for AWS EventBridge?

EventBridge uses six fields with a required year and a ? placeholder in one day field: 0 0 ? * 6 *. Wrap it as cron(0 0 ? * 6 *) in the console or CloudFormation.

What is the Quartz equivalent of 0 0 * * 6?

Quartz is seconds-first with a trailing year, so the equivalent is 0 0 0 ? * 6 *. Remember Quartz numbers Sunday as 1, the opposite of Unix.

Related cron patterns

More cron tools

Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.