Cron
Paste a 5-field cron expression. See parsed fields and the next runs (interpreted in UTC).
Parsed fields
- Minute
- 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55
- Hour
- every
- Day of month
- every
- Month
- every
- Day of week
- every
Next runsUTC
| # | UTC | Local | From now |
|---|---|---|---|
| Loading… | |||
Notes
- Standard 5-field cron: minute hour day-of-month month day-of-week.
- Supports *, ,, -, /, month/weekday names (jan, mon, …), and shortcuts (@hourly, @daily, @weekly, @monthly, @yearly).
- Both 0 and 7 mean Sunday in day-of-week.
- If day-of-month and day-of-week are both restricted, the schedule fires when either matches (standard Vixie cron OR semantics).
- Expressions are interpreted in UTC. The Local column converts each run to your browser timezone for convenience.
The five-field cron expression
A classic cron expression has five space-separated fields: minute hour day-of-month month day-of-week. Each field accepts a single value, a comma-separated list, a range (1-5), a step (*/15), or * for "every value". The parser on this page accepts the same syntax Linux cron uses and previews the next handful of times the expression will fire.
Expressions everyone reaches for
0 * * * *— once an hour, on the hour.*/15 * * * *— every fifteen minutes.0 9 * * 1-5— 9:00 a.m. on weekdays.0 0 1 * *— midnight on the first of every month.0 0 * * 0— midnight on Sunday.
Gotchas
- Day-of-month and day-of-week are OR-ed, not AND-ed, in classic cron. If you specify both, the job fires whenever either field matches.
- Time zones vary by host. A bare cron expression is interpreted in the server's local timezone unless the cron implementation supports a per-job
CRON_TZ. Cloud schedulers (AWS EventBridge, GCP Cloud Scheduler) usually run in UTC; check before you migrate. - Step values are relative to the start of the range.
*/5on the minute field fires at:00,:05,:10, …, not every five minutes from when the job was created.