Cron Expression Parser
Paste a crontab line or type an expression and see straight away what it means in plain English, which values each of the five fields matches, and the next 10 times it will run. Start from a preset if you're writing a new schedule.
EXPRESSION
PRESETS
FIELDS
- Minute 0–59
- 0 0
- Hour 0–23
- 9 9
- Day of month 1–31
- * every day
- Month 1–12, JAN–DEC
- * every month
- Day of week 0–6 (or 7), SUN–SAT
- 1-5 Monday, Tuesday, Wednesday, Thursday, Friday
MEANING AND NEXT RUNS
At 09:00, Monday through Friday
NEXT 10 RUNS
Working out the run times…
Special characters
* matches every value of the field. A comma makes a list, as in 1,15 for the 1st and the 15th. A dash makes a range, as in 1-5 for Monday to Friday. A slash adds a step: */15 is every 15th value from the start, and 10-50/20 is 10, 30 and 50. Month and weekday names, such as JAN or MON-FRI, work in any mix of upper and lower case.
Macros
Instead of five fields you can write a macro. @hourly is 0 * * * *, @daily (or @midnight) is 0 0 * * *, @weekly is 0 0 * * 0, @monthly is 0 0 1 * * and @yearly (or @annually) is 0 0 1 1 *. @reboot runs once when the machine starts, so it has no schedule to show.
Common mistakes
A job that should run once a day but runs every minute of that hour usually has a * in the minute field: * 3 * * * runs 60 times, from 03:00 to 03:59, while 0 3 * * * runs once. Hours go up to 23, so midnight is 0, not 24. And remember that cron uses the server's clock, which is often UTC, not your local time.
How to read a cron expression
- 1
Enter the expression
Type or paste the five fields, such as 0 9 * * 1-5, or a macro like @daily. Or tap one of the presets to start from a common schedule and change it from there.
- 2
Check the meaning and the fields
The sentence on top says when the job runs. Below it every field is listed with the values it matches. If a field is wrong, it's marked red with the reason, such as an hour of 24.
- 3
Look at the next runs
The next 10 run times are listed in your own time zone. Switch to UTC to see them as most servers run cron, then copy the expression into your crontab.
Frequently asked questions
What do the five fields of a cron expression mean?
From left to right they are the minute (0–59), the hour (0–23), the day of the month (1–31), the month (1–12 or JAN–DEC) and the day of the week (0–6 or SUN–SAT, where 0 and 7 are both Sunday). A * means every value, so 30 2 * * * runs at 02:30 every day.
How do I run a job every 5 minutes?
Use */5 * * * *. The /5 is a step, so the minute field matches 0, 5, 10 and so on up to 55. Steps work in any field and on ranges too, so 0 8-18/2 * * * runs every two hours from 08:00 to 18:00.
What happens when both the day of month and the day of week are set?
Then the job runs on days that match either one, not both. 0 0 1 * 1 runs on the first of every month and also on every Monday. This is how standard cron has always worked, and it surprises many people. If one of the two fields is *, only the other counts.
Which time zone does cron use?
The time zone of the machine or service that runs it. Many servers and cloud schedulers use UTC, so the parser can show the run times in UTC as well as in your own zone. On days when the clocks change, a time that's skipped doesn't run here and a time that happens twice is listed once; real cron daemons differ in how they handle this.
Does this support seconds, years or Quartz syntax?
No. It reads the standard five-field cron used by crontab, Vixie cron, cronie, Kubernetes CronJobs and GitHub Actions, plus the macros @yearly, @monthly, @weekly, @daily and @hourly. Quartz and Spring add a seconds field and symbols like L, W,