DevOps ToolBox is a growing collection of small, browser-based utilities — no backend, nothing sent to a server. Two cron tools are here today: generate a schedule, or convert one between time zones.
Pick values for each field (every / every N / specific) — no cron syntax to memorize. The expression, a plain-English description, and the next run times update live, and you get the correct syntax for Unix, AWS EventBridge, GitHub Actions, Kubernetes, and Quartz. Set a time zone (defaults to your local one) for the CRON_TZ recipe, or hit “Open in Converter” to change zones.
Set Minute = 0, Hour = 9, Day-of-week = Mon–Fri. You get Unix 0 9 * * 1-5, AWS cron(0 9 ? * 2-6 *), and Quartz 0 0 9 ? * 2-6 — the tool handles AWS’s ? rule and 1–7 weekday numbering for you.
Hours 1, 9, 23 on days 1, 7, 9 of the month: set Hour = specific 1, 9, 23 and Day-of-month = specific 1, 7, 9 → 0 1,9,23 1,7,9 * *.
Already have an expression? Paste it — Unix, AWS cron(…), or Quartz — pick a source and target zone, and see the next runs in UTC, the source zone, and the target zone, with DST gaps and overlaps flagged.
0 9 * * 1-5 in America/New_York is 13:00 UTC in summer but 14:00 UTC in winter — so no single UTC line is right all year. The Converter shows each exact time and the fix: CRON_TZ=America/New_York with the original line, which runs at 09:00 New York time on any machine.
Cron has no time zone — it fires on the machine’s local clock. When two zones observe Daylight Saving Time differently, no single static cron line is correct all year; the answer is CRON_TZ=<zone> with your original expression. Both tools surface it automatically.