// IT TOOLS & CALCULATORS
| 50+ TOOLS
ADVERTISEMENT
[ ADSENSE 728×90 — REPLACE WITH YOUR AD UNIT ]
🕐 CRON EXPRESSION BUILDER & EXPLAINER
// Build, validate and understand cron job schedules with plain English descriptions
ADVERTISEMENT
[ ADSENSE IN-CONTENT AD — INSERT YOUR AD UNIT ]

Cron Expression Builder — Create and Understand Cron Job Schedules

Our free cron expression builder helps you create, test and understand cron schedules with plain English descriptions. Whether you're scheduling Linux cron jobs, AWS EventBridge rules, Kubernetes CronJobs, GitHub Actions scheduled workflows or database maintenance tasks — this tool instantly translates between cron syntax and human-readable descriptions.

Cron Expression Format Explained

A standard cron expression consists of five fields separated by spaces:

  • Minute (0–59) — when in the hour to run
  • Hour (0–23) — which hour (24-hour clock, UTC by default)
  • Day of Month (1–31) — which day of the month
  • Month (1–12) — which month
  • Day of Week (0–6, Sunday=0) — which day of the week

Cron Special Characters

  • * — Any value (every minute, every hour, etc.)
  • , — List separator (1,3,5 = 1st, 3rd and 5th)
  • - — Range (1-5 = 1 through 5)
  • / — Step values (*/15 = every 15 units)

Common Cron Schedule Examples

  • 0 2 * * * — Daily at 2:00 AM (good for backups)
  • */5 * * * * — Every 5 minutes (health checks, queue processing)
  • 0 9 * * 1-5 — Weekdays at 9:00 AM (business hours jobs)
  • 0 0 1 * * — First day of every month at midnight (monthly reports)
  • 0 */4 * * * — Every 4 hours (log rotation, sync jobs)
  • 30 23 * * 0 — Sunday at 11:30 PM (weekly maintenance window)

Cron Best Practices

Always specify cron jobs in UTC to avoid issues with daylight saving time. Add random jitter (sleep $((RANDOM % 60))) to jobs that run at round numbers to avoid thundering herd problems when many servers run the same job simultaneously. Always log cron output — use command >> /var/log/cronjob.log 2>&1 to capture both stdout and stderr.