Cron Expression Parser
Decode a cron expression into plain English, see the next run times in your local time zone, and inspect each field. Supports 5- and 6-field crons with ranges, lists, steps and names.
6/9/2026, 9:00:00 AMin 24h6/10/2026, 9:00:00 AMin 2d6/11/2026, 9:00:00 AMin 3d6/12/2026, 9:00:00 AMin 4d6/15/2026, 9:00:00 AMin 7d6/16/2026, 9:00:00 AMin 8d| Minute | 0 | minute 0 |
| Hour | 9 | hour 9 |
| Day of month | * | every day |
| Month | * | every month |
| Day of week | 1-5 | weekday 1, 2, 3, 4 and 5 |
About the cron expression parser
Paste a cron expression and Bytewrench explains it in plain English, shows the next several run times in your local time zone, and breaks down each field. It understands standard 5-field crons plus optional 6-field (with seconds), and supports ranges, lists, steps (*/n) and month/day names like JAN and MON.
It's the quickest way to sanity-check a schedule before committing it to a crontab, CI pipeline or scheduler — and it runs entirely in your browser.
Turns cryptic expressions into a readable sentence.
Computes the upcoming executions in your local time, with relative timing.
Ranges, lists, steps, names (JAN/MON) and optional seconds field.
Common schedules you can load and tweak.
Frequently asked questions
What do the five cron fields mean?
In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, Sunday=0). A sixth field at the front adds seconds.
How do day-of-month and day-of-week interact?
When both are restricted (not *), standard cron treats them as OR — the job runs if either matches. This tool follows that same rule.
What does */15 mean?
A step value: */15 in the minute field means every 15 minutes. Steps also work with ranges, e.g. 0-30/10.
Are the run times in my time zone?
Yes. The next run times are computed and shown in your browser's local time zone.