Cron Expression Generator

The Cron Expression Generator transforms cryptic cron syntax (*/5 9-17 * * 1-5) into something you can actually read and build. The visual editor has controls for each of the five fields (minute, hour, day-of-month, month, day-of-week) with options like "every N", "specific values", "range", or raw input. As you configure, the tool generates the cron expression, translates it to plain English ("every 5 minutes from 9am to 5pm, Monday through Friday"), and shows the next 10 run times so you can verify the schedule matches what you intended.

Cron is the oldest and still most common scheduling system in Unix/Linux. It runs behind the scenes for database backups, log rotation, monitoring alerts, periodic cleanup, analytics jobs, cache warming, and thousands of other automated tasks. Modern systems (Kubernetes CronJob, AWS EventBridge, GCP Cloud Scheduler, Jenkins) all use cron syntax or variations. Getting the expression right is critical — a wrong cron can run tasks every minute instead of every month, overload your servers, or skip essential backups. This tool eliminates that risk by showing you exactly when your cron will run before you deploy it.

Cron expressions have 5 fields for standard cron, or 6 for some variants (like Quartz, which adds seconds).

Standard cron (5 fields):

``
minute hour day_of_month month day_of_week
0-59 0-23 1-31 1-12 0-7 (0 and 7 are Sunday)
``

Special characters:

- * — every value (wildcard)
- */N — step: every Nth value (e.g., */5 = every 5 minutes)
- N-M — range: from N to M (e.g., 9-17 = 9am-5pm)
- N,M — list of values (e.g., 0,15,30,45 = at 0, 15, 30, 45 minutes)
- - — range separator
- Combined: 0-5,10,20-25 — 0-5, 10, and 20-25

Special strings (nicknames):

- @yearly or @annually → 0 0 1 1 * (midnight Jan 1)
- @monthly → 0 0 1 * * (midnight first of month)
- @weekly → 0 0 * * 0 (midnight Sunday)
- @daily or @midnight → 0 0 * * * (midnight)
- @hourly → 0 * * * * (top of each hour)
- @reboot — at system startup (non-standard)

Day of week conventions:

Values 0-7 where 0 and 7 both mean Sunday. Some systems also accept names: SUN, MON, TUE, WED, THU, FRI, SAT.

Common patterns:

- 0 0 * * * — daily at midnight
- */15 * * * * — every 15 minutes
- 0 9 * * 1-5 — 9am weekdays
- 0 */4 * * * — every 4 hours
- 0 0 1,15 * * — 1st and 15th of each month at midnight
- 0 2 * * 0 — 2am every Sunday
- */30 9-17 * * 1-5 — every 30 min during business hours weekdays

Implementations and variants:

- Unix cron (standard): 5 fields.
- Vixie cron (most Linux): standard + @nicknames.
- Quartz (Java, Spring): 6-7 fields (seconds at start, optional year at end).
- Kubernetes CronJob: standard 5 fields.
- AWS EventBridge: standard or 6 fields with year.
- GCP Cloud Scheduler: standard.
- GitHub Actions: standard.

Timezone handling:

- Standard cron runs in server timezone (usually UTC).
- Kubernetes 1.24+ supports spec.timeZone field.
- AWS EventBridge: explicitly set timezone or defaults to UTC.
- GCP Cloud Scheduler: explicit timezone field.

Common mistakes:

- Confusing day-of-month (third field) with day-of-week (fifth field).
- Using 0/15 vs */15 — some implementations accept both, others only */15.
- Assuming the day-of-month and day-of-week are ANDed (they are ORed when both specified).
- Missing that 0 0 * * * means midnight, not "every 0 seconds".
- Forgetting timezone — DST transitions can cause unexpected behavior.

Next run calculation:

Good cron tools calculate next run times by iterating: current time + 1 minute, check if matches, next minute if not. This is O(720 minutes per day max) but typically finds matches within minutes.

Standard Unix cron vs Quartz cron: Unix cron has 5 fields. Quartz (Java, Spring) has 6-7 fields (seconds at start, optional year at end). Most systems use Unix cron; Quartz is specific to Java scheduling.

Crontab vs systemd timers: Crontab is the traditional Unix cron. systemd timers are the modern alternative for Linux — more powerful (dependencies, fuzzy times, unit activation) but more complex syntax. Both work; cron is simpler.

Cron vs Kubernetes CronJob: Cron lives on a Linux host. CronJob runs as a Kubernetes resource, scheduled on cluster nodes. For cloud-native systems, CronJob provides monitoring, logs, history, and cluster-level scheduling.

Cron vs AWS EventBridge schedule: EventBridge is AWS serverless scheduler. Trigger Lambda, ECS, Step Functions. Uses similar cron syntax with timezone support. More reliable than cron on EC2 instance (which dies when instance dies).

Cron vs GCP Cloud Scheduler: GCP Cloud Scheduler — similar to EventBridge. Triggers Cloud Functions, HTTP endpoints, Pub/Sub. Cron syntax with timezone support.

Cron vs Celery Beat (Python): Celery Beat is a Python-specific task scheduler used with Celery workers. Different syntax from cron but can accept cron expressions. Provides Python-native integration.

Cron vs Airflow: Airflow is a workflow orchestrator, not just a scheduler. Use Airflow when jobs have dependencies (job A then job B after A succeeds). Use cron for independent periodic tasks.