Cron Expression Parser
Runs on your device. Nothing is sent.Nothing is ever uploaded - all parsing happens on your device.
Common schedulesAlso accepts @yearly, @monthly, @weekly, @daily, and @hourly.
In plain English
At 09:00, Monday through Friday
Field breakdown
Minute
0
Hour
9
Day of month
*
Month
*
Day of week
1-5
Next scheduled runs
Parse a cron expression into a human-readable schedule and see its next upcoming run times, entirely in your browser.
A cron expression is five space-separated fields - minute, hour, day of month, month, and day of week - that describe a recurring schedule, used by cron itself and by countless schedulers modeled after it (CI pipelines, cloud functions, task queues). This tool parses one into a plain-English description and a list of its next actual run times, entirely in your browser.
Frequently asked questions
What happens when both day-of-month and day-of-week are restricted?
Standard cron treats that specific combination as OR, not AND - the schedule fires whenever either field matches, unlike every other pair of fields (which must all match together). So "0 0 1 * 1" runs on the 1st of every month AND every Monday, not only on Mondays that happen to be the 1st.
What do the @daily, @weekly, and similar shorthands mean?
They're common aliases for a fixed schedule: @yearly/@annually is "0 0 1 1 *" (midnight, January 1st), @monthly is midnight on the 1st of every month, @weekly is midnight every Sunday, @daily/@midnight is midnight every day, and @hourly is the top of every hour.
Why do the next run times use my computer's local time?
Because that's what the browser's own clock and date calculations use - if the schedule is meant to run somewhere else (a server in a different time zone), interpret the field values with that server's time zone in mind rather than your own.