CRON Calculator

CRON is a Unix daemon that automatically executes commands or scripts at specific intervals. It is essential for automating repetitive tasks like backups, log rotation, updates, and more. With a CRON calculator you can translate any CRON expression to plain English and verify that your CRON jobs run at the exact time you need.

CRON Expression Format

A CRON expression has 5 fields separated by spaces:

Special Characters

• * - Any value
• , - List of values (1,3,5)
• - - Range of values (1-5)
• / - Step (* /5 every 5 minutes)

Common Examples

• 0 * * * * - Every hour
• 0 0 * * * - Every day at midnight
• 0 0 * * 0 - Every Sunday at midnight
• 0 */6 * * * - Every 6 hours
• 30 4 1,15 * * - At 4:30 on days 1 and 15 of each month

Follow these three steps to calculate CRON expressions and get plain English descriptions:

1. Enter the CRON expression

   Type your 5-field CRON expression in the main input field or use the individual selectors (minute, hour, day of month, month, day of week) to build it field by field. You can also pick one of the predefined examples to get started quickly.

2. Read the plain English description

   The calculator will automatically convert your CRON expression to plain English, telling you exactly when it will run. You will also see the next 5 execution dates and times to confirm the schedule is correct.

3. Copy and add to your crontab

   Once the expression is correct, use the "Copy" button to save it to your clipboard. Then run crontab -e in your Linux terminal and paste the expression along with the command you want to schedule.

With this free CRON calculator you can validate any expression before adding it to your crontab, avoiding syntax errors that could prevent your scheduled tasks from executing.

CRON is used in production environments to automate all kinds of system administration tasks. Here are some of the most common CRON use cases:

• Automated backups: Schedule daily or weekly backups of databases and critical files. For example, 0 2 * * * runs a backup script every night at 2:00 AM when server load is lower. This is one of the most common CRON jobs on any production server.
• Log rotation: Log files can grow quickly and fill the disk. With CRON you can run logrotate or custom scripts to compress and rotate logs periodically: 0 0 * * 0 /usr/sbin/logrotate /etc/logrotate.conf.
• Temporary cache cleanup: Delete temporary files and caches that are no longer needed. A task like 0 4 * * * find /tmp -type f -atime +7 -delete cleans files in /tmp older than 7 days.
• Scheduled report delivery: Generate and send reports via email automatically. For instance, a weekly sales summary every Monday at 8:00 AM with the expression 0 8 * * 1 /scripts/weekly-report.sh.
• Server synchronization: Keep directories synchronized across multiple servers using rsync. A CRON expression like 0 * * * * rsync -avz /data/ user@server:/backup/ replicates data hourly.
• SSL certificate renewal: Certbot can run automatically with CRON to renew Let's Encrypt certificates before they expire: 0 0 * * * certbot renew --quiet.
• Service monitoring: Healthcheck scripts that verify critical services are running and restart them if needed. For example, every 5 minutes: */5 * * * * /scripts/healthcheck-nginx.sh.

These are just a few examples of how to schedule Linux tasks with CRON. You can use our calculator to build and verify any expression before putting it into production.

To avoid issues and ensure your CRON jobs run reliably, follow these CRON best practices:

1. Redirect output to a log file

   By default, CRON emails any output to the user. It is better to redirect stdout and stderr to a log file for review:

   */5 * * * * /usr/local/bin/script.sh >> /var/log/script.log 2>&1

2. Always use absolute paths

   CRON runs commands with a minimal PATH (/usr/bin:/bin). If your script uses tools in /usr/local/bin, you must specify the full path or configure PATH in the crontab:

   30 2 * * * /usr/bin/python3 /home/user/scripts/cleanup.py

3. Do not assume environment variables

   CRON does not load user profile files (.bashrc, .bash_profile). If your script needs environment variables, define them within the script or at the top of the crontab:

   PATH=/usr/local/bin:/usr/bin:/bin

   [email protected]

   0 3 * * * /scripts/backup.sh

4. Schedule heavy tasks during off-peak hours

   Run backups, updates, and intensive processes between 2:00 AM and 5:00 AM when server usage is minimal. Avoid scheduling heavy tasks during peak hours to prevent impact on application performance.

5. Use descriptive comments in crontab

   Document each task with comments explaining what it does, who created it, and when. A well-documented crontab makes long-term maintenance much easier:

   # Nightly database backup - 2:30 AM

   30 2 * * * /scripts/backup-db.sh

6. Monitor job execution

   Implement logging and alerting. Have your scripts notify on failure using MAILTO or integrate with monitoring tools like Nagios, Datadog, Prometheus, or simply review logs periodically with grep.

7. Use the correct 5-field syntax

   Standard CRON syntax uses 5 fields. Do not confuse it with special keywords like @reboot, @daily, or @weekly, which are extensions in some systems (Vixie cron, cronie) and are not part of the POSIX standard. If you need portability across systems, always use the 5-field syntax and verify it with a CRON expression calculator.

Following these CRON best practices will help you maintain a stable system and avoid tasks that do not run as expected. Use our calculator to validate each expression before putting it into production.