Day fields have special behavior
When both day-of-month and day-of-week are restricted, traditional Unix cron runs when either field matches. This parser follows that behavior.
Minute0–59Hour0–23Day of month1–31Month1–12Day of week0–7
Schedule explained
Upcoming executions
Common schedules
The server timezone matters
Cron normally uses the scheduler host’s timezone unless configured otherwise. Select the same IANA timezone as your server to preview accurately.
Clock changes affect jobs
A local time may be skipped or repeated during daylight-saving transitions. Actual daemon behavior can vary, so verify critical schedules on the target system.
Five-field cron reference
| Field | Values | Examples |
|---|---|---|
| Minute | 0–59 | 0, */15, 5,35 |
| Hour | 0–23 | 9-17, 0,12 |
| Day of month | 1–31 | *, 1, 1-15/2 |
| Month | 1–12 or JAN–DEC | JAN, 1,6,12 |
| Day of week | 0–7 or SUN–SAT | 1-5, MON,FRI |
Cron parser FAQ
Does this support Quartz cron?
No. This tool targets classic five-field Unix cron. Quartz, AWS EventBridge and some frameworks use six or seven fields and different special characters.
Are L, W, # and ? supported?
No. Those belong to Quartz-like dialects, not portable Unix crontab syntax.
When is usage counted?
One usage is recorded when you explicitly parse a schedule. Selecting presets, copying, and changing the timezone do not add uses until Parse is pressed.