Type schedules in plain English, validate any expression, and monitor cron jobs across 7 platforms. Free for indies.
Try the generator now — no signupType a schedule in plain English and press Generate
Try: "every Monday at 8am EST" or "daily at midnight UTC"
Paste any cron expression and get a plain-English breakdown: what it does, when it fires next, and what platform quirks to watch for.
Supports standard 5-field, AWS 6-field, Quartz 6-7 field, and Spring expressions.
Try the cron explainerInput
0 */6 * * 1-5Output
Every 6 hours on weekdays (Mon-Fri), at minute 0. Next run: Monday 00:00 UTC.
A cron expression that works on Linux might silently fail on AWS or GitHub Actions. Our validator checks your expression against all 7 platforms at once.
Catch plan limits, syntax mismatches, and edge cases before they break production.
Validate your cron expressionStop memorizing 5-field syntax. Stop guessing day-of-week numbering. Just describe your schedule.
Linux · AWS EventBridge · Kubernetes · Quartz · Spring · GitHub Actions · Vercel · Cloudflare Workers
DST transitions · UTC requirements · plan limits · platform-specific syntax · invalid edge cases
Input
backup at 3am SGT every dayLinux
0 3 * * *
TZ=Asia/Singapore
Kubernetes
0 3 * * *
timeZone: Asia/Singapore
The 6 most common reasons your scheduled job silently fails — and how to fix each one.
Your "9am" might be 9am UTC, not your local time. GitHub Actions and Vercel only accept UTC.
Sunday is 0 on Linux but 1 on Quartz/Spring. One wrong number and your job runs on Saturday instead.
GitHub Actions enforces a 5-minute minimum. Vercel Hobby plans allow only 1 cron per day. Your expression might be valid but rejected.
Expressions like "0 0 31 2 *" are syntactically valid but never fire. Most platforms accept them silently.
AWS EventBridge requires a "?" in one of these fields. Using "*" in both is an error that Linux cron allows.
A 2:30am job might run twice or skip entirely during daylight saving changes, depending on the platform's timezone handling.
Cronitor and Healthchecks are pure monitors. crontab.guru is a generator but Linux-only. cronwiz does both — generate, explain, validate, and soon monitor.
| Feature | cronwiz.dev |
|---|---|
| Plain English input | |
| Multi-platform output | 8 platforms |
| Plan limit warnings | |
| Edge case detection | |
| Reverse explanation | |
| Free tier | Free + $5/mo |
| Cron monitoring | Coming Q3 ($5) |
We're building the first AI-native cron monitor. Get plain-English alerts when your jobs miss runs, fail silently, or run abnormally slow.
No more "missed cron run on 2026-04-15 02:00 UTC" emails. Just: "Your nightly backup has been running 3x slower since Tuesday — here's why."
Be among the first 100 · Q3 2026 launch · From the makers of cronwiz.dev
A cron expression is a string that defines when a scheduled task should run. The classic format has 5 fields: minute, hour, day-of-month, month, day-of-week. Different platforms (AWS, Quartz, Kubernetes) extend or modify this format.