Cron Expression Parser

Parse, validate, and explain cron schedules with field details and upcoming run times.

Cron expression
Enter a five-field Unix cron expression, or include an optional seconds field when your scheduler supports it.

Valid expression

Quick presets

Start from a common schedule, then adjust the fields directly.

Next executions
Preview the next 10 matching run times from the current browser time.
Valid expression

Summary

Every 5 minutes

Next run times use local time from this browser.

Field breakdown

Read each field from left to right to see what part of the schedule it controls.

FieldValueAllowed range
Minute*/50-59
Hour*0-23
Day of month*1-31
Month*1-12 or JAN-DEC
Day of week*0-7 or SUN-SAT

Next executions

#Date and timeRelative
105/15/2026, 03:00:00in 2 minutes
205/15/2026, 03:05:00in 7 minutes
305/15/2026, 03:10:00in 12 minutes
405/15/2026, 03:15:00in 17 minutes
505/15/2026, 03:20:00in 22 minutes
605/15/2026, 03:25:00in 27 minutes
705/15/2026, 03:30:00in 32 minutes
805/15/2026, 03:35:00in 37 minutes
905/15/2026, 03:40:00in 42 minutes
1005/15/2026, 03:45:00in 47 minutes

Understand Cron Schedules Before You Ship Them

Cron expressions are compact, but a small field mistake can run a job far more often, or far less often, than intended. This parser validates the expression in your browser, explains the schedule in plain language, breaks down every field, and previews upcoming run times.

When To Use It

  • Check a deployment, backup, cleanup, or notification schedule before adding it to a server, CI system, or task runner.
  • Compare a copied cron expression with the schedule you actually expect.
  • Teach or debug cron syntax by changing one field at a time and watching the explanation update.

Supported Format

The tool supports standard five-field Unix cron expressions: minute, hour, day of month, month, and day of week. It also accepts a six-field expression with seconds at the front for schedulers that support second-level precision.

Reading The Result

The summary gives a plain-language description, while the field table shows how the raw expression is split. The upcoming run times use your browser’s local time zone, so compare them with the time zone used by the scheduler that will run the job.

Notes

  • Day-of-week values commonly use 0 or 7 for Sunday, and names such as MON or FRI are also accepted.
  • Month names such as JAN or DEC can make production schedules easier to review.
  • If your scheduler uses a different cron dialect, confirm special tokens such as ?, L, W, or # in that scheduler’s own documentation.