Cron Generator
Trending 🔥Build and explain cron expressions
How to Use Cron Generator
- 1Build the schedule using the visual controls
- 2See the cron expression update in real time
- 3Read the human-readable explanation
- 4Copy the cron expression
About Cron Generator
Cron Expression Generator provides a visual interface for building cron expressions without memorizing the field syntax. Set the schedule using controls for minute, hour, day-of-month, month, and day-of-week, and the tool generates the correct cron expression along with a human-readable explanation.
Cron is the standard scheduling mechanism in Linux/Unix systems, CI/CD pipelines, cloud functions, and serverless platforms. The five-field cron syntax is powerful but cryptic — '0 9 * * 1-5' is not immediately readable.
The tool is compatible with standard Unix crontab, GitHub Actions, AWS EventBridge, Kubernetes CronJobs, and most other cron-compatible schedulers.
Key Features of Cron Generator
- Visual cron expression builder with controls for each field
- Generates standard 5-field cron expressions (minute hour dom month dow)
- Human-readable explanation of the generated schedule
- Shows the next 5–10 scheduled run times based on current time
- Includes common presets (hourly, daily, weekly, monthly)
- Compatible with Unix crontab, GitHub Actions, AWS EventBridge, and Kubernetes
- Works entirely in-browser — no server required
- One-click copy of the generated expression
Examples
Schedule a daily backup at 2 AM
Create a cron expression to run a backup script every day at 2:00 AM.
Input
Minute: 0, Hour: 2, Day: *, Month: *, Weekday: *
Output
Cron: 0 2 * * * — Explanation: Every day at 02:00
Run a job every weekday at 9 AM
Schedule a morning report to run on Monday through Friday at 9 AM.
Input
Minute: 0, Hour: 9, Day: *, Month: *, Weekday: 1-5
Output
Cron: 0 9 * * 1-5 — Explanation: At 09:00 on Monday through Friday
Common Use Cases
- Scheduling database backup scripts via crontab on Linux servers
- Setting up GitHub Actions workflow schedules using cron syntax
- Configuring AWS EventBridge or Lambda scheduled triggers
- Creating Kubernetes CronJob specifications for recurring tasks
- Scheduling data import/export jobs in ETL pipelines
- Setting up health check or monitoring pings at regular intervals
Troubleshooting
Cron job runs at unexpected times
Solution
Cron expressions use the system timezone of the server or cloud provider's default. AWS EventBridge uses UTC. Check and account for timezone differences.
Using both day-of-month and day-of-week causes unexpected behavior
Solution
When both fields are set, most cron implementations run the job when either condition is met (OR logic). Use * for one of the fields if you want only the other to apply.
Expression with */5 runs at unexpected minutes
Solution
*/5 means every 5 minutes starting from 0: 0, 5, 10, 15... If you need a different offset, use a comma-separated list.
Frequently Asked Questions
What cron format is used?
Standard 5-field Unix cron format: minute (0–59), hour (0–23), day-of-month (1–31), month (1–12), day-of-week (0–7). Compatible with crontab, GitHub Actions, AWS EventBridge.
What does * mean in a cron field?
* means every valid value for that field. For example, * in the hour field means every hour.
What does */ mean in a cron expression?
*/n is step syntax meaning every n units. For example, */15 in the minute field means every 15 minutes (0, 15, 30, 45).
How do I run a cron job every 5 minutes?
Use */5 in the minute field: */5 * * * *. This runs at 0:00, 0:05, 0:10, etc.
Does cron support seconds?
Standard Unix crontab does not support seconds — the minimum interval is 1 minute. Some platforms use a 6-field format with seconds.
What timezone does cron use?
Standard crontab uses the local system timezone. Cloud schedulers like AWS EventBridge default to UTC.
Is my data sent to a server?
No. All cron expression generation and validation is performed locally in your browser.
Can I use this for GitHub Actions?
Yes. GitHub Actions uses the standard 5-field cron syntax. Note that GitHub Actions scheduled workflows run in UTC timezone.