Cron Expression Builder

Free Cron Expression Builder -- Visual Editor with Next Run Times

The Toololis Cron Expression Builder helps you create cron expressions visually without memorizing the 5-field syntax. Set each field with simple inputs, see the human-readable description update in real time, and verify the schedule by checking the next 10 execution times. Copy the expression with one click and paste it into crontab, Kubernetes CronJobs, GitHub Actions, Jenkins, or any scheduler.

Understanding cron syntax

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

• Minute (0-59) -- which minute of the hour
• Hour (0-23) -- which hour of the day (24-hour format)
• Day of month (1-31) -- which day of the month
• Month (1-12) -- which month of the year
• Day of week (0-6) -- which day of the week (0 = Sunday)

Each field supports wildcards (*), specific values, ranges (1-5), lists (1,3,5), and step values (*/10). The combination of these operators gives cron expressions extraordinary flexibility for scheduling recurring tasks.

Common cron schedules explained

Here are the most frequently used cron expressions and what they mean:

• * * * * * -- Every minute. Useful for health checks or queue workers.
• 0 * * * * -- Every hour at minute 0. Good for hourly reports.
• 0 0 * * * -- Daily at midnight. Classic for nightly backups.
• 30 9 * * 1-5 -- Weekdays at 9:30 AM. Perfect for business-hours tasks.
• 0 0 1 * * -- First day of every month at midnight. Monthly billing, reports.
• 0 0 * * 0 -- Every Sunday at midnight. Weekly maintenance window.
• 0 0 1 1 * -- January 1st at midnight. Annual tasks.

Where cron expressions are used

Cron is the de facto standard for time-based job scheduling across virtually every platform:

• Linux/macOS crontab -- the original cron daemon for scheduled system tasks
• Kubernetes CronJobs -- scheduled container workloads in k8s clusters
• GitHub Actions -- schedule trigger in workflow YAML files
• Jenkins -- build triggers using cron syntax
• AWS CloudWatch Events / EventBridge -- scheduled Lambda invocations
• Vercel / Netlify Cron -- serverless scheduled functions
• WordPress WP-Cron -- scheduled content publishing and maintenance

Advanced cron syntax tips

Beyond the basics, cron expressions support powerful combinations:

• Step values with ranges: 1-30/5 in the minute field triggers at minutes 1, 6, 11, 16, 21, 26
• Multiple lists: 0,30 in the minute field triggers twice per hour at :00 and :30
• Combining day fields: when both day-of-month and day-of-week are specified (not *), most cron implementations use OR logic -- the job runs if either condition matches

Timezone considerations

Standard cron runs in the server's local timezone. For distributed systems, UTC is recommended. Kubernetes CronJobs default to the kube-controller-manager timezone (usually UTC). This tool calculates next execution times using your browser's local timezone, so adjust accordingly for server deployments.