Cron Expression Generator

Key features

• Five classic fields — minute, hour, day-of-month, month, weekday — each validated for ranges, steps (*/5), lists (0,15,30), ranges (1-5, JAN-MAR) and combinations.
• Month and weekday names are accepted case-insensitively (MON, wed), and both 0 and 7 count as Sunday per cron convention.
• Nine presets from “every minute” to “yearly” fill all fields in one tap, including the workhorse “weekdays at 9:00”.
• A plain-English sentence explains the schedule — including the cron quirk that restricted day-of-month AND weekday must both match.
• The next five run times are computed from your machine's local time by a bounded minute-scan, so you can confirm the schedule before deploying it.

How it works

1. 1

   Fill the fields or pick a preset

   Type values into the five boxes or start from a preset chip. Each field reports its own validation error inline — nothing crashes, nothing silently passes.

2. 2

   Read the explanation

   The sentence panel translates the expression: “At minute 0, every 2 hours, on Monday through Friday.” Check it says what you meant.

3. 3

   Verify the next runs, then copy

   The next-five list shows real upcoming local timestamps. Copy the expression into crontab, your scheduler UI or CI config.

Tips for better results

• 💡Cron has no timezone field — the schedule runs in the machine's local time. Confirm your server's timezone before blaming the expression.
• 💡When both day-of-month and weekday are restricted (not *), cron fires only on days matching BOTH — a classic surprise this tool's explanation calls out.
• 💡Use */15 instead of 0,15,30,45 — same schedule, and readers understand the intent at a glance.

Frequently asked questions