Cron Parser
Paste a cron expression to see what it means in plain English and when it will fire next. Supports standard five-field syntax and the common @hourly / @daily / @weekly / @monthly / @yearly aliases.
Next-run times are computed in your local time zone using your browser's clock.
Plain English
Next 5 runs (your local time)
Next scheduled run times will appear here.
Field reference
| Field | Range | Special |
|---|---|---|
| Minute | 0–59 | * , - */N |
| Hour | 0–23 | * , - */N |
| Day of month | 1–31 | * , - */N |
| Month | 1–12 or JAN–DEC | * , - */N |
| Day of week | 0–6 (Sun=0) or SUN–SAT | * , - */N |
Aliases: @yearly = 0 0 1 1 *, @monthly = 0 0 1 * *, @weekly = 0 0 * * 0, @daily = 0 0 * * *, @hourly = 0 * * * *.
Day-of-month and day-of-week interact
POSIX-style cron evaluates day-of-month and day-of-week with an OR rule when both are restricted. For example 0 12 1 * 1 fires at noon on the 1st of every month and every Monday — not only Mondays that fall on the 1st. If you want “only Mondays that are the 1st”, you have to filter inside the job.
FAQ
What does 0 12 1 * 1 mean?
Noon on the 1st of every month or noon every Monday. Standard cron treats day-of-month and day-of-week as OR when both are restricted.
Why is */5 * * * * not exactly every 5 minutes?
It is — but it always lands on minutes that are multiples of 5 (0, 5, 10, ...), not on offsets from when you started the job. */5 means “values divisible by 5 within the field range”.
Are seconds supported?
Not in this parser. Standard Unix cron has five fields and no seconds. Some schedulers (Quartz, Spring) add a sixth seconds field — paste those into a parser that supports the six-field flavor.
Which time zone are the next runs in?
Your browser's local time zone. The label above the list shows the zone offset for clarity.