Cron Expression Generator & Translator

How to Use the Cron Expression Generator

1. Choose a Preset or Enter Custom Fields: Click any common schedule (e.g. Every 5 Minutes, Hourly, Daily Midnight) or customize the 5 fields manually.
2. Inspect the Plain English Translation: Watch the real-time description update instantly as you change minutes, hours, or weekdays.
3. Verify Upcoming Execution Times: Review the next 5 scheduled trigger timestamps to ensure your job will fire exactly when intended without timezone surprises.
4. Copy with 1-Click: Click Copy Cron to paste directly into your Linux crontab -e, Kubernetes CronJob manifest, or GitHub Actions YAML file.

Understanding the 5 Cron Fields and Special Characters

Common Cron Pitfalls and Cloud Quirks

• UTC Timezone Assumption: GitHub Actions, Kubernetes nodes, and AWS Lambda EventBridge triggers default to UTC. If you schedule a backup at 0 2 * * *, verify if that is 2 AM UTC or 2 AM in your local timezone using our Unix and epoch timestamp converter.
• AWS EventBridge 6-Field Syntax: AWS requires a 6th field for Year (e.g., 0 9 ? * MON-FRI *) and mandates a question mark (?) in either Day of Month or Day of Week.
• Step Values: Writing */15 * * * * executes every 15 minutes. Writing 15 * * * * only executes once per hour at minute 15.