Every platform says it supports cron, and then each one does it a little differently.
GitHub Actions wants five fields, AWS wants six with a question mark in one of them, and systemd doesn't use cron at all. I got tired of translating between them by hand, so this does it for you.
The Differences That Matter
Timezones. A classic crontab runs in the server's timezone. GitHub Actions runs in UTC unless you add a timezone next to the schedule, Kubernetes has a timeZone field, and Vercel and Cloudflare Workers only run in UTC. The tool adds the timezone where the platform supports one and warns you where it doesn't.
Day of the week numbers. Classic cron counts Sunday as 0. Quartz and AWS count Sunday as 1, so 1 means Monday in one and Sunday in the other. The tool writes days as names (MON, TUE) wherever it can, so there's no way to mix them up.
Both day fields at once. When you set both the day of the month and the day of the week, classic cron runs on either one. AWS and Quartz don't allow that at all, and systemd needs two schedules to do it. The tool handles each of those for you.
How often it can run. GitHub Actions won't run a schedule more often than every five minutes, and Vercel's free plan only runs cron jobs once a day. The tool flags a schedule that's too frequent for the platform.
Frequently Asked Questions
Why is my GitHub Actions schedule late?
GitHub runs scheduled workflows on shared runners, and when they're busy (especially at the top of the hour) a run can start late or get dropped. Picking an odd minute like 17 instead of 0 helps. Also, in public repositories GitHub turns off scheduled workflows after 60 days with no activity in the repo.
Can I convert from AWS or Quartz back to regular cron?
Yes. Pick the format you're starting from, paste the expression, and you'll get the classic five-field version along with all the others.
Does this send my schedule anywhere?
Nope. It all runs in your browser.