Cron Syntax Guide
Cron syntax varies significantly between platforms. Select a dialect below to see its field structure, special characters, day-of-week numbering, aliases, and common gotchas.
The original 5-field cron from Version 7 Unix — the lowest common denominator across POSIX systems.
Paul Vixie's 1987 extended cron — the de facto Linux default, source of `@daily`, `*/n`, and named days.
Amazon's 6-field cron for EventBridge Scheduler and CloudWatch Events — adds a year field, drops compatibility with `*`-in-both-day-fields.
5-field POSIX-style cron for workflow `schedule` triggers — defaults to UTC (optional `timezone:` field since March 2026), 5-minute minimum interval.
5-field cron for `CronJob` resources — Vixie-style syntax (parsed by robfig/cron), plus a `timeZone` spec field since Kubernetes 1.25.
Java's Quartz Scheduler — 6 or 7 fields, seconds resolution, `L`/`W`/`#` tokens, and 1-indexed day-of-week.
Spring Framework's `@Scheduled` cron — 6 fields (with seconds), Quartz-style L/W/# since Spring 5.3, and 0-indexed day-of-week like Unix.
6-field NCRONTAB format used by Azure Functions timer triggers — seconds first, day-of-week 0–6, full step syntax.
Not sure which syntax you need?
Paste any cron expression into the tester — it auto-detects POSIX, Quartz, and GitHub Actions syntax.
Open Cron Tester