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.

Unix Cron

The original 5-field cron from System V — the lowest common denominator across POSIX systems.

5 fields: minute hour day-of-month month day-of-week

Vixie Cron

Paul Vixie's 1987 extended cron — the de facto Linux default, source of `@daily`, `*/n`, and named days.

5 fields: minute hour day-of-month month day-of-week

AWS EventBridge Cron

Amazon's 6-field cron for EventBridge Scheduler and CloudWatch Events — adds a year field, drops compatibility with `*`-in-both-day-fields.

6 fields: minute hour day-of-month month day-of-week year

GitHub Actions Cron

5-field POSIX-style cron for workflow `schedule` triggers — UTC only, minimum interval 5 minutes.

5 fields: minute hour day-of-month month day-of-week

Kubernetes CronJob

5-field cron for `CronJob` resources — same syntax as Vixie cron, plus a `timeZone` spec field since Kubernetes 1.25.

5 fields: minute hour day-of-month month day-of-week

Quartz Cron

Java's Quartz Scheduler — 6 or 7 fields, seconds resolution, `L`/`W`/`#` tokens, and 1-indexed day-of-week.

6 or 7 fields: second minute hour day-of-month month day-of-week [year]

Spring Cron

Spring Framework's `@Scheduled` cron — 6 fields (with seconds), no `L`/`W`/`#`, and 0-indexed day-of-week like Unix.

6 fields: second minute hour day-of-month month day-of-week

Azure Logic Apps Cron

6-field NCronTab format for Azure Logic Apps recurrence triggers — seconds first, day-of-week 0–6, no step syntax.

6 fields: second minute hour day-of-month month day-of-week

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