Runs locally in your browser. Nothing you enter is uploaded to our servers.
at minute 0 of every hour
Tips for cron expressions
Confirm which cron dialect your scheduler uses (Linux, Quartz, etc.).
Test in the target timezone — cron is easy to misread.
Prefer explicit ranges over overly clever step values.
Document the intended human schedule next to the expression.
Avoid overlapping jobs that pile up if a run is slow.
Cron expressions you can read back
Processing stays in your browser — your input is not uploaded to our servers.
A cron string is five (or six) fields that say when a job runs. This helper builds or explains that string so you do not ship `* * * * *` by accident.
Flavors differ (Linux crontab vs Quartz vs Kubernetes). Confirm the dialect of the runner.
Build a cron expression
Describe the schedule in fields
Minute, hour, day of month, month, day of week — in that order for classic cron.
Read the explanation
If the English summary is not what you meant, the fields are wrong.
Paste into the runner
Set the timezone the worker actually uses. UTC vs local is a common outage.
Cron generator FAQ
Does this create a job on a server?
No. It only builds the expression. You still install it in crontab, CI, or k8s.
Five fields or six?
Classic Unix cron is five. Some systems add seconds. Match the docs of the scheduler.
Local only?
Yes. Nothing is scheduled on our side.