Every Weekend at Midnight Cron Expression for Spring

0 0 0 * * SAT,SUN

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. 1Mon, May 18, 09:00 AM UTCin 3d
  2. 2Tue, May 19, 09:00 AM UTCin 4d
  3. 3Wed, May 20, 09:00 AM UTCin 5d
  4. 4Thu, May 21, 09:00 AM UTCin 6d
  5. 5Fri, May 22, 09:00 AM UTCin 7d
  6. 6Mon, May 25, 09:00 AM UTCin 10d
  7. 7Tue, May 26, 09:00 AM UTCin 11d
  8. 8Wed, May 27, 09:00 AM UTCin 12d
  9. 9Thu, May 28, 09:00 AM UTCin 13d
  10. 10Fri, May 29, 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.

Related Expressions