Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenBuild cron expressions. - runs entirely in your browser. Free, fast and private.
Select minute, hour, day, month, and weekday.
Use every, specific, or interval syntax per field.
Five-field cron expression assembles automatically.
Paste into crontab, GitHub Actions, or Kubernetes.
You need "every weekday at 9:30" as a five-field cron string and do not want to re-learn the minute/hour/dom/month/dow order from memory. Cron Generator builds the expression from plain controls and shows you the result to copy.
Use it for CI schedules, backup jobs, Kubernetes CronJobs, and queue workers. Remember that cron dialects differ: some platforms add a seconds field or use non-standard day-of-week numbering. Confirm against your runtime docs after you copy.
Pitfall: setting both day-of-month and day-of-week in ways your cron treats as OR vs AND. Keep one field starred unless you know the platform rules.
Next step: paste the expression into Cron Explainer or Cron Calendar to preview upcoming fire times in a timezone you care about.
Schedule building is local UI state. No job is registered on our servers when you generate an expression.
Follow-up: Cron Explainer · Cron Calendar
Processes data instantly with no server round-trips.
Your data never leaves your browser. Nothing is uploaded.
Works in any modern browser. Nothing to download or install.
No limits, no sign-up, no credit card required.
Works on desktop, tablet and mobile devices.
Beautiful in both themes. Your preference is saved.
Keyboard shortcut
Produce cron strings for workers and batch scripts.
Draft expressions before pasting into CI or orchestrators.
Translate a spoken cadence into minute and hour fields.
Answers for this tool. For site-wide help, open the FAQ hub.
Cron Generator build cron expressions. Output stays in your browser for quick iteration.
Prefer redacted samples. Even with local processing, treat prod credentials carefully and rotate anything accidentally shared.
No. Generators and linters produce text for you to copy into Git, CI, or consoles - they do not deploy for you.
Always run official CLIs (kubectl, terraform plan, actionlint, etc.) on the final files after using Cron Generator as a starting point.
Syntax may vary across Kubernetes/Terraform/GitHub Actions versions. Adjust generated snippets to your runtime version.
After the page loads, most authors work offline. Keep a local copy of critical manifests.
Use Sample to learn the format, edit, then Download/Copy into your editor.
Request it via Contact with the platform and version you use.