Skip to main content
Epoch Calculator
UTC 17:34:12

Cron Expression Tester

Paste any cron expression. See the next 10 execution times in your timezone, a plain-English summary, and a per-field breakdown. Supports five-field (Unix) and six-field (AWS / Quartz) variants.

Cron expression
✓ Every 15 minutes, between 07:00 AM and 07:59 PM, Monday through Friday
Field breakdown
Minute
*/15
every 15
Hour
7-19
7–19
Day
*
Any day
Month
*
Any month
Day of week
1-5
Mon–Fri
Next 10 runs
1Mon, Aug 31 2026 07:00:001788159600in 37h 25m
2Mon, Aug 31 2026 07:15:001788160500in 37h 40m
3Mon, Aug 31 2026 07:30:001788161400in 37h 55m
4Mon, Aug 31 2026 07:45:001788162300in 38h 10m
5Mon, Aug 31 2026 08:00:001788163200in 38h 25m
6Mon, Aug 31 2026 08:15:001788164100in 38h 40m
7Mon, Aug 31 2026 08:30:001788165000in 38h 55m
8Mon, Aug 31 2026 08:45:001788165900in 39h 10m
9Mon, Aug 31 2026 09:00:001788166800in 39h 25m
10Mon, Aug 31 2026 09:15:001788167700in 39h 40m
Common patterns
Syntax cheat sheet
Fields (5): minute · hour · day-of-month · month · day-of-week
Operators: * any · N exact · N-M range · N,M,O list · */N step
Ranges: minute 0–59 · hour 0–23 · day 1–31 · month 1–12 (or Jan–Dec) · day-of-week 0–6 (Sun=0)
Six-field variant (AWS / Quartz) prepends a seconds field with the same operators.

Frequently asked questions

What is a cron expression?

A cron expression is a five-field string that describes a recurring schedule: minute, hour, day of month, month, and day of week. The asterisk means "every", a number is an exact match, comma-separated lists mean "any of these", a hyphen is a range, and a slash is a step. For example "*/15 7-19 * * 1-5" means every 15 minutes between 7am and 7pm, Monday through Friday.

How do I validate a cron expression?

Paste your expression into the input above. If it is valid you will see the plain-English summary, a per-field breakdown, and the next 10 execution times in the timezone you select. If the expression is malformed, the tool tells you which field failed and what the allowed range is. For example, "Constraint error, got value 99 expected range 0-59".

What is the difference between five-field and six-field cron?

Five-field cron is the classic Unix variant: minute, hour, day-of-month, month, day-of-week. Six-field cron adds a seconds field at the start; it is used by some schedulers (notably AWS EventBridge and Quartz) when sub-minute precision is required. This tool accepts both; six-field expressions are detected automatically by token count.

How do I run a cron job every 15 minutes during business hours?

Use "*/15 7-19 * * 1-5". This evaluates to every 15 minutes, between 7am and 7pm UTC (or whichever timezone you select), Monday through Friday. The first field "*/15" is a step expression that triggers at 0, 15, 30, and 45 minutes past the hour; "7-19" restricts the hour to the inclusive range 7 through 19; "1-5" restricts the day of week to Monday through Friday.

Does this support AWS EventBridge or Quartz expressions?

Yes. AWS and Quartz add a six-field variant with seconds at the start, plus extensions like "?" for "any value" in day-of-month or day-of-week, and "L" for the last day of the month. These are accepted by the parser, though some edge-case combinations (mixed "?" usage) follow the original Quartz semantics, not the AWS overlay.

Why are my next-run times off by an hour during the spring or fall?

Daylight saving transitions can produce surprising results in cron schedules. A run scheduled for 02:30 in the United States during the spring-forward transition will be skipped that morning because 02:00–03:00 does not exist; in the fall-back transition it will run twice if your scheduler does not deduplicate. Always pick a timezone explicitly using the dropdown above and verify the next runs match what you expect across DST boundaries.