Developer / Debugging

Cron Expression Parser

Parse 5-field cron schedules, inspect each field, and preview upcoming run times directly in your browser. Parse 5-field cron schedules, inspect each field, and preview the next run times directly in your browser.

Yes

Valid

Next runs

Std

Day rule

UTC

Timezone

Loaded weekday schedule sample

Quick notes

This tool supports standard 5-field cron plus shortcuts like `@daily` and `@hourly`.

Month aliases like `JAN` and weekday aliases like `MON` are supported.

When both day-of-month and day-of-week are set, standard cron usually treats that as an OR match.

If you paste a 6-field Quartz expression, the tool will flag that instead of failing silently.

Next-run previews use your current browser timezone: `UTC`.

Cron expression

Normalized expression

0 9 * * 1-5

Human summary

minute 0, during hour 9, on day-of-week 1-5

Detected format

Standard 5-field cron

Shortcut expansion

If you enter a shortcut like @daily, the expanded 5-field form will appear here.

Field overview

Minute

Hour

Day of month

Every day of month

Month

Every month

Day of week

1-5

1 (Mon), 2 (Tue), 3 (Wed), 4 (Thu), 5 (Fri)

Next run times

Wed, Jul 29, 2026, 9:00 AM
Thu, Jul 30, 2026, 9:00 AM
Fri, Jul 31, 2026, 9:00 AM
Mon, Aug 3, 2026, 9:00 AM
Tue, Aug 4, 2026, 9:00 AM

Parsed JSON

[
  {
    "name": "minute",
    "source": "0",
    "wildcard": false,
    "values": [
      0
    ]
  },
  {
    "name": "hour",
    "source": "9",
    "wildcard": false,
    "values": [
      9
    ]
  },
  {
    "name": "dayOfMonth",
    "source": "*",
    "wildcard": true,
    "values": [
      1,
      2,
      3,
      4,
      5,
      6,
      7,
      8,
      9,
      10,
      11,
      12,
      13,
      14,
      15,
      16,
      17,
      18,
      19,
      20,
      21,
      22,
      23,
      24,
      25,
      26,
      27,
      28,
      29,
      30,
      31
    ]
  },
  {
    "name": "month",
    "source": "*",
    "wildcard": true,
    "values": [
      1,
      2,
      3,
      4,
      5,
      6,
      7,
      8,
      9,
      10,
      11,
      12
    ]
  },
  {
    "name": "dayOfWeek",
    "source": "1-5",
    "wildcard": false,
    "values": [
      1,
      2,
      3,
      4,
      5
    ]
  }
]

Minute and hour

Minute: 0

Hour: 9

Date logic

Day of month: Every day of month

Month: Every month

Day of week: 1 (Mon), 2 (Tue), 3 (Wed), 4 (Thu), 5 (Fri)

Practical signals

Valid expression. You can inspect it, copy the normalized version, and compare upcoming run times without reaching for server docs.

Next-run previews are often the real reason people revisit cron tools. Seeing actual timestamps is much faster than mentally simulating the rule.

Why this gets reused

Cron syntax is easy to forget and even easier to misread when you are moving fast.

People usually do not want just a parser. They want confidence that the job runs when they think it runs.

Field-level summaries, shortcut expansion, and next-run previews make this useful during deployments, incident checks, and server maintenance.

Strong first-use cases

Checking whether a backup job really runs on weekdays and not weekends.

Explaining a copied cron line in plain language to teammates.

Spotting OR behavior when both day-of-month and day-of-week are configured.