Free Online Cron Expression Generator, Builder & Explainer

1. The 5-Field Standard Crontab Architecture (RFC Standard)

Every standard Linux and Unix cron expression consists of 5 space-delimited fields evaluated sequentially from left to right. Each field controls a specific unit of time.

• Field 1 (Minute): 0 to 59 — specifies the exact minute of the hour.
• Field 2 (Hour): 0 to 23 — specifies the hour in 24-hour military time (0 = midnight, 12 = noon, 23 = 11 PM).
• Field 3 (Day of Month): 1 to 31 — specifies the calendar day of the month.
• Field 4 (Month): 1 to 12 or standard three-letter abbreviations (JAN - DEC).
• Field 5 (Day of Week): 0 to 6 or SUN - SAT (both 0 and 7 represent Sunday in standard Unix cron).

┌───────────── Minute (0 - 59)
│ ┌───────────── Hour (0 - 23)
│ │ ┌───────────── Day of Month (1 - 31)
│ │ │ ┌───────────── Month (1 - 12 or JAN - DEC)
│ │ │ │ ┌───────────── Day of Week (0 - 6 or SUN - SAT, 0=Sun)
│ │ │ │ │
* * * * *

2. Cron Operators & Syntax Rules Explained

Combining cron operators unlocks powerful recurring schedules without writing complex timing logic in application code.

• Wildcard (*): Matches every possible value for that field (e.g. * * * * * = runs every single minute).
• Step Values (/): Specifies intervals (e.g. */5 in minutes = every 5 minutes; 0 */3 * * * = every 3 hours on the hour).
• Range Operator (-): Specifies inclusive boundaries (e.g. 0 9-17 * * * = hourly from 9:00 AM through 5:00 PM).
• List Separator (,): Specifies discrete values (e.g. 0 0 1,15 * * = at midnight on the 1st and 15th of each month).

3. Essential Production Crontab Recipes

Here are the most frequently deployed schedule patterns across servers, databases, and cloud workflows:

• Every 5 minutes: */5 * * * *
• Every 15 minutes: */15 * * * *
• Every hour on the hour (:00): 0 * * * *
• Every night at midnight (00:00): 0 0 * * *
• Every workday (Mon-Fri) at 8:30 AM: 30 8 * * 1-5
• Weekly database backup (Sunday at 2:00 AM): 0 2 * * 0
• Twice daily sync (8:00 AM & 8:00 PM): 0 8,20 * * *
• Monthly billing report (1st of month at midnight): 0 0 1 * *

4. Output Redirection, Error Logging & Environment Variables

By default, cron emails command output to the local system user mailbox. In modern cloud setups, standard practice is to redirect output to log files or cloud logging agents.

• Redirect standard output and errors to log: 0 4 * * * /app/cleanup.sh >> /var/log/cleanup.log 2>&1
• Discard all output completely: 0 * * * * /app/ping.sh > /dev/null 2>&1
• Set custom PATH in crontab: Add 'PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' at the top of your crontab file.
• Set recipient email for failures: Add 'MAILTO=alerts@example.com' at the top of crontab.

# Example Crontab File Header with Variables & Logging:
SHELL=/bin/bash
PATH=/usr/local/bin:/usr/bin:/bin
MAILTO=devops@example.com

# Runs database backup every night at 2:30 AM with full output logging
30 2 * * * /usr/local/bin/pg_backup.sh >> /var/log/pg_backup.log 2>&1

5. Cross-Platform Scheduling: Linux, Kubernetes, GitHub Actions & Cloud

Cron expressions are utilized across virtually every modern cloud and DevOps platform:

• Linux / Unix Crontab: Managed via 'crontab -e' (user crontabs) or '/etc/crontab' (system crontabs with username field).
• Kubernetes CronJobs: Runs containerized batch tasks on scheduled intervals with automatic pod cleanup.
• GitHub Actions: Triggers automated continuous integration pipelines, security scans, and nightly test suites.
• AWS EventBridge (CloudWatch Events): Triggers serverless AWS Lambda functions and AWS ECS container tasks.