What is the cron expression for every sunday at midnight?

The cron expression for every Sunday at midnight is 0 0 * * 0. This schedule runs once per week.

How do I set up a cron job for every sunday at midnight?

Open your crontab with 'crontab -e' and add a line starting with '0 0 * * 0' followed by the command you want to run. For example: 0 0 * * 0 /path/to/script.sh

Cron Expression for Every Sunday at Midnight

Q: What does each field in 0 0 * * 0 mean?

A cron expression has 5 fields: minute (0), hour (0), day of month (*), month (*), and day of week (0). In 0 0 * * 0: 0 — at the top of the hour; 0 — at midnight (00:00).

0 0 * * 0

Expression Breakdown

The cron expression 0 0 * * 0 schedules a job to run every sunday at midnight. A standard cron expression consists of five fields representing minute, hour, day of month, month, and day of week. Here is what each field means in this expression:

Minute	`0` — at the top of the hour
Hour	`0` — at midnight (00:00)
Day of Month	`*` — every day of the month
Month	`*` — every month
Day of Week	`0` — Sunday only

This schedule runs once per week, which amounts to 1 time per week and approximately 4-5 times per month.

Next 5 Run Times

Starting from April 11, 2026 00:00 UTC, the next five executions are:

2026-04-12T00:00:00Z — Sun, 12 Apr 2026 00:00:00 GMT
2026-04-19T00:00:00Z — Sun, 19 Apr 2026 00:00:00 GMT
2026-04-26T00:00:00Z — Sun, 26 Apr 2026 00:00:00 GMT
2026-05-03T00:00:00Z — Sun, 03 May 2026 00:00:00 GMT
2026-05-10T00:00:00Z — Sun, 10 May 2026 00:00:00 GMT

Common Use Cases

Running a task every sunday at midnight is a popular cron schedule. Here are some typical applications:

Weekly full: Weekly full database backup before the new work week
Weekly analytics: Weekly analytics digest email to stakeholders
Clearing temporary: Clearing temporary files and expired cache entries
Weekly dependency: Weekly dependency vulnerability scanning for security

Code Examples

Linux / macOS Crontab

# Open crontab editor
crontab -e

# Add this line to run your script every sunday at midnight
0 0 * * 0 /usr/local/bin/my-task.sh

# With logging
0 0 * * 0 /usr/local/bin/my-task.sh >> /var/log/my-task.log 2>&1

Python (schedule library alternative)

# Using APScheduler with cron trigger
from apscheduler.schedulers.blocking import BlockingScheduler
from apscheduler.triggers.cron import CronTrigger

scheduler = BlockingScheduler()
trigger = CronTrigger.from_crontab("0 0 * * 0")
scheduler.add_job(my_function, trigger)
scheduler.start()

JavaScript (Node.js with node-cron)

const cron = require('node-cron');

// Run task every sunday at midnight
cron.schedule('0 0 * * 0', () => {
  console.log('Task running at', new Date().toISOString());
  // Your task logic here
});

Frequently Asked Questions

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

A cron expression has five fields separated by spaces: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-7, where 0 and 7 are Sunday). The */n syntax means "every nth interval." In 0 0 * * 0, the fields are: 0 — at the top of the hour; 0 — at midnight (00:00); * — every day of the month.

How do I verify that 0 0 * * 0 is correct?

Use the EpochPilot Cron Expression Builder to paste your expression and see the next run times visually. You can also use the crontab -l command to list your current crontab entries, or test with a simple echo command: 0 0 * * 0 echo "test" >> /tmp/cron-test.log.

What timezone does cron use?

By default, cron uses the system timezone configured on your server. On most cloud servers this is UTC. You can check your system timezone with timedatectl on Linux or date +%Z. Some cron implementations (like Kubernetes CronJobs) let you specify a timezone explicitly. Always verify your server's timezone to ensure jobs run at the expected times.

Try the Cron Expression Builder to create and test cron schedules.