What is a Cron Expression?

A cron expression is a string comprising five or six fields separated by white space that represents a set of times, used to schedule tasks on Unix-like operating systems.

What do the 5 stars in cron mean?

The five stars represent the five time fields: Minute (0-59), Hour (0-23), Day of Month (1-31), Month (1-12), and Day of Week (0-6).

How do I handle timezones in Cron?

Standard cron runs based on the system's local time. To handle timezones, you either set the system timezone to UTC (recommended for servers) or handle timezone logic within the script being called.

Can Cron run every second?

Standard Unix cron has a minimum granularity of one minute. To run tasks every second, you would need to use a loop in your script or a different scheduler like systemd timers.

What is the difference between * and ?

The asterisk (*) means 'every' unit (e.g., every minute). The question mark (?) is used in some non-standard cron implementations (like Quartz) to specify 'no specific value' for Day of Month or Day of Week, but standard Linux cron does not support it.

Free Online Cron Expression Generator & Schedule Builder

Complete Guide to Cron Expressions

A Cron Expression is a string consisting of five or six fields that represent a time schedule. It is primarily used in Unix-like operating systems (Linux, macOS, BSD) to schedule commands or scripts to run periodically at fixed times, dates, or intervals.

Whether you are automating database backups, scheduling email newsletters, or running system maintenance scripts, mastering the crontab syntax is an essential skill for developers and system administrators.

Cron Expression Structure

A standard cron expression consists of five fields separated by spaces. Here is the breakdown:

Field	Required	Allowed Values	Allowed Special Characters
Minutes	Yes	0-59	* , - /
Hours	Yes	0-23	* , - /
Day of Month	Yes	1-31	* , - / ? L W
Month	Yes	1-12 or JAN-DEC	* , - /
Day of Week	Yes	0-6 or SUN-SAT	* , - / ? L #

Special Characters Explained

* (Asterisk): Represents "every" value. For example, a * in the minutes field means "every minute".
, (Comma): Used to separate items in a list. MON,WED,FRI in the weekday field means Monday, Wednesday, and Friday.
- (Hyphen): Defines a range. 10-15 in the hours field means hours 10, 11, 12, 13, 14, and 15.
/ (Slash): Specifies increments or steps. */15 in the minutes field means "every 15 minutes" (0, 15, 30, 45).

Common Cron Examples

Here are some of the most frequently used schedules:

Expression	Description
`* * * * *`	Run every minute.
`0 0 * * *`	Run daily at midnight.
`0 0 * * 0`	Run weekly on Sunday at midnight.
`0 9-17 * * 1-5`	Run on the hour from 9 AM to 5 PM, Monday through Friday.
`/5 * * *`	Run every 5 minutes.
`0 0 1,15 * *`	Run at midnight on the 1st and 15th of every month.

Tips and Best Practices

Always use absolute paths: When writing a cron job, your environment variables (like $PATH) might differ from your interactive shell. Always specify the full path to your interpreter and script, e.g., /usr/bin/python3 /home/user/scripts/backup.py.
Redirect Output: By default, cron sends an email to the user if the script produces any output. To prevent this or capture logs, redirect standard output and error: 0 0 * * * /path/to/script.sh >> /var/log/myjob.log 2>&1.
Check Timezones: Cron runs on the system's local time. If your server is in UTC but you want a job to run at 9 AM EST, you must calculate the offset or change the server's timezone.
Use Comments: In your crontab file, you can add comments by starting a line with #. This helps you remember what complex schedules are doing.

Common Mistakes

Mistaking Day of Week 0 and 7: In most systems, both 0 and 7 represent Sunday. However, some systems might only accept 0. It is safer to use 0 for Sunday or the string SUN.
Forgetting File Permissions: The script you are trying to schedule must have the executable permission (chmod +x script.sh), or you must run it via an interpreter.
Environment Differences: A script that runs perfectly in your terminal might fail in cron because environment variables like API keys or library paths are missing.

Frequently Asked Questions (FAQ)

How do I list my current cron jobs?

Open your terminal and type crontab -l. This will list the cron jobs for the currently logged-in user. To edit them, use crontab -e.

What is the difference between system cron and user cron?

User cron jobs are stored in /var/spool/cron/crontabs/username and run with that user's permissions. System cron jobs are defined in /etc/crontab or /etc/cron.d/ and usually include a field specifying which user the command should run as (often root).

Can I schedule a job for every second?

Standard cron is limited to one-minute granularity. You cannot natively schedule a job to run every second. To achieve this, you would need to write a script with a loop and a sleep command, or use a process manager like Systemd timers or Supervisord.

Does this tool support Quartz or AWS Cron?

This tool focuses on standard Unix/Linux cron syntax (5 fields). AWS CloudWatch Events and Quartz Scheduler use slightly different syntax (often 6 fields including Year or Seconds). While the core logic is similar, please verify specific extensions for those platforms.

What does "2>&1" mean in a cron job?

It is a shell redirection operator. File descriptor 1 is Standard Output (stdout), and 2 is Standard Error (stderr). 2>&1 redirects the error output to the standard output stream, allowing you to capture both success messages and error messages in a single log file.