Build Cron Expressions Visually

Understanding Cron Expressions

Cron is a time-based job scheduler found in Unix-like operating systems including Linux and macOS. It allows users to schedule commands or scripts to run automatically at specified intervals, from every minute to once a year. The schedule is defined by a cron expression -- a compact string of five fields that represent minute, hour, day of month, month, and day of week. Mastering cron syntax is essential for system administrators, backend developers, and DevOps engineers who need to automate backups, data processing, health checks, report generation, and countless other recurring tasks.

The Five Fields Explained

A standard cron expression consists of five space-separated fields: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or Jan-Dec), and day of week (0-6 or Sun-Sat, where 0 is Sunday). An asterisk (*) in any field means "every possible value." The step syntax */N means "every Nth value" -- so */5 in the minute field triggers at 0, 5, 10, 15, and so on. You can also use commas for lists (1,15 means the 1st and 15th), hyphens for ranges (9-17 means 9 through 17), and combine these for complex schedules like 0 9-17/2 * * 1-5 (every 2 hours from 9 AM to 5 PM, Monday through Friday).

Common Cron Patterns and Best Practices

The most frequently used cron schedules include: every 5 minutes (*/5 * * * *) for health monitoring, daily at midnight (0 0 * * *) for log rotation, and weekly backups (0 2 * * 0) on Sunday at 2 AM. When designing schedules, avoid running resource-intensive jobs at the same time -- stagger them by a few minutes. Use absolute paths for all commands in crontab entries, and redirect output to log files (>> /var/log/myjob.log 2>&1) so you can troubleshoot failures. Always test your cron expression with a tool like this one before deploying to production, and verify the next execution times match your expectations.