09 / DevOps / cron-tester
Cron Expression Tester
Explain cron expressions and preview next and previous runs.
How to use
- 01Paste an existing five-field cron expression (minute hour day month weekday) into the Cron expression field, or click a preset such as Every 5 minutes, Weekdays 09:00 or Monthly.
- 02Check the Valid badge and the plain-English description. If the expression is malformed, an error names the field that failed and its allowed range.
- 03Review the field breakdown, which shows which part of the expression landed in Minute, Hour, Day, Month and Weekday.
- 04Read Next executions (local time) for the next 10 scheduled runs and Previous executions for the 5 most recent ones.
- 05Adjust the expression until the run times match what you expect, then press Copy expression.
What is this tool?
The Cron Expression Tester checks a cron line you already have and shows when it will actually fire. It validates the expression, describes it in plain English, and lists the next 10 and previous 5 run times calculated in your browser's local time zone. Seeing concrete dates is the fastest way to catch a schedule that looks right but runs at the wrong hour or on the wrong days. Everything is computed locally in your browser.
Cron expression syntax supported by the tester
The tester reads the standard five-field crontab format: minute (0-59), hour (0-23), day of month (1-31), month (1-12) and day of week (0-6, where 0 is Sunday and 7 is also accepted as Sunday). Each field accepts * for every value, a single number, a range such as 9-17, a comma-separated list such as 1,15, and a step such as */15 or 0-30/10. Month names JAN-DEC and weekday names SUN-SAT are accepted in any letter case, so 0 9 * * MON-FRI is equivalent to 0 9 * * 1-5.
It does not accept a sixth seconds field, a year field, @daily-style macros, or the Quartz extensions ?, L, W and #. Any expression that does not have exactly five fields is rejected with an error, which makes the tester useful for spotting expressions copied from Quartz or Spring that a classic crontab would refuse.
Common cron mistakes: day-of-month vs day-of-week
When both the day-of-month and day-of-week fields are restricted, cron runs the job if either one matches, not only when both match. For example, 0 0 13 * 5 fires at midnight on the 13th of every month and also every Friday, not only on Friday the 13th. The tester follows this rule, so the run list makes the surprise obvious. If either of those two fields is *, only the other one constrains the day.
Another frequent error is assuming */5 in the hour field means every five minutes, or writing 0 */2 * * * and expecting runs at odd hours; the step always counts from the start of the range, so */2 gives 00:00, 02:00, 04:00 and so on.
Why preview run times instead of reading the expression
A description like At every 15 minutes, past hour 9-17, on weekday Monday-Friday is accurate but easy to misread. A list of dates shows exactly when the job fires: with the default expression */15 9-17 * * 1-5 the last weekday run is 17:45, not 17:00, because the hour range includes all of hour 17.
Run times are shown in your browser's local time zone. Most servers and CI schedulers evaluate cron in UTC or the host time zone, so if your machine is in a different zone, shift the times accordingly before concluding a schedule is wrong.
Common use cases
- Confirming when a crontab entry on a server or in a Kubernetes CronJob will next run
- Checking that a weekday business-hours schedule stops at the hour you expect
- Debugging a job that ran on an unexpected day because both day fields were set
- Reviewing a cron line in a pull request by looking at concrete run dates
- Verifying that a monthly or yearly schedule lands on the intended date
FAQ
What does */5 * * * * mean?
It runs every five minutes: at minute 0, 5, 10 and so on of every hour, every day.
What time zone are the next run times shown in?
Your browser's local time zone. Your server or scheduler may use UTC, so convert before comparing.
Can I use MON-FRI or JAN instead of numbers?
Yes. Weekday names SUN-SAT and month names JAN-DEC are accepted in any letter case and can be used in ranges and lists.
Does the tester support seconds or @daily?
No. It accepts only the classic five-field format, so six-field expressions and @-macros are reported as invalid. Use 0 0 * * * in place of @daily.
Why does my job run on more days than expected?
If both day of month and day of week are restricted, cron runs when either matches. Set one of them to * to restrict days by a single rule.
How is this different from the Cron Generator?
The Cron Generator helps you build an expression field by field. The tester takes an expression you already have and shows its next and previous run times.