Cron Expression Parser
Enter a five-field crontab expression and the tool breaks it down field by field and lists the next runs, so you can check a schedule before it goes live.
| Minute | 00, 15, 30, 45(4) |
|---|---|
| Hour | 09–17(9) |
| Day of month | every |
| Month | every |
| Day of week | Mon–Fri(5) |
…
About this tool
A cron expression has five fields: minute, hour, day of month, month and day of week. An asterisk means every value, a comma separates a list, a hyphen gives a range and a slash sets a step, so */15 9-17 * * 1-5 means every 15 minutes between 09:00 and 17:59 on weekdays. Month and weekday names (JAN, MON) are accepted, and shortcuts such as @daily and @hourly expand to their classic forms.
When both day-of-month and day-of-week are restricted, most cron implementations run the job if either matches, and this parser follows that rule. Next run times are computed in your browser's timezone; servers usually run cron in UTC or their local zone, so compare with the timezone shown before trusting the exact hour.
Frequently asked questions
- Does it support seconds or year fields?
- No. It follows the classic five-field crontab format used by Linux cron, Kubernetes CronJobs and most schedulers. Six-field Quartz expressions are not supported.
- What does */5 mean?
- Every fifth value starting from the minimum: in the minute field it fires at :00, :05, :10 and so on.
- Which timezone are the next runs in?
- Your browser's local timezone, shown next to the list. Cron on a server uses the server's timezone, which is often UTC.
- Why does 0 0 31 2 * never run?
- February never has 31 days, so no real date matches. The tool tells you when an expression can never fire.