Cron Generator

A cron generator creates a compact cron expression from a schedule such as every five minutes, weekdays at 09:00, or the first day of each month. ToolsSonic combines guided presets with editable fields so you can see both the human schedule and the exact expression that a scheduler will receive.

Choose a cron dialect, select a frequency preset, adjust the generated fields, choose a preview timezone, and select Generate expression. The page validates the fields, explains the schedule in plain English, and shows upcoming run times calculated locally in the browser.

Unix or POSIX cron normally uses minute, hour, day of month, month, and day of week in that order. The usual ranges are minute 0–59, hour 0–23, day of month 1–31, month 1–12, and day of week 0–7 or SUN–SAT depending on the implementation.

Choose the Every N minutes preset, enter 5, and generate the expression. In standard five-field cron the result is `*/5 * * * *`, which matches minute 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 of every hour.

Use the Weekdays at 09:00 quick start or choose the corresponding guided preset. Standard Unix output is `0 9 * * 1-5`; the builder explains that the job runs at minute 0 of hour 9 on Monday through Friday.

Yes. The builder includes daily, weekly, monthly, and yearly patterns as quick starts and supports direct field editing. Select the day, month, and time values required by your scheduler, then review the generated expression and upcoming dates.

An asterisk allows every value, a comma creates a list such as `1,15`, a hyphen creates an inclusive range such as `9-17`, and a slash creates a step such as `*/15` or `1-30/5`. The generated field table shows the selected value and its expanded meaning.

Yes. Supported parser modes accept common names such as JAN through DEC and SUN through SAT where the target scheduler supports them. Numeric values are often more portable; confirm the accepted names and Sunday numbering in the platform that will run the job.

Yes. Select Seconds prefix mode. The output order becomes second, minute, hour, day of month, month, and day of week. This mode is useful for libraries or schedulers that require seconds, but it is not interchangeable with ordinary five-field Unix crontab syntax.

Yes. Select Quartz mode to generate six-field expressions with seconds and optional seven-field expressions that include a year. Quartz also uses `?` for no specific day-of-month or day-of-week value, so use Quartz mode only when the target application expects Quartz-style syntax.

A generator starts with a human scheduling goal and produces an expression. A parser starts with an existing expression and explains or validates it. ToolsSonic links both workflows so you can generate a schedule, inspect the result, and then parse or review the final expression before deployment.

Yes. Choose browser local time, UTC, or a named timezone and select 5, 10, or 20 upcoming runs. The preview shows the selected-zone time, a UTC equivalent, and a relative label. It is calculated from the current browser clock without sending the expression to a server.

The preview formats dates using the selected browser timezone, but the exact behavior of skipped or repeated wall-clock times is controlled by the scheduler and its timezone database. Treat the preview as a local inspection aid and verify DST behavior in the target platform.

The workspace exposes a DOM/DOW policy selector. Standard POSIX cron commonly treats two restricted day fields as an OR condition, while other schedulers may require both or use `?` to mark one field as unspecified. The generated report keeps this boundary visible instead of implying one universal rule.

Yes. Copy expression places the raw expression on the clipboard. Copy report includes the dialect, timezone, readable summary, field breakdown, warnings, and upcoming runs. Download report saves that information as a local plain-text file.

The tool is designed as a free browser utility with no account required. Field generation, parsing, validation, schedule explanation, next-run preview, copying, and report generation run locally. The expression is not uploaded or stored in persistent browser storage.

Cron dialects differ in field order, seconds support, weekday numbering, day-of-month/day-of-week rules, shortcuts, timezone handling, and special operators. Choose the dialect that matches the scheduler and compare the resulting explanation and next runs instead of assuming every five-field string is portable.

No. A generator creates and reviews schedule syntax, but it cannot verify the command, permissions, environment variables, working directory, worker availability, retries, overlaps, monitoring, or scheduler outages. Test the expression and command in the platform where the job will run.

Five-field Unix-style expressions are common in Linux crontab and many cloud or CI tools, while Kubernetes CronJobs, GitHub Actions, AWS, Azure, and Quartz can apply different field, timezone, and syntax rules. Always compare the generated dialect with the destination documentation before copying it into production.

The generator uses practical frequency presets rather than shortcut strings. If your target scheduler accepts @daily, @hourly, or similar shortcuts, type the shortcut directly into the expression field after generating, then verify it in the Cron Parser or in the platform itself. The Cron Parser tool supports @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly shortcuts for validation and preview.