Cron expression

Explain a cron schedule, preview its next runs, or build one from dropdowns.

How to use it

  1. Paste a 5-field cron expression — its meaning and the next five run times appear as you type, with no button to press.
  2. The fields are minute, hour, day of month, month and day of week. Use * for every, */5 for every fifth, 1-5 for a range, and JAN–DEC or SUN–SAT for names.
  3. Switch to Build to pick each field from dropdowns instead of typing; the expression, its meaning and its next runs stay in sync.
  4. Copy the expression or the whole result, or download it as a .txt file.

Example

Expression

0 9 * * 1-5

Meaning and next runs

Minute: 0
Hour: 9
Day of month: every day
Month: every month
Day of week: from Monday to Friday

Next runs
(local time, with UTC beside each)

This runs at 09:00 on weekdays. The next-run times on the page are computed from the moment you open it, so they differ from this example.

Rules, limits and known issues

  • Only the standard 5-field Vixie cron is supported (minute hour day-of-month month day-of-week). There is no seconds field and no Quartz extensions: ?, L, W and # are reported as errors, never guessed.
  • Supported: * , lists (1,15), ranges (1-5), steps (*/5 and 10-50/10), month and weekday names (JAN–DEC, SUN–SAT, any case), and the @yearly @annually @monthly @weekly @daily @midnight @hourly macros.
  • @reboot has no schedule, so it is reported as an error instead of given a made-up time.
  • When both day-of-month and day-of-week are restricted (for example 0 0 13 * 5), the job runs when either one matches — the same OR rule Vixie cron uses.
  • Next-run times are computed in your browser’s local time zone and shown beside their UTC equivalent. There is no way to simulate a different server time zone.
  • The search looks at most 366 days ahead. A schedule that never fires within a year — like Feb 29 in a non-leap year — says so instead of showing nothing.
  • Daylight-saving time follows the browser clock: hours that do not exist are skipped, and a repeated hour runs twice, matching a real cron daemon.
  • Nothing is uploaded, stored or written to the URL. The tool only reads and explains; it never runs anything.

What people usually need next, once a schedule is clear.