Regex and cron

Cron Expression for Every Weekend

At 00:00 on Saturday and again at 00:00 on Sunday. Copy it, check the next runs in your time zone and grab a snippet for your platform.

  • Free foreverNo trial, no paywall, no usage limits.
  • No sign-upOpen the page and start. We never ask for an email to use a tool.
  • PrivateEverything runs in your browser. Your input is never uploaded or stored on our servers.
  • Works offlineOnce the page has loaded, the tool keeps working without a connection.

Cron expression

0 0 * * 6,0
Customize
0minuteMinute: at minute 0 (on the hour)0hourHour: at hour 0 (midnight)*day (month)Day of month: every day of the month*monthMonth: every month6,0day (week)Day of week: only on Sunday and Saturday

At 00:00 on Saturday and again at 00:00 on Sunday.

Time zone
Run times, the week view and the snippets use this zone. It starts as your device's zone.
Show times as 9:00 AM instead of 09:00.

Next runs

Each run in your selected time zone, with the same moment in UTC. Daylight saving changes follow cronie, the cron on most Linux servers.
Copy run times (ISO 8601)

Next 7 days

Each square is one hour of local time in your selected zone. Darker squares have more runs. Daylight saving changes are not drawn.

Use it on your platform

Copy-ready config for each scheduler. Dialects differ: some only run in UTC, some can't do seconds, Cloudflare and AWS number weekdays from 1 = Sunday. The snippet handles the conversion and says what changed.
A line for crontab -e on Linux or macOS (Vixie cron, cronie).on.schedule for a workflow, with the timezone field GitHub added in March 2026 (UTC when omitted).A CronJob manifest with the timeZone field (Kubernetes 1.27+).Cron Triggers in wrangler.toml for a Worker. Runs in UTC and numbers weekdays from 1 = Sunday.crons in vercel.json plus the route it calls. Runs in UTC.EventBridge Scheduler (any time zone, recommended by AWS) and a legacy EventBridge scheduled rule (UTC).A .timer unit with OnCalendar=, the systemd replacement for cron.
Runs as writtenRuns in your time zone
crontab -e
Copy crontab -eDownload my-job.crontab
# ┌───────────── minute (0–59)
# │ ┌─────────── hour (0–23)
# │ │ ┌───────── day of month (1–31)
# │ │ │ ┌─────── month (1–12)
# │ │ │ │ ┌───── day of week (0–6, Sunday = 0)
# │ │ │ │ │
# * * * * *  command
CRON_TZ=UTC
0 0 * * 6,0  /path/to/my-job.sh >> /var/log/my-job.log 2>&1
  • CRON_TZ=UTC is honored by cronie (Fedora, RHEL, Arch). Other cron daemons ignore it and use the server's time zone, so check timedatectl first.
  • Edit with crontab -e. Cron starts the next run even if the last one is still going; wrap the command in flock -n /tmp/my-job.lock to prevent overlaps.

Need scheduled jobs, queues and monitoring that never miss a run? Talk to our team

Quick answer

The cron expression for every weekend is 0 0 * * 6,0. The day-of-week list 6,0 means Saturday (6) and Sunday (0), and the first two fields run it at 00:00. That is two runs per weekend: one as Saturday begins and one as Sunday begins. The order of a list doesn't matter, so 0,6 is identical.

  • Live next runs
  • Any time zone
  • Field-by-field breakdown
  • Seven platform snippets
  • Daylight saving aware

How to use this schedule

  1. 1Copy 0 0 * * 6,0 with the Copy expression button.
  2. 2Check Next runs in your time zone to confirm it fires when you expect, including around daylight saving changes.
  3. 3Pick your platform under Use it on your platform and copy the ready-made crontab line, workflow, manifest or timer.
  4. 4Need a different time or day? Click Customize to open it in the cron expression generator and change any field.

Why is it 6,0 and not 6-0?

Saturday is 6 and Sunday is 0, so the weekend straddles the end of cron's numbering. A range has to run upward, which makes 6-0 invalid: cron rejects the line, and the error is easy to miss if you never read cron's logs. There are three correct ways to write the weekend:

  • 6,0: a list, read as "Saturday and Sunday"
  • 0,6: the same list in numeric order
  • 6-7: a range from Saturday to 7, which is Sunday's alternative number in Vixie cron and cronie

Lists are the most portable of the three, since not every scheduler accepts 7. In crontab you can also write SAT,SUN. The same rule applies to any span that crosses Sunday, such as Friday to Monday: write 5,6,0,1 or 5-7,1, never 5-1.

Do you want one run per weekend or two?

0 0 * * 6,0 runs twice: at the start of Saturday and at the start of Sunday. That suits jobs that should happen on each weekend day, like a heavier maintenance pass while traffic is low. If you want the job once per weekend, pick a single day instead: 0 0 * * 6 (Saturday at midnight) or 0 3 * * 0 (Sunday at 3 AM). For maintenance windows, an early-morning hour such as 03:00 is often quieter than midnight, when other nightly jobs are still running. Both weekend days are judged in the server's time zone, so on a UTC server "the weekend" starts on Friday evening in the Americas.

