Cron expression parser
Runs entirely in your browser. Your files and data never leave your device.
Every 5 minutes
| Minute | 0-59, */5, 1-30 |
|---|---|
| Hour | 0-23 |
| Day of month | 1-31 |
| Month | 1-12 |
| Day of week | 0-7 (0 and 7 = Sunday) |
About this tool
A cron expression packs a schedule into five fields: minute, hour, day of month, month, and day of week. Reading one at a glance is hard, especially with ranges, steps, and lists mixed together. This tool takes an expression like 0 9 * * 1-5 and turns it into a sentence you can actually read, plus a list of its next five run times in your local time zone.
What exactly does it show me?
Type or paste a five-field expression and the tool produces two things: a plain-English description (“At 09:00, Monday through Friday”) and a preview of the next five times that schedule will actually fire, converted to your browser’s local time zone. It understands the usual cron syntax: asterisks, ranges like 1-5, steps like */15, comma-separated lists, and the @daily/@hourly/@weekly style shorthand macros some schedulers accept. If the expression is malformed, the tool reports that instead of guessing at what you meant.
Is my cron expression sent anywhere?
No. Everything runs in your browser using two small JavaScript libraries bundled into the page, one for the English description and one for computing run times, with no server call involved. The expression you type never leaves your machine, so you can check a schedule from a private deployment config or a cron job you’d rather not paste into a public site. This also holds for the localized versions of this page: the description and run times are translated the same way, entirely client-side, whichever language you’re reading in.
What is it useful for?
Common uses: verifying a schedule before you commit it to a crontab or CI config, double-checking a @daily or @hourly macro actually means what you think, or figuring out when a colleague’s job actually fires without doing the day-of-week math yourself. It’s also a fast way to catch a common mistake, like mixing up the minute and hour fields, before a job runs at 3am instead of 3pm. See the crontab(5) man page for the full field syntax and the Wikipedia article on cron for background on the format’s history.