Cron expression explainer

Paste a cron expression to read it in plain English and see the next 10 times it will run. Works with standard Unix cron, Quartz and AWS EventBridge, and marks mistakes in place.

Next runs
    Waiting for an expression

    The cron format

    ┌───────────── minute        0–59
    │ ┌─────────── hour          0–23
    │ │ ┌───────── day of month  1–31
    │ │ │ ┌─────── month         1–12 or JAN–DEC
    │ │ │ │ ┌───── day of week   0–6 or SUN–SAT (0 = Sunday)
    │ │ │ │ │
    * * * * *  command

    Each field takes a number, a list (1,15), a range (1-5), a step (*/10 or 0-30/10) or * for every value. Click a field card above the explanation to select that field in your expression.

    Common expressions

    ExpressionRuns
    */5 * * * *Every 5 minutes.
    0 * * * *Every hour, on the hour.
    0 9 * * 1-5At 09:00, Monday to Friday.
    30 2 * * 0At 02:30, on Sunday.
    0 0 1 * *At 00:00, on the 1st of the month.
    0 0 1 1 *At 00:00, on the 1st of the month, in January.
    0 9,17 * * *At 09:00 and 17:00.
    15 14 1 * *At 14:15, on the 1st of the month.

    Mistakes it catches

    • Day of month and day of week both set, which runs when either matches.
    • Schedules that never run, like the 31st in a month that doesn’t have one, or the 30th of February.
    • Uneven steps like */7, with the actual run times listed.
    • Backwards ranges like 22-2, with the two-part version suggested.
    • Quartz or AWS syntax in standard cron: ?, L, W and #.
    • Misspelled names like MONDAY or Sept, with the right three-letter name.
    • A whole crontab line pasted with its command, which is split off and ignored.

    Shortcuts

    Most cron versions accept these in place of the five fields:

    @yearly    0 0 1 1 *     (also @annually)
    @monthly   0 0 1 * *
    @weekly    0 0 * * 0
    @daily     0 0 * * *     (also @midnight)
    @hourly    0 * * * *
    @reboot    once, when the cron daemon starts

    Where cron expressions are used

    • crontab on Linux and macOS: crontab -e to edit, crontab -l to list.
    • Kubernetes CronJob and GitHub Actions schedule: standard five fields. GitHub runs in UTC and can be delayed at busy times.
    • AWS EventBridge: cron(0 9 ? * MON-FRI *), six fields, always UTC unless you use EventBridge Scheduler with a time zone.
    • Spring @Scheduled and Quartz: six or seven fields, starting with seconds.

    Checking when a job actually ran? Paste log times into the Unix timestamp converter.

    Questions people ask

    What do the five fields in a cron expression mean?
    In order: minute (0–59), hour (0–23), day of the month (1–31), month (1–12 or JAN–DEC) and day of the week (0–6 or SUN–SAT, where 0 is Sunday). 30 9 * * 1 means 09:30 every Monday.
    What does */5 mean in cron?
    Every 5th value, starting from the lowest. In the minute field, */5 runs at 0, 5, 10 … 55. Watch out with steps that don’t divide evenly: */7 runs at 0, 7 … 56 and then again at 0, a gap of only 4 minutes.
    Why does my job run more often than I expected?
    Usually because you set both the day of the month and the day of the week. In standard cron, the job runs when either matches. 0 9 13 * 5 runs every Friday and on the 13th of every month, not just on Friday the 13th.
    What time zone does cron use?
    The server’s local time zone, unless you set one (for example with CRON_TZ on some systems). Kubernetes CronJobs default to the controller’s zone, GitHub Actions and AWS EventBridge use UTC. The explainer can show next runs in UTC or your local time.
    What’s the difference between Quartz and standard cron?
    Quartz (used by Java schedulers, Spring and Jenkins plugins) adds a seconds field at the start and an optional year at the end, uses 1–7 for days of the week with 1 as Sunday, and needs ? in one of the day fields. It also supports L, W and #. AWS EventBridge uses a six-field format similar to Quartz, without seconds.
    ↑↓ move↵ openesc close