Cron every day at midnight

The cron expression for every day at midnight is:

0 0 * * *

Runs once a day at 00:00.

Once a day

Standard 5-field cron

Monitor this schedule Open in translator Change it in the generator

Next 10 runs

For 0 0 * * *, in the timezone you pick. Cron uses the server's timezone.

Times in UTC as of the last site update. They refresh when the page loads in a browser.

Timezone

#	Date and time	When
1	Oct 30, 2026, 00:00	Friday
2	Oct 31, 2026, 00:00	Saturday
3	Nov 1, 2026, 00:00	Sunday
4	Nov 2, 2026, 00:00	Monday
5	Nov 3, 2026, 00:00	Tuesday
6	Nov 4, 2026, 00:00	Wednesday
7	Nov 5, 2026, 00:00	Thursday
8	Nov 6, 2026, 00:00	Friday
9	Nov 7, 2026, 00:00	Saturday
10	Nov 8, 2026, 00:00	Sunday

How to read 0 0 * * *

0 0 sets minute 0 of hour 0. The last three * fields mean every day of the month, every month and every day of the week.

Field	Value	Meaning	Allowed
Minute	0	At the top of the hour	0-59
Hour	0	At 12:00 AM	0-23
Day of month	*	Every day of the month	1-31
Month	*	Every month	1-12 or jan-dec
Weekday	*	Every day of week	0-7 or sun-sat

Watch out for

Midnight in the server's timezone, which is often UTC. Check with date on the host. Some cron versions, such as cronie, accept CRON_TZ=Europe/Berlin at the top of the crontab; a Kubernetes CronJob takes timeZone.
@daily and @midnight are shortcuts for 0 0 * * * in most cron versions.
A lot of jobs start at midnight. If yours can run at any time, an odd time such as 17 3 * * * keeps it out of the rush.

Often used for: Daily rollups, cleanup, report emails and backups.

Use it in

crontab

0 0 * * * /path/to/your-script.sh

Edit with crontab -e. Runs in the server's timezone.

Kubernetes CronJob

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "0 0 * * *"
  timeZone: "Etc/UTC"
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: my-job
              image: busybox:1.36
              command: ["sh", "-c", "date"]

Without timeZone, the schedule follows the timezone of the kube-controller-manager.

GitHub Actions

on:
  schedule:
    - cron: '0 0 * * *'
      timezone: "Etc/UTC"
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./your-script.sh

Without timezone, GitHub runs schedules in UTC. It runs them at most every 5 minutes, and a run can start late when GitHub is busy.

All cron schedules

Cron does not tell you when a job stops

Know when a job on this schedule does not run.

Your job pings Drumbeats when it finishes. If a ping does not arrive on schedule, you get an alert. No SDK, free for up to 50 monitors.

Monitor this schedule Set up with AI agent

Free for up to 50 monitors · Setup in 60 seconds · No credit card required