Every 5 minutes
Input
*/5 * * * *
Output
Runs every 5 minutes
Cron Descriptor (Human-Readable Timing)
Convert cron expressions into plain-language timing and calculate upcoming runs.
Supports 5/6/7-field formats, timezone selection, and copy-ready output.
How to use
- Enter a cron expression or choose an example chip.
- Confirm format (5/6/7 fields) and timezone.
- Check description and next N runs, then copy/share.
Sample
Weekdays at 09:00
Input
0 9 * * 1-5
Output
Runs at 09:00 on weekdays (Mon-Fri)
With seconds (daily at 02:30:00)
Input
0 30 2 * * *
Output
Runs daily at 02:30:00
Common Cron Examples
Every 10 minutes
*/10 * * * *
Common pattern for recurring checks and polling jobs.
At minute 0 every hour
0 * * * *
Use when you want an hourly trigger at exact hour boundary.
Weekdays at 09:00
0 9 * * 1-5
Typical business-day schedule.
Every Sunday 00:00
0 0 * * 0
Typical weekly maintenance window.
First day monthly 00:00
0 0 1 * *
Common monthly batch schedule.
Every Jan 1st 00:00
0 0 1 1 *
Useful for annual rollover tasks.
Supported Syntax and Notes
- Supported standard syntax includes `*`, `/`, `-`, `,`, ranges, and step values.
- Implementation-dependent tokens (`L`, `W`, `#`, `?`) may not be interpreted consistently.
- Displayed run times may differ from actual runtime behavior due to timezone and DST differences.
FAQ
Should I use 5 or 6 fields?
Start with 5 fields (minute hour day month weekday). If your expression includes seconds, switch to 6 fields.
Does it support every cron syntax?
It supports standard syntax (`*`, `/`, `-`, `,`). For implementation-dependent tokens like `L`, `W`, `#`, `?`, it shows a warning.
Can it show next run times?
Yes. It calculates and displays the next N runs (5/10/20) with timezone support.