⏰ Cron Expression Generator

Understanding Cron Expression Syntax

A cron expression is a compact string that tells a scheduler exactly when to run a task. The standard format used on Linux, macOS, and most cloud platforms consists of five fields separated by spaces. Each field controls a different unit of time, and together they define a precise recurring schedule.

The Five Fields

Special Characters

• Asterisk (*) matches every possible value for that field. For example, * in the hour field means "every hour."
• Comma (,) separates a list of specific values. Writing 1,15 in the day-of-month field means "on the 1st and 15th."
• Hyphen (-) defines an inclusive range. 9-17 in the hour field means "every hour from 9 AM through 5 PM."
• Slash (/) specifies a step interval. */10 in the minute field means "every 10 minutes" (0, 10, 20, 30, 40, 50).

By combining these characters you can express virtually any recurring schedule, from simple intervals to complex multi-day patterns. Understanding this syntax is the foundation for automating tasks reliably across servers, containers, and cloud services.

Cron in Linux, Unix, and macOS

The cron daemon has been a cornerstone of task automation on Unix-like operating systems since the 1970s. On modern Linux distributions and macOS, cron runs as a background service that wakes up every minute, reads each user's crontab file, and executes any jobs whose schedule matches the current time.

Managing Your Crontab

You interact with cron through the crontab command. Run crontab -e to open your personal crontab in a text editor. Each line follows the pattern minute hour day-of-month month day-of-week command. After you save and close the file, cron picks up the changes automatically.

• crontab -l lists all jobs in your current crontab
• crontab -e opens the crontab for editing
• crontab -r removes your entire crontab (use carefully)

Common Pitfalls

One of the most frequent issues with cron jobs is environment differences. Cron runs commands in a minimal shell environment, so paths and variables you rely on in your interactive terminal may not be available. Always use absolute paths to executables and scripts inside crontab entries. Another common mistake is forgetting to redirect output: by default, cron emails any stdout or stderr to the user, which can fill up mail queues silently. Redirect output to a log file or to /dev/null if you do not need it.

Timezone awareness is also important. Cron evaluates schedules according to the system clock. If your server is set to UTC but you want a job to run at 9 AM Eastern, you need to calculate the UTC equivalent or configure the CRON_TZ variable (supported on some systems). On macOS, launchd is the preferred scheduler, but cron is still fully functional and widely used for quick, simple scheduling tasks.

Common Cron Patterns and Examples

While the cron syntax is flexible enough to express nearly any schedule, most real-world use cases fall into a handful of common patterns. Keeping a reference of these patterns saves time and prevents mistakes when setting up new jobs.

Frequently Used Schedules

• * * * * * runs every single minute. Useful for health checks, queue workers, or monitoring scripts that need near-real-time execution.
• */5 * * * * runs every five minutes. A popular interval for syncing data between systems, refreshing caches, or polling external APIs.
• 0 * * * * runs once every hour, at the top of the hour. Great for hourly reports, log rotation, or periodic cleanup tasks.
• 0 0 * * * runs at midnight every day. The classic choice for nightly backups, database maintenance, and daily summary emails.
• 0 9 * * 1-5 runs at 9 AM every weekday (Monday through Friday). Perfect for business-hours automation like sending daily standup reminders or generating morning reports.
• 0 0 1 * * runs at midnight on the first day of every month. Ideal for monthly billing runs, report generation, or certificate renewal checks.
• 0 0 * * 0 runs at midnight every Sunday. A solid choice for weekly maintenance windows, full backups, or weekly digest emails.

Combining Patterns

You can combine special characters to build more targeted schedules. For example, 30 6,18 * * * fires at 6:30 AM and 6:30 PM every day, while 0 9-17 * * 1-5 runs every hour from 9 AM to 5 PM on weekdays only. The comma and range operators are especially powerful when used together, letting you define schedules like "every 15 minutes during business hours on the first and fifteenth of each month."

When building complex expressions, always verify them with a tool like this generator. A misplaced value can cause a job to run far more often than intended, potentially overloading your system or duplicating operations. Testing against the next five run times gives you immediate confidence that the schedule matches your expectations.

Cron in Cloud Services and Modern Platforms

Cron expressions have outgrown their Unix origins and are now a standard interface for scheduling across major cloud providers and modern application frameworks. Understanding how each platform implements cron-like scheduling helps you choose the right tool for your infrastructure.

AWS EventBridge (CloudWatch Events)

Amazon Web Services uses cron expressions in EventBridge Scheduler (formerly CloudWatch Events) to trigger Lambda functions, Step Functions, and other AWS services on a schedule. AWS extends the standard five-field format to six fields by adding a year field and supports a ? wildcard for day-of-month or day-of-week when the other is specified. For example, cron(0 12 ? * MON-FRI *) triggers at noon UTC every weekday. EventBridge also offers a simpler rate() syntax for basic intervals like rate(5 minutes).

Google Cloud Scheduler

Google Cloud Scheduler accepts standard Unix cron expressions and adds timezone support directly in the job configuration. You specify both a cron expression and a target timezone (such as "America/New_York"), and the scheduler handles daylight saving time transitions automatically. Targets can be HTTP endpoints, Pub/Sub topics, or App Engine services.

Azure Functions and Logic Apps

Microsoft Azure uses NCRONTAB expressions in Azure Functions timer triggers. These consist of six fields (adding seconds as the first field): {second} {minute} {hour} {day} {month} {day-of-week}. Azure Logic Apps also support recurrence triggers configured through cron-like patterns in the workflow definition.

Kubernetes CronJobs

Kubernetes provides a native CronJob resource that uses standard five-field cron expressions to schedule containerized workloads. The CronJob controller creates a new Job object at each scheduled time, and you can configure concurrency policies, history limits, and deadline tolerances. This is the go-to approach for periodic batch processing in container orchestration environments.

Regardless of the platform, the core cron syntax remains consistent. Mastering the five-field format covered on this page equips you to work with scheduling on any system, from a single Linux server to a global multi-cloud architecture.

🔒 100% Private & Free

All cron expression building and scheduling previews happen entirely in your browser. No data ever leaves your device. No server processing, no logging, no signup required.

Frequently Asked Questions

Related Tools