Cron Expression Builder
Switch between Builder and Parser modes. Builder lets you compose a cron expression field-by-field and shows the next 5 scheduled runs. Parser takes any cron string and explains it in plain English.
Used 6,100 times
* * * * *
Runs every minute.
Next 5 Scheduled Runs
- 1Sun, Nov 15, 2026, 06:17 AM
- 2Sun, Nov 15, 2026, 06:18 AM
- 3Sun, Nov 15, 2026, 06:19 AM
- 4Sun, Nov 15, 2026, 06:20 AM
- 5Sun, Nov 15, 2026, 06:21 AM
Latest DevOps articles
Cron Daylight Savings Fixer – Prevent Duplicate and Missing Job Runs
Learn why cron jobs can run late, twice or not at all around DST changes, how cronie and EventBridge Scheduler handle it, and how UTC schedules avoid it.
Migrating Cron Schedules to Databricks (Quartz) and EventBridge Without Surprises
A field-by-field checklist for moving Unix crontab schedules to Databricks (Quartz) and AWS EventBridge: seconds, ?, Sunday numbering, the OR rule, L/W/#, years, rate() and timezones.
GitHub Actions Linter — Catch Broken Workflows Before They Break CI
Paste any workflow YAML and get instant feedback on triggers, jobs, runs-on labels, unsafe secrets usage, and deprecated actions before shipping to main.
What is a Cron Expression?
A cron expression is a string of five fields — minute, hour, day-of-month, month, day-of-week — that define a recurring schedule for Unix cron, GitHub Actions, Kubernetes CronJobs, AWS EventBridge, and most CI/CD systems. Each field accepts a specific value, a wildcard (*), a range (1-5), a list (1,3,5), or a step (*/15).
How to Use
- Builder mode — Set each field using Every / Specific / Range / Step / List controls. A live cron string and explanation update as you type.
- Parser mode — Paste any existing cron expression to get a plain-English description and the next 5 scheduled run times.
- Use presets (e.g. Every hour, Every weekday at 9 AM) as a starting point.
Common Cron Mistakes
- Wrong field count — Standard cron has 5 fields. Some systems (AWS, GitHub Actions) add a 6th seconds field at the front — check your platform's docs.
- Day-of-month + day-of-week interaction — When both are non-
*, most cron implementations use OR logic (runs if either matches). - Timezone confusion — Cron runs in the server's local timezone by default. For UTC-pinned schedules, set
TZ=UTCor use your platform's timezone setting.
Quartz, Databricks and EventBridge Cron
This builder writes standard 5-field Unix cron. Quartz (used by Databricks jobs) and AWS EventBridge use different formats: a seconds or year field, ? in one day field, and Sunday = 1 instead of 0. A Unix expression pasted into either one is rejected or runs on the wrong days.
- Quartz Cron Generator — validate and explain Quartz expressions, including L, W and #.
- EventBridge Cron Expression Validator — check cron() and rate() expressions with next runs in UTC.
- Cron Converter — convert between Unix, Quartz and EventBridge with a warning for every rule that changes.
FAQs
What does */15 * * * * mean?
Run every 15 minutes: at :00, :15, :30, and :45 of every hour, every day. The step syntax */n means "every n units".
How do I schedule something every weekday at 9 AM?
0 9 * * 1-5 — minute 0, hour 9, any day-of-month, any month, Monday through Friday (1–5).
Is Sunday 0 or 7?
Both. Most implementations accept 0 and 7 as Sunday in the day-of-week field. Monday is always 1.