What is Cron Builder?

Cron is a time-based job scheduler built into Unix and Linux systems. A cron expression is a compact string — like 0 9 * * 1 — that tells the system exactly when to run a task: which minute, hour, day of month, month, and day of week. The syntax is powerful but unintuitive, and a single misplaced value can mean a job runs at the wrong time or not at all.

The Cron Builder lets you construct valid cron expressions visually. Instead of memorizing field positions and special characters, you set your schedule using dropdowns and selectors, and the tool generates the expression in real time — along with a plain-English description of exactly when it will run.

---

How to Use Cron Builder

1. Choose a preset or build from scratch. Common schedules (every hour, every day at midnight, every weekday) are available as one-click presets. Switch to custom mode for full control over each field.
2. Set your time fields. Configure the minute, hour, day of month, month, and day of week independently. Each field supports specific values, ranges, steps (*/5), and wildcards (*).
3. Read the natural language translation. As you adjust the fields, the tool shows a human-readable description of the schedule — confirming your expression means what you intend.
4. Copy the expression. Click to copy the final cron string, ready to paste into a crontab, GitHub Actions workflow, CI/CD config, or any system that accepts cron syntax.

---

Cron Expression Format

A standard cron expression has five fields separated by spaces:

┌─────────── minute (0–59)
│ ┌───────── hour (0–23)
│ │ ┌─────── day of month (1–31)
│ │ │ ┌───── month (1–12)
│ │ │ │ ┌─── day of week (0–6, Sunday = 0)
│ │ │ │ │
* * * * *

Special characters:

• * — every value (any minute, any hour, etc.)
• , — list of values: 1,15 means the 1st and 15th
• - — range: 9-17 means 9 through 17
• / — step: */15 means every 15 units

Some systems (AWS, GitHub Actions, Quartz) support a sixth field for seconds. The tool notes where extended syntax is needed.

---

Common Use Cases

Scheduled backups — run a database backup script every night at 2 AM: 0 2 * * *

Recurring reports — generate and email a weekly report every Monday morning: 0 8 * * 1

Cache clearing — purge application caches every hour: 0 * * * *

CI/CD pipelines — trigger nightly builds or dependency update checks automatically

Server maintenance — run log rotation, certificate renewal (certbot), or cleanup scripts on a fixed schedule

Learning cron syntax — experiment with expressions and immediately see what schedule they produce

---

Privacy

All cron expression generation and validation happens in your browser. No input is sent to any server or stored between sessions.