Why it exists

Cron syntax is short, old and easy to get subtly wrong. 0 9 13 * 5 looks like “Friday the 13th” but runs every Friday and every 13th. A job scheduled at 02:30 silently skips a day when clocks change. GitHub Actions runs in UTC whatever your laptop says. Most mistakes only show up after the job has failed to run, so the point of CronGen is to show you, before you deploy, exactly when a schedule fires.

What the tools do

  • Generator: describe a schedule in plain English or set each field, then copy the expression for crontab, GitHub Actions, Kubernetes, AWS EventBridge, Quartz, systemd or node-cron.
  • Decoder: paste an expression or a whole crontab line and get a plain-English description, the next run times in your time zone, a calendar, and warnings about common traps.
  • Saved: keep schedules, commands and notes together. Everything stays in your browser.

All of it runs in your browser. The plain-English converter is a rule-based parser, not an AI model, so the same sentence always gives the same expression, and the run times come from a real cron engine that follows the same rules as Vixie cron and cronie.

How the articles are written

The blog covers the problems people actually search for: jobs that don't run, missing environment variables, time zones, overlapping runs, and scheduling on specific platforms. Each article aims to answer the question near the top, then explain why, with commands you can copy.

We check commands and behaviour against the documentation of the tools involved (cronie, Debian cron, systemd, Kubernetes, GitHub Actions, AWS, Quartz and others) and update articles when those tools change. Every article shows when it was published and when it was last updated. If you find something wrong or out of date, tell us and we'll fix it.

How the site is funded

CronGen is free and has no accounts or paid tier. It is paid for by ads from Google AdSense, shown only if you accept cookies, and by a small number of clearly marked affiliate links to hosting and monitoring services. Neither decides what we write. See the privacy policy for details.

Get in touch

Bug reports, corrections, ideas for tools or articles: support@crongen.com.