Every Weekend at Midnight Cron Expression

0 0 * * 6,0

Try it live

Valid
MINMinute
0
HRHour
9
DOMDay of Month
*
MONMonth
*
DOWDay of Week
1-5

In plain English

At 09:00 AM, Monday through Friday

English → Cron

Try: "every 5 minutes", "every weekday at 9am", "every Monday at 3pm", "every month on the 1st"

Next 10 Executions

UTC
  1. 1Tue, Jul 7, 09:00 AM UTCin 15h
  2. 2Wed, Jul 8, 09:00 AM UTCin 2d
  3. 3Thu, Jul 9, 09:00 AM UTCin 3d
  4. 4Fri, Jul 10, 09:00 AM UTCin 4d
  5. 5Mon, Jul 13, 09:00 AM UTCin 7d
  6. 6Tue, Jul 14, 09:00 AM UTCin 8d
  7. 7Wed, Jul 15, 09:00 AM UTCin 9d
  8. 8Thu, Jul 16, 09:00 AM UTCin 10d
  9. 9Fri, Jul 17, 09:00 AM UTCin 11d
  10. 10Mon, Jul 20, 09:00 AM UTCin 14d
crontab entrybash
# Add to crontab with: crontab -e
0 9 * * 1-5    /path/to/your/script.sh

When to use this schedule

  • Weekend batch jobs that can run during low-traffic periods
  • Social media digest emails sent Saturday and Sunday mornings
  • Full database snapshots that take longer and should avoid weekday peak hours

Platform Syntax Comparison

The same "Every Weekend at Midnight" schedule expressed in every major platform's cron syntax.

PlatformExpression
Standard Linux/Unix
0 0 * * 6,0
GitHub Actions
0 0 * * 6,0
Google Cloud Scheduler
0 0 * * 6,0
Kubernetes CronJob
0 0 * * 6,0
Azure Functions (NCRONTAB)
0 0 0 * * 6,0
AWS EventBridge
0 0 ? * SAT,SUN *
Quartz Scheduler
0 0 0 ? * SAT,SUN
Spring @Scheduled
0 0 0 * * SAT,SUN
Jenkins
H H * * 6,0
Apache Airflow
0 0 * * 6,0

Frequently Asked Questions

Why "6,0" and not "6,7" for weekends?
In standard cron, 0 and 7 both mean Sunday. "6,0" means Saturday (6) and Sunday (0). Using "6,7" is also valid on most cron implementations.
Built & maintained by Danny Vargas
Last updated January 2026·Parsing runs in your browser — no expression leaves your device

Related Expressions