Cron Calendar
Explain cron expressions and preview the next run times in any timezone.
OpenClick a common schedule and copy its cron expression without looking up the syntax.
Each preset shows its label and expression side by side.
The expression drops into the output box.
Use the Copy button to grab the expression.
Check which zone your scheduler uses before deploying.
Most scheduled jobs use one of a handful of cadences: every few minutes, hourly, nightly, weekday mornings. Typing those from memory invites small mistakes like swapping the minute and hour. Cron Presets keeps the usual ones a click away.
Seven presets are listed with their expressions next to the label: every minute (* * * * *), every 5 minutes (*/5 * * * *), hourly at minute 0, daily at 09:00, weekdays at 09:00 (0 9 * * 1-5), weekly on Sunday at midnight, and monthly on the 1st at midnight. Click one and it appears in the output box, ready for the Copy button.
The times carry no timezone. Crontab follows the server's local zone, Kubernetes CronJobs default to UTC unless timeZone is set, and GitHub Actions always uses UTC, so 09:00 can mean very different moments. It also pays to offset busy times: dozens of jobs all set to minute 0 compete for the same resources, so 7 9 * * * is often kinder than 0 9 * * *. To change a preset field by field, open it in the cron field editor, and to see exactly when it runs around a daylight-saving change, preview the next runs by timezone. For CI pipelines, the GitHub Actions workflow builder is a natural next stop.
The preset list is built into the page, and clicking one only places text in the output box on your machine.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Classic cron's smallest unit is one minute. To run something every few seconds, use a long-running worker with its own timer or a scheduler that supports a seconds field.
Yes. */5 fires at minutes 0, 5, 10 and so on of every hour, not five minutes after the job was installed.
Standard five-field cron cannot express that. Common workarounds are scheduling on days 28 to 31 and checking in the script whether tomorrow is the 1st, or using a scheduler that supports the L extension.