Time to Cron Converter: Schedule Jobs from Human Time
5/28/20262 min readBy RM
cronschedulingdevopssretime
Writing cron by hand is easy to get wrong. If you know the schedule you want (say, every weekday at 9:30), generate the cron expression and validate it before it hits production.
Use the Time to Cron Converter to build the cron string from plain inputs.
Quick steps
- Pick the time and interval you want (hour, minute, day of week, etc.).
- Select the days or range that match your job.
- Copy the generated cron expression.
- Paste it into Cron to Time and confirm the next run times.
Example schedules
| Plain English | Cron expression |
|---|---|
| Every weekday at 09:30 | 30 9 * * 1-5 |
| Every day at midnight | 0 0 * * * |
| Every 15 minutes | */15 * * * * |
| Every Monday at 02:00 | 0 2 * * 1 |
Cron uses 24-hour time: 9 PM is 21, not 9.
Where this shows up
- Linux crontab: paste the expression into
crontab -e. - GitHub Actions:
on.schedule.cron(runs in UTC). - Kubernetes CronJob:
spec.schedulein your manifest YAML.
Always confirm the timezone of the scheduler. Your laptop time is not necessarily the server time. Use the Timezone Converter when comparing UTC to local time.
For a full field-by-field explanation, see Cron Expressions Explained.
Common mistakes
- Forgetting 24-hour time.
9in the hour field means 09:00, not 21:00. - Mixing day-of-month with day-of-week. Combining both can narrow the schedule in unexpected ways.
- Skipping validation. Always loop generated cron through Cron to Time before deploy.
Verification checklist
- Paste the generated cron into Cron to Time and read the plain-English summary.
- Compare the next 5 run times with your expected schedule.
- Confirm the timezone on your server or workflow runner.