Cron Parser

Translate cron expressions into plain English, see a field-by-field breakdown, and preview the next 5 run times in your timezone.

100% Private
Your files never leave your device
Lightning fast
Optimised for speed
No sign-up
Use instantly, no account
Cron expression

Standard 5-field cron (minute, hour, day-of-month, month, day-of-week).

Every…

Daily

Weekly / Monthly

In plain English

At 09:00 AM, only on Monday

Field breakdown
  • Minute00
  • Hour99
  • Day of month*any
  • Month*any
  • Day of week11
Next 5 runsUTC
  • Mon, Jul 13, 09:00 AMin 7 days
  • Mon, Jul 20, 09:00 AMin 14 days
  • Mon, Jul 27, 09:00 AMin 21 days
  • Mon, Aug 3, 09:00 AMin 28 days
  • Mon, Aug 10, 09:00 AMnext month

Paste a cron expression and instantly get a plain-English description, a field-by-field breakdown, and the next five times the schedule will fire — in your local timezone. Curated presets cover the common cases, and everything runs in your browser.

How to use Cron Parser

  1. 1Type or paste a 5-field cron expression (or pick a preset).
  2. 2Read the plain-English translation of what it does.
  3. 3Inspect the per-field breakdown — minute, hour, day-of-month, month, day-of-week.
  4. 4See the next 5 fire times with absolute date and a relative “in 3 hours” label.

What the next-runs preview shows you

Cron expressions are easy to misread — a stray comma or off-by-one and your job runs once a year instead of once a day. Primova computes the actual next 5 fire times from the expression using the standard Vixie-cron rules (including the day-of-month / day-of-week “OR” semantics), so you can sanity-check the schedule against a clock instead of guessing from the syntax.

Times are shown in your device’s local timezone, with the timezone label next to them so there’s no confusion about UTC drift.

Supported cron syntax

Standard 5-field cron is fully supported: wildcards (*), single values, ranges (1-5), comma lists (1,3,5), step values (*/15 and 0-30/5), and month/day name aliases (JAN-DEC, SUN-SAT). The day-of-month and day-of-week fields follow Vixie semantics — if both are restricted, a date matches when either condition is true.

Quartz-only extensions like L, W, and # aren’t evaluated for next runs (those are Java schedulers’ extras), but the English translation still works on them via cronstrue.

Frequently asked questions

No. Parsing, translation, and next-run calculation all happen in your browser, so the expression — and anything you paste alongside it — never leaves the page.
Standard 5-field cron with *, A, A-B, A,B,C, A-B/N, */N, plus JAN-DEC and SUN-SAT name aliases. Both day-of-month and day-of-week fields follow Vixie-cron’s OR rule when both are restricted.
The English translation handles them, but next-run calculation here is limited to the standard 5-field syntax. Quartz extensions like L, W, and # aren’t evaluated for next runs.
Your device’s local timezone — its name is shown next to the list. Cron schedules themselves are timezone-agnostic; whatever scheduler runs them controls the actual TZ.
Because February never has a 30th. Primova searches up to 5 years ahead and reports an empty list when an expression can’t match a real date, instead of looping forever.
Yes — free with no sign-up or limits.

Still have questions?

If you can’t find the answer you’re looking for, our support team is here to help.

Contact Support
Secure Fast Private
More tools

Keep going.

Browse all tools