Cron Expression Builder
Build and validate cron expressions with a visual editor. See human-readable descriptions, preview next run times, and copy for crontab, Kubernetes, GitHub Actions, or any scheduler.
Cron expression
* * * * *
Every minute
* = every minute, */5 = every 5 min, 0,30 = at 0 and 30
* = every hour, 9 = at 9 AM, 9-17 = 9 AM to 5 PM
* = every day, 1 = 1st, 1,15 = 1st and 15th
* = every month, 1 = January, 1-6 = Jan through Jun
* = every day, 0 = Sunday, 1-5 = Monday to Friday
Common schedules
Next 5 run times
Based on your local time zone
Syntax reference
| Symbol | Meaning | Example |
|---|---|---|
| * | Every value | * in hour = every hour |
| */n | Every nth value | */15 in minute = every 15 min |
| a-b | Range from a to b | 9-17 in hour = 9 AM to 5 PM |
| a,b,c | Specific values | 1,15 in day = 1st and 15th |
Make sure your cron jobs actually run
A cron expression defines when a job should run. Heartbeat monitoring confirms that it did. Vantaj alerts you within minutes when a scheduled job misses its expected check-in.
Start monitoring freeHow cron expressions work
A cron expression is a five-field string that tells a scheduler when to run a job. Each field represents a time unit, read left to right: minute, hour, day of month, month, day of week. The scheduler evaluates the expression every minute and runs the job when all five fields match the current time.
The format was introduced in Unix V7 in 1979 and remains the standard scheduling syntax across crontab, Kubernetes CronJobs, GitHub Actions, AWS CloudWatch Events, Google Cloud Scheduler, and most task scheduling libraries in every major programming language.
Where cron expressions are used
Linux/macOS crontab: The original. Edit with crontab -e and add lines like 0 2 * * * /usr/local/bin/backup.sh to run a backup at 2 AM daily.
Kubernetes CronJobs: The spec.schedule field uses standard cron syntax to run containerized jobs on a schedule.
GitHub Actions: The schedule trigger accepts cron expressions in UTC. Common use: nightly builds, scheduled dependency updates, periodic data syncs.
AWS CloudWatch / EventBridge: Supports both cron and rate expressions. Note that AWS cron has 6 fields (adds year) and uses ? for "no specific value" in day fields.
Application schedulers: Libraries like node-cron, celery beat, APScheduler, and Hangfire all accept standard cron expressions for task scheduling within applications.