Regex and cron

Cron Expression for Every Week

Once a week at 00:00 on Sunday, the same as @weekly. 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 * * 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 month0day (week)Day of week: only on Sunday

Once a week at 00:00 on Sunday, the same as @weekly.

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 * * 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 week is 0 0 * * 0, which is what the @weekly macro expands to: once a week at 00:00 on Sunday. Cron has no weekly interval as such, so a weekly job is really a day of the week plus a time. Any day works, for example 0 0 * * 1 for Monday at midnight.

  • 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 * * 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.

Does @weekly mean Sunday or Monday?

It depends on the tool, and that surprises people moving jobs between cron and systemd:

ToolWeekly shorthandRuns at
crontab (Vixie cron, cronie)@weeklySunday 00:00 (0 0 * * 0)
Kubernetes CronJob@weeklySunday 00:00
GitHub Actionsnone (macros aren't accepted)Write 0 0 * * 0
systemd timerOnCalendar=weeklyMonday 00:00

So a weekly job that moves from a crontab to a systemd timer quietly shifts by a day unless you spell the day out, for example OnCalendar=Sun *-*-* 00:00:00. Writing all five cron fields instead of a macro avoids the question entirely and makes the day obvious to the next person who reads the file.

Why doesn't */7 in the day-of-month field mean every 7 days?

Because steps restart every month. 0 0 */7 * * matches days 1, 8, 15, 22 and 29, then the 1st of the next month, so the last gap of most months is only one to three days. It looks weekly, but it isn't.

Cron has no notion of "every N days since a start date". For a strict seven-day cycle, use a fixed weekday: 0 0 * * 0 is exactly seven days apart every time. For every two weeks, run weekly and let the job skip alternate weeks based on the ISO week number, or use a scheduler with real intervals. Choosing the day itself is a separate decision: Monday suits work-week reporting, while Sunday is the quieter maintenance day.

What does each field in 0 0 * * 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 week00–7 (0 and 7 are Sunday), SUN–SATonly on Sunday

Read together: Once a week at 00:00 on Sunday, the same as @weekly.

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

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

ExpressionWhat it does
0 0 * * 1Weekly on Monday at midnight
0 3 * * 0Weekly on Sunday at 3 AM
0 12 * * 3Weekly on Wednesday at noon, mid-week
0 9 * * 5Weekly on Friday at 9 AM
0 0 */7 * *Not weekly: days 1, 8, 15, 22 and 29 of each month

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 Sunday · Every Monday · Every weekend · Every month

Browse all schedules in the cron schedule library.

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

PlatformWrite it asTime zone
Linux crontab0 0 * * 0Server's time zone; CRON_TZ= in cronie
GitHub Actions- cron: "0 0 * * 0"UTC by default; add timezone: (IANA name)
Kubernetes CronJobschedule: "0 0 * * 0"Set timeZone: (1.27+)
Cloudflare Workers0 0 * * SUNUTC only; numbers weekdays from 1 = Sunday, so use names
Vercel Cron Jobs0 0 * * 0UTC only; Hobby runs it within the hour (±59 min)
AWS EventBridge Schedulercron(0 0 ? * SUN *)Takes a time zone; legacy scheduled rules are UTC only
systemd timerOnCalendar=Sun *-*-* 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 * * 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 * * 0?

  • systemd's weekly is Monday 00:00, while cron's @weekly is Sunday 00:00. Spell the day out when you migrate a job.
  • */7 in the day-of-month field restarts on the 1st, so it is not every seven days. Use a fixed day of the week instead.
  • Plain cron skips a weekly run if the machine is off at that moment, and the next try is a week later. anacron and systemd timers with Persistent=true catch up instead.
  • A weekly job that fails silently can go unnoticed for weeks. Alert on failure, or ping a heartbeat monitor on success.
  • 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 * * 0 runs once a week at 00:00 on Sunday, the same as @weekly. Change the last field to choose another day, for example 1 for Monday.
In crontab and Kubernetes, @weekly means Sunday at 00:00. In systemd, OnCalendar=weekly means Monday at 00:00. Write the day explicitly if the difference matters.
No. Cron matches calendar fields, not intervals from a start date. A fixed weekday gives a steady seven-day gap; for other intervals, run more often and let the job decide whether enough time has passed.
Standard cron has no every-other-week field. Schedule the job weekly and have it exit on odd or even ISO week numbers, or use a scheduler with intervals, such as a systemd timer with OnUnitActiveSec.

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