*/5 * * * *Every 5 minutes
Match any value (*)
Match any value (*)
Match any value (*)
Match any value (*)
Next 6 runs
- 1.5/11/2026, 6:10:00 PM
- 2.5/11/2026, 6:15:00 PM
- 3.5/11/2026, 6:20:00 PM
- 4.5/11/2026, 6:25:00 PM
- 5.5/11/2026, 6:30:00 PM
- 6.5/11/2026, 6:35:00 PM
About Cron Expression Generator
Cron Expression Generator builds a cron expression visually, one field at a time. Pick minute, hour, day-of-month, month, and day-of-week values from dropdowns and toggles; preview the resulting expression and the next ten run times update live. Common patterns are pre-set as one-click templates (every minute, every hour at :00, weekday mornings, midnight UTC, first of the month).
Reach for it whenever you are authoring a schedule and the raw `0 */15 9-17 * 1-5` is harder than picking from a UI: setting up a Kubernetes CronJob, a GitHub Actions schedule, a Vercel cron, a backup job, or a digest email. Cron Expression Parser is the inverse — paste an existing expression and read it in plain English. The two tools round-trip cleanly.
Examples
minute: every 15
hour: 9-17
weekday: Mon-Fri*/15 9-17 * * 1-5
Next runs (UTC):
2026-05-05 14:15
2026-05-05 14:30
2026-05-05 14:45Visual selections produce the standard five-field expression. Add a leading seconds field for Quartz-style schedulers.
Frequently asked questions
Which scheduler will this work with?
Standard Unix cron, the cron-like schedulers in Kubernetes (CronJob), GitHub Actions (`schedule.cron`), Vercel, AWS EventBridge cron expressions, and most CI systems. Quartz / Spring need the six-field variant — toggle the seconds field on for those.
How is this different from Cron Expression Parser?
Generator builds new expressions from a UI; Parser reads existing expressions and explains them. Use Generator to author; use Parser to debug or document. Anything you produce here can be pasted into Parser to confirm the schedule.
What timezone are the previewed run times in?
UTC by default. Toggle to your local timezone for a sanity check, but remember that cron itself is timezone-naive — the actual run time depends on the scheduler's configured timezone. AWS EventBridge runs in UTC; Vercel runs in UTC; Kubernetes uses the cluster's timezone; GitHub Actions runs in UTC.
Can I generate every-N-minutes that does not divide 60?
Sort of. Cron's `*/N` fires when the field value is divisible by N — `*/7` does not give every 7 minutes, it gives 0, 7, 14, 21, 28, 35, 42, 49, 56, 0 (resets each hour). For true every-N-seconds intervals, use a job runner with native interval support rather than cron.