Cron Expression Parser & Evaluator 5-Part & 6-Part Cron • Plain English • Next Runs Timeline

Parse, validate, and convert any crontab or Quartz expression into natural human-readable English. Preview upcoming execution dates in local time or UTC with zero latency.

⚡ Quick Presets:

⏰

Cron Expression to Parse

Enter any 5-field (standard Unix/Linux) or 6-field (Quartz/cron with seconds) expression

Include seconds (6-part)

📖 Human Readable Schedule

Every minute

Field Structure Breakdown (Click to inspect)

📅

Next Scheduled Executions

Upcoming timestamps calculated from your system clock

Count:

#	Execution Timestamp	Relative Countdown	Action

🛠️

Schedule Builder Helper

Quickly construct common recurring intervals

Frequency:

Time of Day (HH:MM):

📖

Cron Syntax Cheat Sheet

Quick reference of special characters & symbols

*

Wildcard (Every / Any) — Matches all allowed values in that field.

,

Value List — Separates distinct values (e.g. 1,15,30).

-

Range — Defines a continuous inclusive range (e.g. 1-5 or MON-FRI).

/

Step Increments — Specifies intervals (e.g. */10 = every 10 units, 10-30/5).

?

No Specific Value — Quartz cron placeholder for Day-of-Month or Day-of-Week.

L

Last — Last day of month (e.g. L), or last specific weekday (e.g. 5L).

Understanding Cron Expressions & Crontab Schedules

Cron was originally developed as a daemon utility in Unix operating systems in 1979 by Ken Thompson. It enables software systems and site reliability engineers (SREs) to schedule recurring jobs, automated backups, email digests, web crawlers, and cloud functions at fixed times, dates, or intervals.

Standard 5-Part Cron (Unix/Linux)

Standard crontab format consists of 5 whitespace-separated fields:

┌───────────── Minute (0 - 59)
│ ┌─────────── Hour (0 - 23)
│ │ ┌───────── Day of Month (1 - 31)
│ │ │ ┌─────── Month (1 - 12 or JAN - DEC)
│ │ │ │ ┌───── Day of Week (0 - 6, 0=Sun or SUN - SAT)
* * * * *

6-Part Cron (Quartz & Cloud Schedulers)

Many enterprise and cloud platforms (such as Quartz.NET, Spring Framework, and Azure Functions) support an additional leading field for Seconds:

┌─────────────── Second (0 - 59)
│ ┌───────────── Minute (0 - 59)
│ │ ┌─────────── Hour (0 - 23)
│ │ │ ┌───────── Day of Month (1 - 31)
│ │ │ │ ┌─────── Month (1 - 12 or JAN - DEC)
│ │ │ │ │ ┌───── Day of Week (0 - 6)
0 * * * * *