Build or paste
Minute, hour, day, month, weekday with presets (every 5 minutes, nightly at 02:00, first of month).
Developer
Cron syntax is terse and easy to get wrong by one field. Pick the schedule with dropdowns or type an expression, read it back in plain English, and see the next ten run times in your local timezone and UTC. Output includes a crontab line, a Kubernetes CronJob snippet and a GitHub Actions schedule block.
Loading the tool…
Minute, hour, day, month, weekday with presets (every 5 minutes, nightly at 02:00, first of month).
The expression is described in words and the next runs are listed; a mistake shows immediately.
crontab, systemd OnCalendar, Kubernetes, GitHub Actions.
Server cron runs in the server's timezone (usually UTC on cloud VMs); the tool shows both so 02:00 IST does not become 02:00 UTC by accident.
When both are set, standard cron runs when either matches, which surprises people; the explanation says so.
Six-field expressions with seconds (Quartz, some schedulers) are supported with a toggle.
Standard cron cannot; the tool offers the common workaround (28-31 with a date check) and the systemd form that can.
Recognised and expanded.
No; it only builds the expression.