What's the field order?

Standard Vixie cron: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12 or JAN-DEC), day-of-week (0-6 or SUN-SAT, where 0 and 7 both mean Sunday).

What syntax is supported?

* (any), */n (every n), a-b (range), a-b/n (range with step), a,b,c (list — each item can itself be a range or step), and three-letter names (JAN-DEC, SUN-SAT).

What happens when both day-of-month and day-of-week are restricted?

Per Vixie cron, when both fields are restricted (not *), the OR of the two is used — the job runs on any day matching either. When only one is restricted, AND semantics apply.

What timezone are the next runs in?

Your browser's local timezone. The 'next 5 runs' search starts from the next minute after 'now' and walks forward minute by minute, capped at 5 years to avoid infinite loops for impossible schedules (like Feb 30).

Does it support quartz-style 6/7-field cron with seconds?

No — this parser is strictly 5-field POSIX cron. For seconds-level cron, you'd want a quartz-compatible parser.

Is the expression uploaded?

No. Parsing and run computation happen entirely in your browser.

Cron Expression Parser

Explain a 5-field cron expression and compute its next 5 runs.

100% private — no uploads Developer ToolsFree & unlimited Read tutorial

See how it works

Watch a quick simulation of this tool in action — no file needed.

How to use Cron Expression Parser

Follow these steps — everything happens instantly in your browser.

1
Step 1. Enter a 5-field cron expression (e.g. */15 * * * *) or click a sample chip.
2
Step 2. Click Parse to see the human-readable description.
3
Step 3. Review the next 5 upcoming run times in your local timezone.
4
Step 4. Copy the run list with one click.