Cron Expression Builder
Build cron expressions, read them in plain language, and see the next runs
- Files never leave your device
- Runs in your browser
- Free, no sign-up, no watermark
Edit the fields below or paste an expression here — they stay in sync.
Minute */15Hour 9-17Day of month *Month *Day of week 1-5
In plain words
…
Minute
0–59Everystarting at
Hour
0–23FromTo
Day of month
1–31Month
1–12Day of week
0–6FromTo
Next 10 runs
Cron runs in the server’s time zone (GitHub Actions always uses UTC).
Crontab line
*/15 9-17 * * 1-5 /usr/local/bin/backup.shHow to use Cron Expression Builder
Build a cron expression field by field or paste one to decode it. The tool explains it in plain words, lists the next 10 run times in any time zone, and supports standard 5-field cron, 6-field cron with seconds, and Quartz.
- 1
Pick a Format: Standard (5 fields), With seconds (6), or Quartz (6–7).
- 2
Start from a preset, or set each field to Every, Specific, Range, Interval, or Custom.
- 3
Or paste an expression into Cron expression; the fields update to match.
- 4
Read In plain words and Next 10 runs, switch the time zone if needed, then copy the expression.
Frequently asked questions
Which cron format does GitHub Actions use?
Standard (5 fields), the same as Linux crontab, Kubernetes CronJob, and Vercel. GitHub Actions always runs schedules in UTC.
What's different about Quartz?
Quartz adds seconds and an optional year, numbers days of the week 1–7 starting on Sunday, and needs ? in either day-of-month or day-of-week.
Does it understand @daily and other macros?
Yes. Macros such as @hourly, @daily, @weekly, @monthly, and @yearly are expanded and explained.
Why are next run times missing for my expression?
The preview engine doesn't support the W (nearest weekday) character. The expression may still be valid on your scheduler.
Can I get a full crontab line?
Yes. In Standard format, type your command under Crontab line and copy the finished line.