Cron Expression Explainer

Explain a 5-field cron expression, break down each cron part, and show the last plus next run times.

Plain Language
Detecting...
Detecting...
Last Run
Detecting...
Detecting...
Detecting...
Detecting...
Part Value Range Examples Meaning
Supports standard 5-field cron expressions: minute, hour, day of month, month, and day of week.

About this tool

Cron Explainer helps developers, schedulers, SREs, and support teams explain cron fields and show last plus next scheduled run times. Use it for crontab reviews, maintenance windows, backup schedules, recurring reports, timezone-sensitive runbooks, and incident questions about when a job should have fired.

Use cases

  • Paste a 0 2 * * * expression from production and explain which minute, hour, day-of-month, month, and weekday fields drive the job.
  • Confirm whether a backup, billing task, or digest email runs hourly, daily, weekly, or only on weekdays before changing a schedule.
  • Compare the last run and next run around a deployment window so support can tell whether a missed job is a schedule issue or an execution failure.
  • Check weekday and day-of-month combinations before documenting maintenance windows or regional reporting cutoffs.

FAQ

What is Cron Explainer best used for?

Cron Explainer is best used when you need to translate a cron expression into plain language and inspect the previous and upcoming run times for a scheduled job.

What input and output should I expect?

Enter a cron expression. The tool returns an explanation of the fields and schedule plus recent and upcoming run times that can be copied into tickets, runbooks, or deployment notes.

What cron edge cases should I verify?

Cron implementations differ on seconds fields, timezone handling, day-of-week numbering, names, macros, and how day-of-month interacts with day-of-week, so confirm behavior in the scheduler you deploy.

Does it run or monitor the job?

No. It explains schedule syntax and run times only; use your scheduler, logs, and monitoring system to verify whether the actual task executed successfully.