Cron Dialect Converter

Paste a normal five-field cron expression and see it rewritten for Quartz, Spring, AWS EventBridge, GitHub Actions and Kubernetes CronJob, side by side.

Use the tool

Why this tool exists

Cron is not one language. The Unix schedule you test on a server needs a leading seconds field in Quartz and Spring, a trailing year and a question mark in AWS EventBridge, and Kubernetes adds its own timeZone key. Moving a job between systems usually means a round of trial, error and a failed deploy.

This converter takes the classic five-field form (or macros like @daily) and prints each dialect. It also warns when day-of-month and day-of-week are both set, because standard cron ORs them while Quartz and EventBridge cannot. Everything runs in your browser.

How to use it

  1. Enter a five-field cron such as 30 2 * * 1-5, or a macro like @daily.
  2. Set the time zone to write into the Kubernetes CronJob block.
  3. Copy the dialect you need from the output.

Frequently asked questions

Does it accept six-field or Quartz input?

No. It expects exactly five fields (minute, hour, day of month, month, day of week) or a macro such as @hourly. Anything else returns an error naming what it expected.

Why was my day-of-week dropped?

Standard cron runs when either day-of-month or day-of-week matches. Quartz and EventBridge require one of them to be a question mark, so the tool keeps the day-of-month and adds a note. Split the job into two schedules if you need both.

Is the GitHub Actions cron in my time zone?

No. GitHub Actions schedules run in UTC only, so the tool writes the expression unchanged. Convert your local time to UTC first. The time zone field affects only the Kubernetes CronJob output.

Does it check that the numbers are valid?

Only the characters and field count are checked. Out-of-range values such as minute 99 are not rejected, so confirm the schedule with a cron explainer before you deploy it.