EN
My tools

Cron Expression Parser (Cron to English)

Explain a crontab or Quartz cron expression in plain English and list its next run times in any time zone, with daylight-saving clashes flagged and clear errors.

5 fields = crontab (Vixie / cronie). 6–7 fields = Quartz (seconds first, optional year).
In plain English
At 09:30, on Monday through Friday
Next run
2026-11-10 09:30
Dialect
crontab (5 fields)
Daylight-saving clashes
0
runs in this list that fall in a skipped or repeated hour

Read as a standard crontab line (Vixie cron / cronie): minute, hour, day of month, month, day of week (0 or 7 = Sunday). When both day fields are restricted, the job runs if either matches.

Next 10 runs at or after 2026-11-10 00:00 (UTC)
Run time (UTC)Day
2026-11-10 09:30Tue
2026-11-11 09:30Wed
2026-11-12 09:30Thu
2026-11-13 09:30Fri
2026-11-16 09:30Mon
2026-11-17 09:30Tue
2026-11-18 09:30Wed
2026-11-19 09:30Thu
2026-11-20 09:30Fri
2026-11-23 09:30Mon
My tools →
Advertisement

Cron expressions are compact but hard to read. This parser explains a crontab or Quartz expression in plain English and lists its next run times in the time zone you choose, flagging any run that falls in an hour skipped or repeated by a daylight-saving change. It understands ranges, steps, lists, month and weekday names, the @ macros and the Quartz L, W, # and ? markers, and names the field when something is wrong.

How to use this tool

  1. Paste the expression: 5 fields for crontab, or 6–7 for Quartz (seconds first, optional year).
  2. Set the start date, time and the time zone the scheduler runs in.
  3. Read the English description and the dialect it was read as.
  4. Check the next run times and any daylight-saving warnings in the table.

Formula

Crontab fields are minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC) and day of week (0–7, where 0 and 7 are Sunday, or SUN–SAT). Quartz puts seconds first, numbers weekdays 1 (Sunday) to 7 (Saturday), allows a year field, and needs "?" in one day field.

Following Vixie cron, if both day fields are restricted the job runs when either matches; if either starts with "*", both must match. Quartz adds L (last day, or last given weekday as 6L), L-3 (three days before the last), W (nearest weekday) and # (the nth weekday, as 2#2).

Example

30 9 * * 1-5 reads "At 09:30, on Monday through Friday"; from 1 January 2026 (a Thursday) it next runs that same morning. The Quartz expression 0 15 10 ? * 6L runs at 10:15 on the last Friday of each month — 30 January 2026 first.

Frequently asked questions

What does "*/15" mean?

A step: starting from the lowest value, every 15th one. In the minute field that is minutes 0, 15, 30 and 45. A step that does not divide 60, like */7, restarts at minute 0 every hour.

Why does restricting both day fields behave oddly?

Standard cron treats "day 13 and Friday" as "the 13th OR any Friday", not "Friday the 13th". The parser follows that rule and says "or" in the description. Quartz avoids the problem by requiring "?" in one of the two fields.

What happens at a daylight-saving change?

A wall-clock time such as 02:30 may not exist on the day clocks go forward, and 01:30 may happen twice when they go back. Vixie cron and cronie run a fixed-time job from a skipped hour right after the change and run it only once in a repeated hour; other schedulers differ. The table flags those runs so you can decide.

Sources

Last updated:

Cite or embed this tool
APA

kakaoCalc. (2026, November 8). Cron Expression Parser (Cron to English). https://kakao.mobile/tools/cron-expression-parser/

MLA

“Cron Expression Parser (Cron to English).” kakaoCalc, 8 Nov. 2026, kakao.mobile/tools/cron-expression-parser/.

Paste this code into your page. The widget runs in your visitors' browsers, shows no ads and keeps a link back to this page. Embedding terms

Advertisement