Paste a cron expression and find out what it actually does: a plain-English description, a validity check that names the field at fault, and the next run times so you can confirm the schedule matches what you intended. Ranges, comma lists, step syntax, named months and weekdays, wrapping ranges like 22-2, the @daily aliases and six-field expressions with seconds are all handled. It also gets the rule most online parsers get wrong — when both the day-of-month and day-of-week fields are restricted, cron fires when either matches, not both, so 0 0 1 * MON runs on the first of the month and on every Monday. Seeing the next five runs listed is usually what catches a mistake; a schedule that reads plausibly can still fire at the wrong time. Everything runs in your browser.
| Syntax | Means | Example |
|---|---|---|
| * | Every value | * * * * * — every minute |
| 5 | Exactly this value | 0 5 * * * — 05:00 daily |
| 1-5 | A range | 0 9 * * 1-5 — 09:00 on weekdays |
| 1,15 | A list | 0 0 1,15 * * — 1st and 15th |
| */15 | Every nth | */15 * * * * — every 15 minutes |
| 10-20/5 | Every nth in a range | minutes 10, 15 and 20 |
| MON, JAN | Named day or month | 0 0 * JAN MON |
| @daily | Alias | Same as 0 0 * * * |
In order: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–7, where both 0 and 7 mean Sunday). A sixth field at the front, where supported, is seconds.
Usually because the day-of-month and day-of-week fields are both set. Cron treats that as OR, not AND — 0 0 1 * MON fires on the 1st AND on every Monday, not only on Mondays that fall on the 1st. Leave one of the two as * to get the behaviour most people intend.
Every 15 units through the field, starting at its minimum. In the minute field that is :00, :15, :30 and :45. You can combine it with a range too: 10-20/5 in the minute field means minutes 10, 15 and 20.
The next run times here are computed in UTC and displayed in your local timezone for reference. Your actual cron daemon uses the server's timezone, which is frequently UTC on cloud hosts but not always — check before relying on an exact local hour.
Partly. The question mark is accepted and treated as a wildcard, and six-field expressions with seconds work. The Quartz-specific L (last), W (weekday) and # (nth weekday) tokens are not supported, since they do not exist in standard cron.
No. Parsing and the schedule calculation happen entirely in your browser. Expressions you paste — which can reveal internal job names and timings — are never sent to a server.
Each field is expanded into the explicit set of values it matches, handling wildcards, single values, ranges, comma lists, step syntax such as */15 and 10-20/5, ranges that wrap around the end of the field like 22-2 for hours, and the named month and weekday tokens. Both the standard five-field form and the six-field form with leading seconds are accepted, along with the @daily and @hourly aliases and the Quartz question mark, which is treated as a wildcard. Day 7 is folded into day 0 so both spellings of Sunday behave the same. The description is generated from the expanded sets rather than from the raw text, which is what lets it collapse a contiguous weekday run into 'Monday through Friday' and recognise an evenly spaced set as a step. Next-run calculation iterates forward from the current minute, but skips a whole day whenever the date cannot match and a whole hour whenever the hour cannot, so a yearly schedule resolves in milliseconds instead of crawling through half a million minutes. It also implements the rule most tools get wrong: when both the day-of-month and day-of-week fields are restricted, a date matches if EITHER does, not both — so '0 0 1 * MON' fires on the first of the month and on every Monday. All arithmetic is in UTC, so a daylight-saving change cannot shift a predicted run.