Daily at Midnight Cron Expression — 0 0 * * *
Cron Expression
0 0 * * *What it means
Runs once a day at midnight (00:00)
The most common daily schedule for database backups, log rotation, nightly analytics aggregation, and sending daily summary reports. Runs at 00:00 UTC.
Next 8 Scheduled Runs (UTC)
- 1.Thu, 25 Jun 2026 00:00:00 GMT
- 2.Fri, 26 Jun 2026 00:00:00 GMT
- 3.Sat, 27 Jun 2026 00:00:00 GMT
- 4.Sun, 28 Jun 2026 00:00:00 GMT
- 5.Mon, 29 Jun 2026 00:00:00 GMT
- 6.Tue, 30 Jun 2026 00:00:00 GMT
- 7.Wed, 01 Jul 2026 00:00:00 GMT
- 8.Thu, 02 Jul 2026 00:00:00 GMT
Platform Snippets
GitHub Actions
- cron: '0 0 * * *'
Kubernetes CronJob
schedule: "0 0 * * *"
AWS EventBridge
cron(0 0 * * ? *)
AWS uses a 6-field format with year and requires either DOM or DOW to be ?.
systemd Timer
[Timer] OnCalendar=*-*-* 00:00:00 Persistent=true
Want to decode a different expression or test your own?
Test this expression interactively →FAQ
What does the cron expression 0 0 * * * mean?
Runs once a day at midnight (00:00). The most common daily schedule for database backups, log rotation, nightly analytics aggregation, and sending daily summary reports. Runs at 00:00 UTC.
How do I use 0 0 * * * in GitHub Actions?
Add a schedule trigger under the "on" key in your workflow YAML: on: schedule: - cron: '0 0 * * *'. This will run your workflow runs once a day at midnight (00:00). Note that GitHub Actions uses UTC time.
Is the cron expression 0 0 * * * valid for Kubernetes CronJobs?
Yes. Set the schedule field in your CronJob spec to "0 0 * * *". Kubernetes CronJobs use standard 5-field cron syntax and run in UTC by default unless you configure a timeZone field.