Visual Builder · Instant Explain · Free

Cron Job Expression
Generator & Explainer

Build cron expressions visually, get plain-English descriptions, preview next run times, and browse a library of common schedules.

*
Minute
·
*
Hour
·
*
Day/Month
·
*
Month
·
*
Day/Week
Visual Cron Builder
Minute (0–59)
* :00 :30 */5 */15 */30
* = every, */5 = every 5 min, 0,30 = at :00 and :30
Hour (0–23)
* 12am 6am 9am 12pm 6pm
0 = midnight, 12 = noon, */6 = every 6 hours
Day of Month (1–31)
* 1st 15th Last 1&15
1-31, L = last day of month
Month (1–12)
* Jan Jun Dec Quarterly
1=Jan, 12=Dec, or use JAN, FEB...
Day of Week (0–7)
* Weekdays Weekend Mon Fri
0 or 7 = Sunday, 1 = Monday... 6 = Saturday
Every minute, every hour, every day.
Next 10 Scheduled Runs (UTC)

Common Cron Schedules

Click any schedule to load it into the builder.

Cron Syntax Reference

Special characters and their meanings in cron expressions.

CharacterMeaningExampleDescription
*Any value* * * * *Every minute
,Value list0 9,17 * * *At 9am and 5pm
-Range0 9 * * 1-5At 9am, weekdays only
/Step*/15 * * * *Every 15 minutes
LLast0 0 L * *Last day of month at midnight
WNearest weekday0 0 15W * *Nearest weekday to 15th
#Nth weekday0 0 * * 2#1First Tuesday of month
?No specific value0 0 ? * MONIgnored (use * for standard cron)

Cron FAQs

Common questions about cron jobs and cron expressions.

A cron job is a scheduled task that runs automatically at specified times on Unix/Linux systems. The name comes from Chronos (Greek god of time). Cron is a daemon that reads a crontab (cron table) file containing expressions that define when each task should run. They're used for automated backups, database maintenance, sending scheduled emails, data syncing, and much more.
Run crontab -e to edit your crontab file. Add a line with your cron expression followed by the command: 0 9 * * 1-5 /path/to/script.sh. Save and exit. Use crontab -l to list your cron jobs. On cloud platforms, AWS EventBridge, Google Cloud Scheduler, and GitHub Actions all support cron syntax for scheduled workflows.
Standard cron has 1-minute granularity — you can't schedule tasks more frequently than once per minute. For sub-minute scheduling, use sleep inside a script loop, or use tools like Supervisor, Celery Beat (Python), node-cron (JavaScript), or platform-specific solutions. AWS EventBridge supports 1-minute minimum intervals; GitHub Actions workflows have the same restriction.
By default, cron uses the system timezone of the server. You can override it per-crontab by adding CRON_TZ=America/New_York at the top of your crontab file. Cloud schedulers like Google Cloud Scheduler let you specify a timezone per job. Always document the timezone assumption in your crontab — server migrations between regions can silently change when jobs run.
Copied to clipboard!