Cron Expression Explainer

Paste a standard 5-field cron expression and get a plain-English description plus the next ten times it will run, in UTC or in your local time.

Use the tool

Why this tool exists

Cron strings are compact and easy to misread. Is "0 9 * * 1-5" weekdays at nine, and does "*/15 9-17" run at 17:45? A wrong schedule means a backup that never runs or a job that fires every minute, and you only find out later.

This tool parses the expression, checks every field for range errors, and explains it in English. It then lists the next ten run times so you can check the schedule against your expectations. Names such as mon-fri and jan, and shortcuts like @daily and @hourly are understood. When both day-of-month and day-of-week are set, it follows the usual rule that either can match.

How to use it

  1. Paste a cron expression with five fields: minute, hour, day of month, month, day of week.
  2. Choose whether to show run times in UTC or local time.
  3. Read the plain-English meaning.
  4. Compare the next ten run times with what you intended.

Frequently asked questions

Which cron syntax is supported?

Standard five-field cron: numbers, lists, ranges, steps, * and ?, month and weekday names, and the aliases @hourly, @daily, @weekly, @monthly and @yearly. Seconds fields, Quartz extras such as L, W or #, and year fields are not supported.

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

If both are restricted, the job runs when either one matches, as classic cron does. If only one is restricted, only that one counts.

Which time zone does my cron run in?

That depends on the scheduler. Many servers use UTC, but crontab uses the system zone and some cloud schedulers let you set one. Compare the UTC and local lists to see the difference.

Why does it say no run found?

The search looks about eight years ahead. An expression such as 0 0 31 2 * (31 February) never matches, so no run is listed. This is usually a sign of a mistake in the schedule.