Cron Expression Parser

Parse, validate, and build cron expressions with a visual editor and next run time calculator.

Runs locallyNo sign-upKeyboard first
Minute
*/15every 15 minutes
Hour
*every hour
Day (month)
*every day
Month
*every month
Day (week)
*every day of the week

Description

Every 15 minutes

Next 10 runs

UTC

Calculating…

Common presets

Cron cheat sheet

Field ranges

FieldRangeAllowed values
Second (6/7 fields)0-590 1 2 … 59
Minute0-590 1 2 … 59
Hour0-230 1 2 … 23
Day of Month1-311 2 3 … 31
Month1-121-12 or JAN-DEC
Day of Week0-60-6 or SUN-SAT (0 = Sunday, 7 = Sunday too)
Year (AWS, Quartz)1970-2199e.g. 2027 or 2026-2030

Special characters

CharacterMeaning
*Any value (wildcard)
,List separator (e.g., 1,3,5)
-Range (e.g., 1-5 means 1, 2, 3, 4, 5)
/Step (e.g., */5 means every 5, 1-10/2 means 1, 3, 5, 7, 9)
?No specific value — day fields only (Quartz, AWS)
LLast: L = last day of the month, 5L = last Friday
WNearest weekday: 15W = weekday nearest the 15th, LW = last weekday
#Nth weekday: MON#2 = second Monday of the month

Day of week

ValueDay
0Sunday (SUN)
1Monday (MON)
2Tuesday (TUE)
3Wednesday (WED)
4Thursday (THU)
5Friday (FRI)
6Saturday (SAT)

Month names

ValueMonth
1January (JAN)
2February (FEB)
3March (MAR)
4April (APR)
5May (MAY)
6June (JUN)
7July (JUL)
8August (AUG)
9September (SEP)
10October (OCT)
11November (NOV)
12December (DEC)

Special strings

StringEquivalent
@yearly0 0 1 1 *
@monthly0 0 1 * *
@weekly0 0 * * 0
@daily0 0 * * *
@hourly0 * * * *
@rebootRun at startup

Formats

FieldsUsed by
m h dom mon dowUnix cron, Kubernetes, GitHub Actions
s m h dom mon dowSpring, Quartz, node-cron
m h dom mon dow yearAWS EventBridge (day of week 1-7 = SUN-SAT)
s m h dom mon dow yearQuartz
Valid cron expression5 fields — standard cronUTCProcessed locally

What is a Cron Expression?

A cron expression is a string of five or six fields that defines a schedule for recurring tasks. Used in Unix cron jobs, Kubernetes CronJobs, GitHub Actions, and CI/CD pipelines, cron expressions specify when a command should run using minute, hour, day-of-month, month, and day-of-week fields. This parser shows the next run times and provides a visual builder.

Common use cases

  • Building cron schedules for CI/CD pipelines
  • Verifying when a Kubernetes CronJob will next execute
  • Converting human-readable schedules to cron syntax
  • Debugging why a scheduled task isn't running as expected
  • Understanding complex cron expressions from legacy systems

How to use

  1. 1Paste or type a cron expression (5 fields, or 6/7 with seconds or a year), or build one in the Visual builder.
  2. 2Read the plain-English description and the field breakdown; pick your timezone to see the next 10 run times.
  3. 3Copy the description and run times, or pick a preset to start from a common schedule.

Frequently asked questions

What does */5 mean in a cron expression?

The */5 syntax means 'every 5 units.' In the minute field, */5 means every 5 minutes (0, 5, 10, 15...). In the hour field, */5 means every 5 hours (0, 5, 10, 15, 20).

What is the difference between 5-field and 6-field cron?

Standard Unix cron uses 5 fields (minute, hour, day, month, weekday). Some systems add a 6th field for seconds at the beginning. Quartz scheduler and Spring use 6-field cron expressions.