How it works
- 1
Paste or type a cron expression
Enter any 5-field cron expression or pick from common schedule presets like 'Every Monday at 9am' or 'Daily midnight'.
- 2
Get a plain-English explanation
See immediately what the schedule means in human terms, with the next 10 scheduled execution times shown in your local timezone.
- 3
Copy the platform snippet
Pick your deployment target — GitHub Actions, Kubernetes CronJob, AWS EventBridge, or systemd timer — and copy the ready-to-paste snippet.
Field breakdown
0
MIN
9
HOUR
*
DOM
*
MON
1
DOW
Minute (0–59)
Hour (0–23)
Day of Month (1–31)
Month (1–12)
Day of Week (0–7)
Common schedules
🛡️ Verify zero uploads — open DevTools → Network tab
Open your browser's DevTools (F12), go to the Network tab, and use this tool. You will see zero outbound requests — all processing runs inside your browser sandbox via WebAssembly or pure JavaScript. Nothing you paste or upload is ever sent anywhere.
Use cases
Verify a cron before deploying
Understand exactly what a cron schedule does and when it will next run before committing it to a GitHub Actions workflow or Kubernetes manifest.
Convert to AWS EventBridge format
AWS uses a different 6-field format where either DOM or DOW must be '?'. This tool auto-converts your standard cron to the correct AWS syntax.
Audit inherited cron jobs
Paste an unfamiliar cron expression from a legacy system and get an immediate human-readable description of its schedule.
Frequently Asked Questions
What is the cron expression format?
Standard cron uses 5 fields separated by spaces: minute (0–59), hour (0–23), day of month (1–31), month (1–12), and day of week (0–7, where 0 and 7 are both Sunday). Special characters include * (any), , (list), - (range), and / (step).
Why does AWS EventBridge use a different format?
AWS EventBridge cron has 6 fields (minute, hour, day-of-month, month, day-of-week, year) and requires that either day-of-month or day-of-week be set to '?' — you cannot specify both. This tool auto-converts standard 5-field cron to the correct AWS format.
Why does the next run time differ from what I expected?
The next run times are shown in your browser's local timezone. A cron like '0 9 * * *' runs at 9am in whatever timezone the server is configured for — typically UTC for cloud services. The times shown here use your local clock.
What are the common cron special characters?
* means 'every' (any value), / means step (*/5 means every 5 units), - means range (1-5 means values 1 through 5), and , means list (1,3,5 means those specific values). For example '0 9 * * 1-5' means 9am on weekdays Monday through Friday.
Does this tool send my cron expression anywhere?
No. All parsing and conversion runs entirely in your browser using JavaScript libraries. Your cron expressions are never sent to any server.
Want unlimited access + saved history?
Pro is $9/month · 30-day money-back guarantee.