navaja.dev / cron

Cron expression explainer

Type a cron schedule to see what it means in plain English and exactly when it runs next. Handy for crontab, Kubernetes CronJobs, GitHub Actions and CI schedules.

    Next runs

      Fields
      FieldValueMeans

      How to read a cron expression

      A standard cron expression has five fields separated by spaces: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC) and day of week (0–7 or SUN–SAT, where both 0 and 7 are Sunday). The job runs whenever the current time matches every field.

      Cron cheat sheet

      Gotchas

      Questions

      What does */5 * * * * mean?

      Every 5 minutes: at minute 0, 5, 10 and so on of every hour, every day.

      How do I run a cron job every weekday?

      Use 1-5 in the last field. For example 0 9 * * 1-5 runs at 09:00 Monday through Friday.

      Is Sunday 0 or 7 in cron?

      Both. Standard cron accepts 0 and 7 for Sunday, and names like SUN work too.

      What time zone does cron use?

      The time zone of the machine or service running it. GitHub Actions uses UTC; Kubernetes CronJobs can set timeZone. This tool shows next runs in your browser's zone or in UTC.

      Why does my job run on the wrong days?

      If both day-of-month and day-of-week are restricted, cron runs when either matches. Set one of them to * to require only the other.

      Can cron run every 30 seconds?

      Not directly: the smallest unit is one minute. A common workaround is two entries, one of them starting with sleep 30.

      Does this support Quartz or AWS cron?

      No, this tool checks standard 5-field cron as used by crontab, Kubernetes and GitHub Actions. It tells you when an expression uses Quartz-only syntax like seconds, L, W, # or ?.