Cron Parser
Parse and validate cron expressions, including 6-field syntax with seconds, and translate them into plain English instantly. Check when a scheduled job will actually run, debug a cron schedule that silently failed, or convert a vague requirement into a working expression.
Usage examples
Checking when a batch job will actually run before deploying it
Before writing a cron expression into a config file, preview the list of next run times to confirm it fires exactly when you intended.
Translating a dense expression into plain language
If something like */15 8-20 * * 1-5 isn't immediately clear, the plain-language description spells out exactly what it means.
Debugging a cron job that silently isn't running
If a scheduled job never seems to fire, paste in the expression to check right away whether it has a syntax error.
Choosing between a comma list and a range for weekday scheduling
Not sure if 1,3,5 and 1-5 mean the same thing in the day-of-week field? Try both and compare the plain-language description and next run times side by side to see exactly how they differ.
Converting a vague requirement into a working expression
Told to run something "every 15 minutes during business hours on weekdays"? Start from a preset, then tweak it toward something like */15 9-17 * * 1-5 and confirm the next run times line up with what was asked.
Migrating a schedule from one job runner to another
Moving a scheduled task from a legacy system into something like a Kubernetes CronJob or GitHub Actions workflow? Paste the old expression in to get a plain-language explanation you can double-check against the new platform's docs before copying it over.
Checking whether a seconds-precision expression parses as expected
Working with a scheduler library that supports an optional leading seconds field, like 0 */30 * * * *? Paste it in to confirm it's being read as a 6-field expression rather than misinterpreted as the standard 5-field format.
Quick reference
| Cron expression | Description |
|---|---|
| * * * * * | Every minute |
| */2 * * * * | Every 2 minutes |
| */5 * * * * | Every 5 minutes |
| */10 * * * * | Every 10 minutes |
| */15 * * * * | Every 15 minutes |
| */30 * * * * | Every 30 minutes |
| 0 * * * * | Every hour |
| 0 */2 * * * | On the hour, every 2 hours |
| 0 */3 * * * | On the hour, every 3 hours |
| 0 */6 * * * | On the hour, every 6 hours |
| 0 */12 * * * | On the hour, every 12 hours |
| 0 0 * * * | At 12:00 AM |
| 30 2 * * * | At 02:30 AM |
| 0 9 * * * | At 09:00 AM |
| 0 9,17 * * * | At 09:00 AM and 05:00 PM |
| 0 9 * * 1-5 | At 09:00 AM, Monday through Friday |
| */15 9-17 * * 1-5 | Every 15 minutes, between 09:00 AM and 05:59 PM, Monday through Friday |
| 0 9 * * 1 | At 09:00 AM, only on Monday |
| 0 0 * * 0 | At 12:00 AM, only on Sunday |
| 0 10 * * 6,0 | At 10:00 AM, only on Sunday and Saturday |
| 0 0 1 * * | At 12:00 AM, on day 1 of the month |
| 0 0 15 * * | At 12:00 AM, on day 15 of the month |
| 0 0 1,15 * * | At 12:00 AM, on day 1 and 15 of the month |
| 0 0 1 */3 * | At 12:00 AM, on day 1 of the month, every 3 months |
| 0 0 1 1 * | At 12:00 AM, on day 1 of the month, only in January |
Frequently asked questions
Is the expression I type sent to a server?
No. Parsing and calculation happen entirely in your browser, and what you type is never sent to a server.
Does this support expressions with seconds (6 fields)?
Yes. Both the standard 5-field cron format (minute, hour, day, month, weekday) and the 6-field format with a leading seconds field are detected automatically.
What time zone are the next run times based on?
They're calculated using your current device's (browser's) time zone, with no separate setting. If the actual server runs in a different time zone, the displayed times will differ accordingly.
Can I use aliases like @daily or @hourly?
Yes. Common aliases such as @yearly, @monthly, @weekly, @daily, and @hourly are all supported.
If the next run times are wrong, is the expression broken?
Not necessarily — the most common cause is a time zone mismatch, not a bad expression. Since the next run times are calculated in your browser's local time zone, an expression that's perfectly correct for a server running in UTC (or any other zone) will show different clock times here. Before assuming the expression itself is wrong, check what time zone the actual scheduler runs in and mentally (or manually) offset accordingly.
What do *, ,, -, and / actually mean in a field?
* means "every value" for that field. A comma-separated list like 1,15,30 matches exactly those values. A hyphenated range like 9-17 matches every value in between, inclusive. A slash like */15 or 9-17/2 means "every Nth value" starting from the beginning of the field (or from the start of a range) — so */15 in the minutes field fires at :00, :15, :30, and :45. These can be combined, e.g. 0,30 9-17 * * 1-5.
What's the difference between day-of-month and day-of-week, and what happens if I set both?
The 5th field is day-of-week (0–6 or names, where both 0 and 7 typically mean Sunday) and the 3rd field is day-of-month (1–31). If you restrict both away from * at the same time, most cron implementations (including the one used here) treat them as OR'd together — the job runs when either condition is met, not only when both are. This trips a lot of people up, so if you only mean one of the two, leave the other as *.
Does this tool support non-standard fields like a year field or L/W characters?
Standard 5-field and seconds-prefixed 6-field cron is fully supported, including *, ranges, lists, and steps. Some less common vendor-specific extensions (such as a trailing year field, or L for "last day of month" and W for "nearest weekday" used by tools like Quartz) may not be recognized — if you see an unexpected parse error with one of those, it's worth checking whether your target scheduler actually needs that extension or if a standard equivalent will do.