Quick access

Saved in this browser. Sign in to keep it on all your devices.

Cron Checker

Validate cron expressions and see next run times.

This schedule runs:

This expression is valid, but no such date exists, so it will never run.

Next runs in your time zone ()

Cron Fields

Minute:
Hour:
Day:
Month:
Weekday:

Common Examples

Version 1.1 Updated What's new

Release notes

  1. v1.1 Latest
    • Added an in-depth guide below the tool, written from what the tool actually does.
    • Replaced the placeholder logic with a full cron engine for accurate next run times.

About the Cron Checker

The cron checker validates a cron expression and shows exactly when it will run next, so you can catch a wrong schedule before it goes live.

How to use it

  1. 1 Paste a cron expression such as 30 2 * * *.
  2. 2 Read the plain-English meaning.
  3. 3 Check the list of upcoming run times.

Frequently asked questions

What does 0 0 * * * mean?

It runs once a day at midnight (00:00) in the server’s time zone.

What happens if I set both day of month and day of week?

In standard cron the job runs when either field matches, not only when both do. This often surprises people.

Are 6-field cron expressions supported?

Standard cron uses 5 fields. Some tools add a seconds field at the start; remove it before checking.

The five fields, in order

┌ minute        0–59
│ ┌ hour        0–23
│ │ ┌ day       1–31
│ │ │ ┌ month   1–12 or JAN–DEC
│ │ │ │ ┌ weekday 0–7 or SUN–SAT (0 and 7 are Sunday)
* * * * *

Each field takes a single value, a list (1,15), a range (9-17), or a step (*/10). Ranges and steps combine, so 10-30/5 means minutes 10, 15, 20, 25 and 30. This checker also accepts the shortcuts @hourly, @daily, @weekly, @monthly and @yearly.

The day rule that catches people out

Most fields combine with AND, so every one must match. The two day fields are the exception. If both are restricted, the job runs when either matches. The expression 0 0 13 * 5 does not mean Friday the 13th. It runs on every 13th and also on every Friday.

A field that starts with an asterisk counts as unrestricted for this rule. So 0 0 */2 * 1 needs both conditions, and fires only on Mondays that fall on an odd-numbered date. The list of upcoming runs on this page follows the same logic, so you can see the effect before deploying.

Steps do not always divide evenly

A step counts from the start of its range and restarts with each new hour or day. With */7 in the minute field the job runs at minutes 0, 7, 14, 21, 28, 35, 42, 49 and 56, then again at 0, leaving a gap of only 4 minutes across the hour. A true every-7-minutes schedule cannot be written in cron. Values that divide 60 evenly, such as 5, 10, 15, 20 and 30, avoid the problem.

Check the clock your server uses

Times on this page are shown in your own time zone, while cron uses the zone of the machine it runs on, and most cloud servers and CI services run on UTC. GitHub Actions schedules, for one, are always UTC. A job written as 0 9 * * * on a UTC server fires at 09:00 UTC, whatever your local time is.

Daylight saving adds a second trap. A job set for 02:30 can be skipped when clocks go forward or repeated when they go back, and cron implementations handle that differently. Scheduling outside the 01:00 to 03:00 window avoids the question entirely.

Syntax this checker rejects

Only standard 5-field cron is accepted. Quartz and some cloud schedulers add a seconds field and special characters such as L, W, # and ?, which ordinary crontabs cannot read, so those are reported as errors. An impossible date such as 0 0 31 2 * is valid syntax that will never fire, and this page warns you about it.

One more crontab quirk: an unescaped % in the command part of a line is treated as a newline. If a job with a date format like +%Y-%m-%d fails only under cron, write each one as \% in the crontab.