What does each field in 0 0 * * 6,0 mean?

FieldValueAllowedMeaning
Minute00–59at minute 0 (on the hour)
Hour00–23at hour 0 (midnight)
Day of month*1–31every day of the month
Month*1–12, JAN–DECevery month
Day of week6,00–7 (0 and 7 are Sunday), SUN–SATonly on Sunday and Saturday

Read together: At 00:00 on Saturday and again at 00:00 on Sunday.

How do I adjust 0 0 * * 6,0 to my own schedule?

Small edits to 0 0 * * 6,0 cover most real-world needs:

ExpressionWhat it does
0 0 * * 6Once a weekend, Saturday at midnight
0 3 * * 0Once a weekend, Sunday at 3 AM
0 */4 * * 6,0Every 4 hours throughout Saturday and Sunday
0 0 * * 6-7Saturday and Sunday, using 7 for Sunday
0 0 * * 1-5The opposite: weekdays only

Need something else? Click Customize at the top of the page to open this schedule in the cron expression generator and change any field.

Related schedules: Every weekday · Every Sunday · Every week · Every Friday at 5pm

Browse all schedules in the cron schedule library.

How do I run 0 0 * * 6,0 in crontab, GitHub Actions, Kubernetes and the cloud?

PlatformWrite it asTime zone
Linux crontab0 0 * * 6,0Server's time zone; CRON_TZ= in cronie
GitHub Actions- cron: "0 0 * * 6,0"UTC by default; add timezone: (IANA name)
Kubernetes CronJobschedule: "0 0 * * 6,0"Set timeZone: (1.27+)
Cloudflare Workers0 0 * * SUN,SATUTC only; numbers weekdays from 1 = Sunday, so use names
Vercel Cron Jobs0 0 * * 6,0UTC only; Hobby runs it within the hour (±59 min)
AWS EventBridge Schedulercron(0 0 ? * SUN,SAT *)Takes a time zone; legacy scheduled rules are UTC only
systemd timerOnCalendar=Sun,Sat *-*-* 00:00:00Add a zone after the time, e.g. Europe/London

In a crontab (crontab -e), the full line looks like this:

0 0 * * 6,0  /path/to/job.sh >> /var/log/job.log 2>&1

The live panel at the top of the page builds complete, copy-ready files for each platform (workflow, CronJob manifest, wrangler.toml, vercel.json, AWS CLI and systemd units) and can shift the schedule to UTC for platforms that need it.

What can go wrong with 0 0 * * 6,0?

  • 6-0 is a backwards range and is invalid. Use 6,0, 0,6 or 6-7.
  • The schedule fires twice each weekend. If the job should run once, choose a single day such as 0 0 * * 6.
  • Weekend days are judged on the server's clock. On a UTC server, Saturday 00:00 is still Friday evening in North America.
  • Quartz, AWS EventBridge and Cloudflare Workers number Sunday as 1 and Saturday as 7, so their weekend is 1,7 or SAT,SUN. Day names avoid the confusion.
  • On UTC-only platforms (Cloudflare Workers, Vercel, legacy EventBridge rules), the local time this runs at moves by an hour when daylight saving time starts or ends. Use GitHub's timezone:, Kubernetes timeZone, EventBridge Scheduler or cronie's CRON_TZ to pin it to local time.

Frequently asked questions

0 0 * * 6,0 runs at midnight on Saturday and Sunday. Replace the first two fields to choose another time, for example 0 10 * * 6,0 for 10 AM.
No. Ranges must go from a lower number to a higher one. Write 6,0 or 0,6 as a list, or 6-7 where 7 is accepted as Sunday.
Pick one day: 0 0 * * 6 runs at the start of Saturday, and 0 0 * * 0 at the start of Sunday. The list 6,0 runs on both days.
Both. Vixie cron and cronie accept 0 and 7 for Sunday. Some other tools only accept 0 to 6, so 0 is the safer choice.

Last updated by the Playxoft engineering team.

From the engineers who built this tool

Need scheduled jobs that never miss a run?

Cron is the easy part. Retries, overlapping runs, time zones, queues and alerts when a job silently stops are where schedules break. We build background job systems you can trust, and we will review your setup for free.

Get a free job-scheduling reviewSee backend services

More free tools

See all tools

Regex Tester

Test regex live with highlighted matches, plain-English explanations and code export.

Open tool

Cron Expression Generator

New

Build and explain cron schedules, see the next runs in any time zone, copy platform snippets.

Open tool

SQL Formatter

Beautify or minify SQL in 12 dialects, with keyword case, indent and line:column errors.

Open tool

cURL to Python Converter

New

Convert cURL commands into Python requests or httpx code with params, json, files and auth.

Open tool

cURL to Fetch Converter

New

Turn any cURL command into JavaScript fetch() code with headers, JSON, forms and auth.

Open tool

cURL to Axios Converter

New

Convert cURL commands into an Axios request config with params, data, auth and timeouts.

Open tool