Cron Expression Builder

Cron Expression Builder

Build

Quick presets:
Daily at
Weekly on at
Monthly on day at
* * * * * Copied!

Runs every minute.


Parse

    What Is a Cron Expression?

    A cron expression is a compact, 5-field schedule format used by Linux/Unix cron, most CI/CD platforms, and countless job schedulers to describe recurring run times: minute hour day-of-month month day-of-week. Each field accepts a wildcard (*, meaning "every"), a specific value, a comma list, a range, or a step - which is exactly what makes cron both compact and easy to misread at a glance.

    This tool lets you build an expression visually with dropdowns and presets, or paste an existing expression to get a plain-English description plus the next 5 times it will actually fire - all computed locally in your browser.

    Cron Field Reference

    FieldAllowed valuesSpecial syntax
    Minute0-59*, 1,15,30, 10-20, */15
    Hour0-23*, 9,17, 9-17, */6
    Day of month1-31*, 1,15, 1-5
    Month1-12*, 3,6,9,12, 6-8
    Day of week0-6 (0 = Sunday, 7 also accepted as Sunday)*, 1-5 (weekdays), 0,6 (weekend)

    When both day-of-month and day-of-week are restricted (neither is *) in the same expression, a date matches if it satisfies either field - this is standard cron behavior, not a bug, and this tool's parser and next-run calculator both follow it exactly.

    Why Use This Cron Tool

    Build Without Memorizing SyntaxPick values from dropdowns or a preset button and get a correct 5-field expression every time.
    Plain-English DescriptionsEvery expression - built or pasted - is translated into a sentence you can sanity-check at a glance.
    See the Next 5 RunsConfirm an expression actually does what you expect before deploying it, with real computed timestamps.
    100% Client-SideNo cron library, no server round-trip - everything is computed locally in your browser.

    Frequently Asked Questions

    Does this tool send my cron expressions to a server?

    No. Building, parsing, describing, and computing upcoming run times all happen entirely in your browser using JavaScript - nothing is uploaded or sent to a server.

    What cron syntax does the parser understand?

    A standard 5-field expression (minute hour day-of-month month day-of-week). Each field can use *, a single value, a comma list like 1,15, a range like 1-5, a step like */15, or a combination like 1-5/2.

    What happens when both day-of-month and day-of-week are restricted?

    Standard cron semantics apply: when both fields are restricted (neither is *), a date matches if it satisfies either field, not both. If only one of the two is restricted, only that one needs to match.