Cron Expression Explainer

Paste any cron expression to see what it means in plain English and exactly when it will run next — in your own time zone, DST included.

About this tool

A cron expression is a compact schedule written as five fields — minute, hour, day of month, month, and day of week. Reading one is easy right up until it is not: is 0 0 1 * 0 the first of the month, a Sunday, or both? This tool answers that, and then tells you the exact moments the job will actually fire.

Most cron helpers stop at translating the expression into English. The part that causes real incidents is the next run time — especially across a daylight-saving boundary, where the same expression fires at a different wall-clock hour twice a year, or where the time you asked for does not exist at all on that date.

Everything runs locally in your browser. No expression you type is sent anywhere, and there is no sign-up.

Day-of-month and day-of-week are combined with OR, not AND

When both fields are restricted, cron runs the job when either one matches. 0 0 1 * 0 therefore fires at midnight on the first of the month and at midnight every Sunday — four to six times a month, not once.

This is the single most common cron surprise, and it is deliberate: it comes from POSIX and Vixie cron, and every mainstream implementation follows it. There is a reason. A job restricted to both "the 1st" and "Sunday" has no useful AND reading — in most months there would be no run at all.

If you actually want "the first Sunday of the month", a five-field cron expression cannot say it. The extra condition has to live in the job itself — check the date inside the script and exit early when it is not in the first seven days.

This tool flags the OR behaviour explicitly instead of silently picking a side, so an expression like 0 0 1 * 0 is never quietly read as something it is not.

What happens to a cron job when the clocks change

A wall-clock time that does not exist on a given date — inside the spring-forward gap — is skipped, and the tool reports it. Times that do exist are unaffected: the job keeps running at the same wall-clock hour.

Spring forward is the case that breaks schedules. Where daylight saving is observed, 02:30 on the second Sunday in March simply never happens. An expression like 30 2 * * * is perfectly valid, but on that one day there is no 02:30 to run at, so the run is skipped rather than moved to 01:30 or 03:30.

Instead of hiding that, the tool lists the skipped occurrences under a daylight-saving gap warning, so you can decide whether a once-a-year skip is acceptable for that job or whether the schedule should avoid the transition hour altogether.

The difference from a naive implementation is worth noting: helpers that do the arithmetic in UTC, or in a fixed offset, make the spring-forward day look ordinary and shift the job by an hour instead. Resolving the time in the target zone and asking whether it actually exists is what makes the gap visible at all.

Schedules that run less often than they appear to

0 0 31 * * does not run every month — February, April, June, September and November have no 31st. The tool detects this and warns, because the failure is silent: no error is raised, the job simply never fires.

Anything with a day-of-month above 28 has months in which it cannot run. Code written for a 31-day month is not wrong so much as conditionally scheduled, and most schedulers will never tell you which months are missing.

The check counts days against a non-leap year as the baseline, so 0 0 29 2 * is flagged too: it can only ever run in a leap year. For anything that reads like a monthly or yearly job, that is worth knowing before it ships rather than after.

If what you really want is "the last day of every month", standard five-field cron has no syntax for it. The condition belongs inside the job — and the expressions that look like they cover it are exactly the ones this warning is about.

Frequently asked questions

Does it take time zones and daylight saving into account?

Yes. Pick a time zone and the next run times are resolved against that zone, including historical and future daylight-saving transitions. Spring-forward gaps are skipped and reported; a wall-clock time that is skipped on that date is never returned as a run time.

What does 0 0 1 * 0 mean?

Both midnight on the first of the month and midnight every Sunday. When both the day-of-month and day-of-week fields are restricted, cron treats them as OR, not AND. This tool flags that behaviour instead of silently picking one side, because it is the single most common cron surprise.

Can I use names like MON or JAN?

Yes. Three-letter month and weekday names are accepted in the month and day-of-week fields, and are case-insensitive.

What about @daily and the other shortcuts?

@yearly, @annually, @monthly, @weekly, @daily, @midnight and @hourly are supported and expanded. @reboot is not supported, because it has no predictable run time — it means "when the machine starts", which is not a schedule.

Does it support six-field expressions with seconds?

Yes. If six fields are supplied, the first is treated as seconds. That is the Quartz and systemd timer convention.

Why does a valid expression sometimes have no run times?

Some expressions can never fire, such as 0 0 31 * * in a month that has no 31st, or a day-of-month and day-of-week combination that never coincide. If no run time is found within the search window, the tool says so instead of inventing an answer.

Related tools