0 9 * * 3 — the mid-week sweet spot. Common use cases: mid-week digest, halfway reminders, mid-cycle reports.View future cron matches in a calendar
Showing next 1000 cron schedules
0 9 * * 3
The day-of-week value 3 is Wednesday in standard cron. Name-alias form: 0 9 * * WED.
See the dedicated guide for the full breakdown: Cron every week.
Paste it into the editor above to see the next runs on a calendar.
0 0 * * 3 — every Wednesday at midnight0 9 * * WED — name-alias form (equivalent)0 9 * * 3 uses standard 5-field cron syntax, so it works in:
crontab — 0 9 * * 3 /path/to/script.shvercel.json.cron(...) with day-of-week as ? and a year field.0) and append day-of-week ?.`0 9 * * 3`. Paste this into any cron-compatible scheduler (Linux crontab, AWS EventBridge, Vercel cron, Quartz, node-cron, robfig/cron) to run a job every Wednesday at 09:00.
The editor above shows the next 30+ runs on a calendar in your local timezone, plus a plain-English description. If the calendar matches your intent, the cron is correct.
It uses standard 5-field cron syntax, so yes — Linux crontab, AWS EventBridge (with the additional `?` and year fields), Vercel cron jobs, Quartz Scheduler, node-cron, robfig/cron, and Kubernetes CronJob all accept it. Vercel's free Hobby plan caps the minimum frequency at once-per-day; the Pro plan removes that cap.
Most schedulers will start the new run anyway, leading to overlap. To prevent this, wrap the command with `flock -n /tmp/myjob.lock /path/to/script.sh` on Linux, or set `concurrencyPolicy: Forbid` on Kubernetes CronJob. Vercel cron and AWS EventBridge let you configure concurrency at the platform level.
Ready to schedule it?
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
Schedule
“every 5 minutes”
Next run
in 23s