Cron Expression Parser
Paste a crontab expression and get what it means in plain English plus the next ten run times in the time zone of your choice — or start from a preset and tweak. Parsed entirely in your browser.
New to this? Read the Cron Expression Parser guide →
Next 10 runs
The five fields, left to right
| Field | Allowed | Examples |
|---|---|---|
| Minute | 0–59 | 0, */15, 5-20 |
| Hour | 0–23 | 0, 9-17, */6 |
| Day of month | 1–31 | 1, 15, 1-7 |
| Month | 1–12 or JAN–DEC | *, 6-8, DEC |
| Day of week | 0–7 or SUN–SAT (0 and 7 = Sunday) | 1-5, SUN, 6 |
Syntax: * means any, , lists values, - ranges, / steps. Macros like @daily and @hourly are accepted. One famous quirk, handled the standard way here: when both day-of-month and day-of-week are restricted, the job runs when either matches — see the guide for why that trips people up.
Run times are computed in the time zone you pick — crucial, because cron fires on the server's clock, and "0 9 * * 1-5" means 9am in whatever zone that server keeps. Everything is parsed locally in your browser.
Frequently asked questions
What do the five fields of a cron expression mean?
Left to right: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC), and day of week (0–7 or SUN–SAT, where both 0 and 7 are Sunday). * means any value, commas list values, dashes give ranges, and /n steps (*/15 = every 15th).
Why does my day-of-month + day-of-week cron run more often than expected?
Because of cron’s oldest quirk: when both day fields are restricted, the job runs when either one matches, not both. "0 0 13 * 5" fires every 13th and every Friday — not just Friday the 13th. The parser applies this standard rule, so the run list shows you the real schedule.
What time zone do the next-run times use?
Whichever you pick — that matters because cron fires on the server’s wall clock, and cloud schedulers (Kubernetes, GitHub Actions) default to UTC. A "9am" job on a UTC scheduler does not run at your 9am unless you live on UTC.
Are @daily and @hourly supported?
Yes. The standard macros (@yearly, @monthly, @weekly, @daily, @midnight, @hourly) are expanded to their five-field equivalents before parsing.