Home / Tools / Cron schedule explainer

Cron schedule explainer

Paste a cron schedule to see what it means in plain English and the next five times it will run, in your own time zone.

  • Code tool
  • Runs in your browser
  • Tested 19 November 2026
  • Sources
Five fields: minute, hour, day of month, month, day of week. Macros such as @daily work too.

Next runs

    The five fields

    FieldAllowed values
    Minute0 to 59
    Hour0 to 23
    Day of month1 to 31
    Month1 to 12, or jan to dec
    Day of week0 to 7, or sun to sat. Both 0 and 7 mean Sunday.
    • * means every value.
    • 1,15 is a list, and 9-17 is a range that includes both ends.
    • */15 is a step: every 15th value, so minutes 0, 15, 30 and 45. Steps work on ranges too: 0-30/10 is 0, 10, 20 and 30.
    • Shortcuts: @hourly, @daily (or @midnight), @weekly, @monthly and @yearly.

    The day-of-month and day-of-week trap

    If you restrict both day fields, cron runs when either matches, not both. 0 0 13 * 5 runs at midnight on every 13th and every Friday, not only on Friday the 13th. If one of them starts with *, the usual "both must match" rule applies. This explainer follows cronie and Vixie cron, the cron found on most Linux systems.

    Other gotchas

    • Time zone. Cron uses the server's time zone, which is often UTC on cloud machines. GitHub Actions schedules always run in UTC. The next runs above are shown in your browser's time zone.
    • Clock changes. In cronie, a time that's skipped when the clocks go forward never runs, and a time that's repeated when they go back runs twice. The list above leaves out times that don't exist. To be safe, avoid scheduling important jobs between 01:00 and 03:00 local time, or run the server on UTC.
    • Steps don't carry over. A step only counts within its own field, so */23 in the hour field means 00:00 and 23:00 each day, not every 23 hours.
    • Percent signs. In a crontab line, % means a new line. Write \% in commands such as date +\%F.
    • A bare environment. Cron jobs run with a minimal PATH and no login shell, so use full paths to programs and files. Our Linux command line guide covers paths.
    • Some systems add a sixth field for seconds or years, such as Quartz and AWS EventBridge. This tool covers the standard five.

    Sources

    Where the formulas and figures on this page come from. We test every tool against worked examples from these before publishing.