Cron Expression Parser

How it works

1. Paste a five-field cron expression: minute, hour, day of month, month, day of week. For example 30 2 * * 0 runs at 02:30 every Sunday.
2. Choose how many upcoming run times you want to see, from 1 to 20.
3. Press Explain cron. You get a readable description such as "At 02:30 on Sunday" and the list of concrete dates and times.
4. Compare the dates with what you intended. Off-by-one mistakes in day-of-week or step values show up immediately in the list.

Frequently asked questions

Which time zone are the next run times in?

They are calculated in your browser's local time zone, the one shown in your operating system settings. Servers usually run cron in UTC or the machine's configured zone, so shift the results accordingly when you compare them to a production schedule.

What syntax is supported?

The standard five fields with * for any value, comma lists (1,15), ranges (1-5), step values (*/10 or 1-30/5) and three-letter names for months (JAN-DEC) and weekdays (SUN-SAT). Both 0 and 7 mean Sunday. The special strings @hourly, @daily, @weekly, @monthly and @yearly are expanded to their five-field equivalents.

How are day-of-month and day-of-week combined?

As in Vixie cron: if both fields are restricted (neither is *), the job runs when either one matches, not both. So 0 0 1 * MON runs on the 1st of every month and on every Monday. This surprises many people, so check the list of next runs.

Does it support seconds or the year field?

Not yet. Six-field expressions used by Quartz, Spring or some Kubernetes controllers, and the optional seventh year field, are outside the classic crontab format this tool follows. Remove the seconds field to test the rest of the schedule.

Is the expression sent to a server?

No. Parsing and date calculation happen in your browser. There is nothing to upload and nothing to log.