Cron Parser
Reserved · Sponsored728 × 90 · zero layout shift
Paste a cron expression and get an instant plain-English translation plus a preview of exactly when it will fire next. Both 5-field (minute-level) and 6-field (with seconds) expressions are supported, along with standard step, range, list, and wildcard syntax. Everything is computed locally in your browser using your system clock and timezone, so the run times you see match what you'd get on your own machine.
Type a standard 5-field expression (minute hour day month weekday) or a 6-field expression with a leading seconds field.
The description updates as you type, translating fields like */15 * * * * into “Every 15 minutes” so you can sanity-check the schedule at a glance.
Adjust the run count (1–20) to see more or fewer upcoming fire times, calculated from the current moment forward in your browser's local timezone.
If a field is out of range or malformed, an error explains what failed so you can correct the specific field before deploying the schedule.
Before merging a new cron job, confirm in plain English that */30 8-18 * * 1-5 really means what you think it means.
See the next 5–20 fire times for a schedule to confirm it won't collide with a maintenance window or another job.
Check whether the discrepancy is a timezone mismatch between your local preview and the server's actual configured timezone.
Experiment with steps, ranges, and lists and watch the human-readable description update live to build intuition for the syntax.
A standard 5-field expression is minute hour day-of-month month day-of-week. A 6-field expression prepends a seconds field, letting jobs run more often than once a minute — this parser detects which format you've entered automatically.
Your browser's local timezone, exactly as your operating system reports it. If the job actually runs on a server in a different timezone (very common with crontab, which usually runs in UTC or system time), the wall-clock times will differ — check your server's configured timezone.
Yes. Steps (*/5), ranges (1-5), lists (1,15,30), wildcards (*), and named months/weekdays (JAN, MON) are all supported, matching standard cron syntax used by crontab and most schedulers.
Common causes are too many or too few fields, a value outside its field's valid range (e.g. 60 in the minute field), or an invalid range where the start is greater than the end. The error message names the specific problem.
Yes, this parser runs in non-strict mode, matching how most cron implementations behave: if both fields are restricted (not *), the job runs when either condition is satisfied.
Every 15 minutes
Times shown in your browser's local timezone — UTC (UTC+00:00).