Cron Generator
Description: Every minute
Minute
Hour
Day (Month)
Month
Day (Week)
Next 5 Executions
- 2026-07-22 18:47:00
- 2026-07-22 18:48:00
- 2026-07-22 18:49:00
- 2026-07-22 18:50:00
- 2026-07-22 18:51:00
About this tool
A cron expression is five fields — minute, hour, day of month, month, and day of week — that together describe a repeating schedule. This tool lets you build one visually: pick Every, a Specific value, a Range, or an Interval for each field, and it writes the expression for you. You can also paste an existing expression and it is parsed back into the controls.
Alongside the expression it shows a plain-English description of what the schedule means and lists the next five times it will fire, so you can confirm the timing before deploying it. Handy presets cover the most common schedules.
All parsing happens in your browser.
How to use
- Set each field using Every, Specific, Range, or Interval — or start from a preset.
- Read the plain-language description to confirm it means what you intend.
- Check the next five execution times.
- Copy the finished expression into your crontab, CI config, or scheduler.
Common use cases
- Scheduling backups, reports, or cleanup jobs on a server
- Configuring CI/CD pipelines and scheduled workflows
- Setting up recurring tasks such as Kubernetes CronJobs
- Decoding an unfamiliar cron line someone else wrote
Frequently asked questions
What cron format does it use?
The standard five-field format: minute, hour, day of month, month and day of week.
How do I run a job every 15 minutes?
Use */15 in the minute field. The interval option builds this for you and shows the next run times.
What do * and , mean in cron?
* means every value, a comma lists specific values like 1,15, a dash sets a range like 9-17 and a slash sets a step like */5.
Do day-of-month and day-of-week apply together?
In standard cron, when both are set the job runs when either matches, not both. If precise day control matters, set one field and leave the other as *.
What timezone do the next-run times use?
The preview uses your browser's local timezone. The server that actually runs the job may use UTC or its own setting, so verify the timezone where it is deployed.