Inspectors

Cron Job Parser

Paste a cron expression and get a plain-English explanation of when it runs, plus a list of the next N execution times. The tool handles standard 5-field cron (minute hour day month weekday), 6-field cron with seconds, and named schedules like @yearly, @monthly, @weekly, @daily, and @hourly. Uses cronstrue for human-readable descriptions.

Cron Job Parser — Explain a cron expression and list its next run times

What it does

  • ▸Explains cron expressions in plain English (e.g., 'At every 15th minute past every hour from 9 through 17 on every day-of-week from Monday through Friday')
  • ▸Lists the next N run times (configurable, up to 50)
  • ▸Supports 5-field and 6-field cron expressions
  • ▸Handles named schedules: @yearly, @monthly, @weekly, @daily, @hourly
  • ▸Validates the expression and reports errors for invalid syntax
  • ▸Exports next run times as CSV or ICS (calendar) files

Use cases

  • ▸Understanding what a cron expression in a config file actually does
  • ▸Verifying that a schedule runs at the expected times before deploying
  • ▸Debugging a cron job that runs at unexpected times
  • ▸Generating calendar entries for scheduled job executions

How it works

1

Paste your cron expression (e.g., */15 9-17 * * 1-5) into the input

2

The tool explains it in plain English using cronstrue

3

The next N run times are computed and listed

4

Export the run times as CSV or ICS if needed

Frequently asked questions

1What's the difference between 5-field and 6-field cron?

5-field cron has minute, hour, day of month, month, day of week. 6-field cron adds a seconds field at the beginning. Most cron daemons (Linux crontab) use 5 fields. Some schedulers (Quartz, Spring) use 6 fields with seconds.

2Does it support special characters like L, W, and #?

The tool supports standard cron syntax including * (any), , (list), - (range), / (step). Extended characters like L (last), W (nearest weekday), and # (nth weekday) are parser-dependent and may not be supported.

3Can I export the next run times to my calendar?

Yes. The tool can export the next run times as an ICS (iCalendar) file, which you can import into Google Calendar, Apple Calendar, or Outlook. It can also export as CSV for spreadsheets.

Related tools

Unix Time Converter — Convert between Unix timestamps and human-readable dates

Unix Time Converter

Convert between Unix timestamps and human-readable dates

Date Difference Calculator — Calculate the difference between two dates in days, hours, minutes, seconds, and business days

Date Difference Calculator

Calculate the difference between two dates in days, hours, minutes, seconds, and business days

Log Timestamp Normalizer — Normalize mixed timestamp formats in log lines to a single target format

Log Timestamp Normalizer

Normalize mixed timestamp formats in log lines to a single target format

Semver Range Tester — Parse semver versions and test them against range expressions (npm/cargo/go syntax)

Semver Range Tester

Parse semver versions and test them against range expressions (npm/cargo/go syntax)

Use Cron Job Parser offline in Devinity

All 95 tools run locally on your Mac. No internet required, no data sent to servers.

Download Devinity →