Cron Expression Translator

The same schedule intent, spelled differently across schedulers — with explicit warnings whenever a feature has no equivalent in the target dialect, instead of a silently wrong conversion.

Not sure what a cron expression means? Get a plain-English description and the next 5 run times — the Cron Expression Explainer.

Dialect translators

• Unix cron Quartz cron Paste a Unix cron expression to get the equivalent Quartz cron trigger expression — seconds and year fields added, day-of-week renumbered, and the day-of-month/day-of-week "?" rule applied automatically.
• Quartz cron Unix cron Paste a Quartz cron trigger expression to get the equivalent Unix cron expression — with explicit warnings whenever seconds-level precision or a year restriction can't survive the conversion.
• Unix cron AWS EventBridge cron Paste a Unix cron expression to get the equivalent AWS EventBridge Scheduler cron expression — a year field appended, day-of-week renumbered, and exactly one of day-of-month/day-of-week set to "?" as EventBridge requires.
• AWS EventBridge cron Unix cron Paste an AWS EventBridge Scheduler cron expression to get the equivalent Unix cron expression, with a clear warning if a specific year in the source can't survive the conversion.

Compatibility checks

These platforms use the same 5-field syntax as Unix cron — the page checks for platform-specific behavior (time zone, delivery guarantees), not field translation.

• Unix cron GitHub Actions schedule GitHub Actions' `schedule` trigger uses the same 5-field cron syntax as Unix cron — this checker highlights the platform-specific caveats that a field-for-field identical expression can still hide.
• Unix cron Kubernetes CronJob schedule Kubernetes' `.spec.schedule` field uses the same 5-field cron syntax as Unix cron — this checker highlights the controller-specific behavior that a field-for-field identical expression can still hide.