welloddcomfortably different

Cron explainer

Data
Ready
Five-field Unix cron

Minute, hour, day of month, month, day of week. Enter the schedule without a command.

Try

In plain English

Ready

Enter a cron expression to read its schedule.

Expanded expression

Field by field

Minute
*No expression0-59
Hour
*No expression0-23
Day of month
*No expression1-31
Month
*No expression1-12 or JAN-DEC
Day of week
*No expression0-7 or SUN-SAT

Preview settings

Choose or type an IANA time zone.
Only runs strictly after this time.

Searches up to 8 years ahead. Missing local times are skipped; repeated times appear twice. Confirm your scheduler's clock-change behavior.

Upcoming runs

Choose a schedule to see matching dates.

    No preview yet.

    Your expression stays in this browser.

    Syntax reference
    *
    Every value in the field.
    1,15,30
    A list of specific values.
    9-17
    An inclusive, ascending range.
    */15 or 5-45/10
    A step within a field or range. Steps restart within that field.
    JAN-MAR, MON-FRI
    Three-letter month and weekday names, in any letter case.
    @daily
    A shortcut for 0 0 * * *. Hourly, weekly, monthly, and yearly shortcuts also work.

    Five fields only. Seconds, years, commands, and Quartz or AWS extensions are not supported. See the crontab manual for Unix cron syntax and day matching.

    Runs in your browser. Nothing is uploaded.All tools

    Cron explainer

    Read a five-field Unix cron expression in plain English. Check each field, try common schedules, and preview upcoming runs in a time zone you choose. Everything runs in your browser; nothing is uploaded.

    Which cron format does this tool support?

    Use five fields in this order: minute, hour, day of month, month, day of week. Supported syntax includes asterisks, comma-separated lists, ascending ranges, and positive steps. Month and weekday names use three letters, such as JAN and MON. Sunday can be 0 or 7. Enter the schedule only, without a command or username. Quartz, AWS, seconds, year fields, and the special characters ?, L, W, and # are not supported.

    Can I use shortcuts such as @daily?

    Yes. The tool expands @hourly, @daily, @midnight, @weekly, @monthly, @yearly, and @annually into five fields. @reboot is not a calendar schedule and cannot have upcoming dates.

    How do the two day fields work together?

    This tool follows Vixie cron day matching. If both day fields are restricted, a match in either field is enough. For example, 0 9 1 * MON runs on the first of the month and every Monday. If either day field starts with an asterisk, both fields must match. A full numeric range is still a restriction for this rule.

    Does */35 mean every 35 minutes?

    It selects minutes 0 and 35 within each hour. The gap from minute 35 to the next hour is 25 minutes. Steps restart inside their field; they do not measure a continuous interval. Use an explicit range for a different start: 5-59/15 selects minutes 5, 20, 35, and 50.

    How are time zones and daylight saving handled?

    The expression uses the selected time zone. The preview skips local times that do not exist during a forward clock change and includes both occurrences when a clock time repeats. Each run shows its UTC offset and UTC timestamp. Time zone rules come from your browser. Scheduler behavior varies, so confirm the settings of the system that will run your job. Choosing a zone here does not change that system.

    Why are there fewer upcoming runs than requested?

    The preview searches up to 8 years after the reference time. Sparse schedules may have fewer matches in that window. A valid expression can also have no matching dates, such as February 31 when the weekday field is unrestricted. This tool explains and previews schedules; it does not run jobs.

    Are my expressions saved or sent anywhere?

    No. Parsing, explanations, time zone lookup, and upcoming runs are calculated in your browser. Expressions are not uploaded, added to the URL, or saved. No account is required.

    More data tools