toolqik

210 · Date & Time

Cron Expression Generator

Build and explain cron schedules, and see the next run times.

Runs in your browser

Next runs

    About this tool

    Cron is the scheduler behind Linux crontabs, Kubernetes CronJobs, GitHub Actions, Vercel and countless job runners, and its five-field syntax is famously easy to get wrong. This cron expression generator explains any expression in plain English and lists the next run times, so you can check a schedule before you deploy it. Pick a preset, edit the fields one at a time, or paste an expression from your config.

    How to use it

    1. Type or paste an expression into the box, or click a preset such as Every 5 minutes.
    2. Change any of the five fields below the box; the full expression updates as you type.
    3. Read the plain-English description and check the Next runs list. Switch between My time and UTC to see when it fires on a server set to UTC.

    Cron syntax

    A 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)
    │ │ │ │ ┌───── day of week   (0–6 or SUN–SAT; 7 is also Sunday)
    │ │ │ │ │
    * * * * *
    SymbolMeaningExample
    *Every value* * * * * runs every minute
    ,A list of values0 9,18 * * * runs at 09:00 and 18:00
    -A range0 9 * * 1-5 runs Monday to Friday
    /A step: every nth value*/15 * * * * runs at minutes 0, 15, 30 and 45
    @daily and friendsShortcuts: @hourly, @daily, @weekly, @monthly, @yearly@daily is the same as 0 0 * * *

    Cron expression examples

    ExpressionRuns
    */10 * * * * Every 10 minutes
    0 9-17 * * 1-5 Every hour from 09:00 to 17:00, Monday to Friday
    */15 9-17 * * 1-5 Every 15 minutes during office hours on weekdays
    0 2 * * * Every day at 02:00, a common time for backups
    0 9,18 * * * Twice a day, at 09:00 and 18:00
    0 0 1,15 * * At midnight on the 1st and 15th of each month
    0 6 * * 6,0 At 06:00 on Saturdays and Sundays
    0 0 1 */3 * At midnight on the 1st of every third month (quarterly)
    59 23 28-31 * * At 23:59 on days 28 to 31; add a check in your script to run only on the last day

    Mistakes that catch everyone

    • Day of month and day of week. When both fields are restricted, cron runs when either matches, not both. 0 0 13 * 5 runs on every 13th and every Friday, not only on Friday the 13th. The description above always spells out which rule applies.
    • Time zones. Cron uses the time zone of the machine or service that runs it. GitHub Actions and Vercel run schedules in UTC by default, so 0 9 * * * fires at 09:00 UTC, which is 14:30 in India. Use the UTC switch to check.
    • Daylight saving time. In zones with DST, a job at 02:30 may be skipped on the night clocks go forward and run twice when they go back. Schedule important jobs outside 01:00–03:00, or run the server in UTC.
    • */n restarts every hour or day. */40 * * * * runs at minutes 0 and 40, so the gap is 40 minutes, then 20. Steps only divide evenly when n divides 60 (or 24 for hours).
    • The last day of the month. Standard cron has no “last day” symbol. Schedule days 28–31 and exit early in your script unless tomorrow is the 1st.

    Cron in popular platforms

    # Edit your crontab:  crontab -e
    # m  h  dom mon dow  command
    */5  *  *   *   *    /usr/local/bin/sync-orders >> /var/log/sync.log 2>&1
    0    2  *   *   *    /usr/local/bin/backup.sh
    
    # Times use the server's time zone. cronie (Fedora, RHEL, Arch) also accepts:
    CRON_TZ=Asia/Kolkata
    30 9 * * 1-5 /usr/local/bin/daily-report

    Quartz, Spring and AWS expressions

    Some schedulers use a longer format. Spring @Scheduled adds a seconds field at the start, so 0 */5 * * * * means every 5 minutes. Quartz does too, needs ? in one of the day fields (0 0/5 * * * ?) and supports L, W and #. AWS EventBridge uses six fields with a year at the end, such as cron(0 12 * * ? *). This tool reads the standard five-field format; drop the seconds or year field to check the rest of the schedule.

    FAQ

    What does * * * * * mean in cron?

    Every minute of every hour of every day. Each * means "every value" for its field: minute, hour, day of month, month and day of week.

    How do I run a cron job every 5 minutes?

    Use */5 * * * *. The step */5 in the minute field matches minutes 0, 5, 10 and so on up to 55.

    How do I run a cron job every day at a specific time?

    Put the minute first, then the hour. For 09:30 every day use 30 9 * * *. For weekdays only, use 30 9 * * 1-5.

    Which time zone does cron use?

    The time zone of the system or service running it. Linux crontabs use the server’s zone; GitHub Actions and Vercel use UTC by default; Kubernetes CronJobs accept a timeZone field.

    Does cron support seconds?

    Standard cron doesn’t; the smallest unit is one minute. Quartz, Spring and some libraries such as node-cron accept an optional seconds field at the start.

    Why does my job run on more days than expected?

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

    esc
    ↑↓ navigate↵ open