// admin tools · 19
Cron builder
Build a schedule field by field or paste one in. Read it back in plain English, preview the next runs in any timezone (DST-aware), and copy it as crontab, Kubernetes, GitHub Actions or systemd config.
// runs locally — nothing is uploaded
Heads up — OR rule. Both day-of-month and day-of-week are restricted, so Vixie cron and cronie run when either matches, not both. To require both, keep one field as * and test the other inside the command, e.g. [ "$(date +\%d)" -le 07 ] && …
presets
builder
next runs
deploy it
How it works
What it does
This builder writes and explains cron schedules. Build one field by field, or paste an expression to see it described in plain English. You also get the next 10 or 20 run times in any IANA timezone and ready-to-paste config for crontab, Kubernetes, GitHub Actions, systemd timers, Spring, node-cron and Quartz. Everything runs locally in your browser.
The three dialects
- Unix
- Classic Vixie cron and cronie:
minute hour day-of-month month day-of-week. Kubernetes CronJobs and GitHub Actions use the same five fields. Day-of-week runs 0–7, where 0 and 7 are both Sunday. Supports lists, ranges, steps,JAN/MONnames and the@hourly…@yearlyand@rebootmacros. - Spring / node-cron
- Adds a leading seconds field. Both day fields must match. Spring also supports
L,W,#and?; node-cron doesn't. - Quartz
- Seconds first plus an optional year. Day-of-week runs 1–7 with 1 = Sunday, a common source of off-by-one bugs. Exactly one day field must be
?.
The day-of-month / day-of-week OR rule
In Unix cron, if both day fields are restricted, the job runs when either matches. 0 9 1 * MON fires on the 1st of every month and on every Monday, not only on Mondays that fall on the 1st. If either field starts with * (including */2), both must match. The builder flags the OR case and the systemd output uses two OnCalendar= lines to reproduce it.
Quartz and Spring specials
L— last day of the month;L-3— three days before it.LW— last weekday (Mon–Fri) of the month;15W— weekday nearest the 15th, never crossing into another month.6#3— third Friday in Quartz (5#3in Spring);6L— last Friday.
Timezones and daylight saving
Next runs are calculated against the wall clock of the timezone you pick, using your browser's built-in timezone database. When clocks spring forward, a time such as 02:30 may not exist; the tool leaves it out and warns you. When clocks fall back, a time happens twice and both occurrences are listed. Vixie cron and cronie handle these hours specially for fixed-time jobs, so check how your scheduler behaves before you schedule anything critical between 01:00 and 03:00.
FAQ
Why is my GitHub Actions schedule an hour off?
GitHub always evaluates on.schedule in UTC. The snippet shifts fixed-time schedules to UTC for zones without daylight saving. For zones with it, there is no single UTC expression that is right all year.
How do I run something on the first Monday of the month?
In Quartz, 0 0 9 ? * 2#1. In Unix cron, use 0 9 * * MON and guard the command with [ "$(date +\%d)" -le 07 ] && …. Note the escaped %, which crontab otherwise treats as a newline. Writing 0 9 1-7 * MON runs on days 1–7 or any Monday.
Does Kubernetes support seconds or L/W/#?
No. CronJob schedules use the five standard fields with minute resolution. Use spec.timeZone (stable since 1.27) instead of shifting hours yourself.