Cron Expression Validator

Check a five-field cron expression, read it as a plain-English sentence and see its next five run times in your local time before you deploy it.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Cron Expression Validator?

The Cron Expression Validator checks a standard five-field cron expression (minute, hour, day of month, month, day of week), explains it in plain English and lists the next five times it will run. It accepts the syntax used by crontab and most schedulers: wildcards (*), lists (1,15), ranges (1-5), steps (*/10) and month or weekday names such as JAN and MON.

Parsing uses the cron-parser library and the description comes from cronstrue, so the next-run list follows real calendar rules, including months with 30 days and the day-of-month or day-of-week behaviour of Unix cron. Run times are shown in your browser's time zone.

Eight ready-made examples, from "every 5 minutes" to "Saturdays at 2:30 PM", can be loaded with one click as starting points. Six- and seven-field formats with seconds or years are rejected.

  • Validates the five standard cron fields with cron-parser
  • Supports *, lists, ranges, steps and month and weekday names
  • Plain-English description of the schedule
  • Next five run times in your local time
  • Eight one-click common examples; runs in your browser
Read the guide: Crontab Syntax & Cron Expressions: The Complete Guide

Updated

How to use the Cron Expression Validator

  1. Type or paste a five-field cron expression, for example 30 2 * * 1-5.
  2. Click Validate to check it, read the plain-English description and see the next five run times.
  3. If it is invalid, read the error message, which says what the parser could not accept.
  4. Load one of the common examples to start from a known-good schedule, then copy the expression.

Worked examples

Business hours, every 15 minutes

Input

*/15 9-17 * * 1-5

Output

Every 15 minutes, between 09:00 AM and 05:59 PM, Monday through Friday

The hour range 9-17 includes the 17:00 hour, so the last run is 17:45, not 17:00. Use 9-16 if the job must stop by 17:00.

Day of month OR day of week

Input

0 9 1 * 1

Output

At 09:00 AM, on day 1 of the month, and on Monday. From Saturday 24 October 2026 (UTC) the next runs are Monday 26 October, Sunday 1 November and Monday 2 November

Restricting both day fields means either can trigger a run. To run only on Mondays that fall on the 1st, check the date inside the job instead.

Background and insight

Cron first appeared in Version 7 Unix in 1979. The five-field format most people use today comes from Paul Vixie's rewrite in 1987, "Vixie cron", which became the default on most Linux distributions. Kubernetes CronJobs, GitHub Actions schedules and many cloud schedulers still use that same five-field syntax.

Not every scheduler agrees on the details. Quartz (Java) and Spring add a leading seconds field and use ? for "no specific value". AWS EventBridge uses six fields with a year at the end. Pasting a Quartz expression into crontab, or the other way round, is a classic source of jobs that never run. This validator follows the five-field Unix format.

One subtle rule catches experienced engineers: in Vixie cron, if both day of month and day of week are restricted, the job runs when either matches, not both. 0 9 1 * 1 runs at 9 AM on the 1st of the month and also every Monday.

Common use cases

  • Before deploying a scheduled job

    Confirm a crontab line or Kubernetes CronJob schedule means what you think before it goes live.

  • Reading someone else's schedule

    Turn an unfamiliar expression in a config file into a sentence you can check.

  • Writing documentation

    Get a plain-English description to put next to the expression in a runbook or README.

  • Learning cron syntax

    Experiment with steps, ranges and lists and see how the description and next runs change.

Tips and limitations

  • Next runs are shown in your browser's time zone. A server or GitHub Actions runner in UTC will fire at different local times.
  • Avoid scheduling at 02:00 to 03:00 local time on servers that observe daylight saving; that hour is skipped or repeated once a year.
  • */7 in the minute field runs at 0, 7, 14 ... 56 and then again at 0, so the gap across the hour is 4 minutes, not 7.
  • Many teams spread load by picking an odd minute (17 3 * * *) instead of 0, so every job in the company does not start at once.
  • GitHub Actions can delay scheduled workflows during busy periods, and the shortest interval it allows is every 5 minutes.

Sources and further reading

  1. crontab(5): tables for driving cron, Linux man-pages project. The five-field format, step values and the day-of-month or day-of-week rule
  2. crontab: schedule periodic background work, The Open Group. The POSIX specification of the crontab format
  3. CronJob, Kubernetes. Schedule syntax and the timeZone field
  4. Events that trigger workflows: schedule, GitHub Docs. Scheduled workflows run in UTC
  5. Cron Trigger Tutorial, Quartz Scheduler. The six- and seven-field Quartz format with seconds and ?

Frequently asked questions

What do the five cron fields mean?

In order: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or JAN-DEC) and day of week (0-6 or SUN-SAT, where 0 is Sunday and 7 is also accepted as Sunday). An asterisk means every value, so * * * * * runs once a minute.

Does this validator support Quartz or Spring cron with seconds?

No. It validates the five-field Unix format used by crontab, Kubernetes CronJobs and GitHub Actions. Quartz and Spring expressions have six or seven fields, starting with seconds and sometimes ending with a year, and use ? in a day field. Drop the seconds field to check the rest here.

What time zone does a cron schedule run in?

Classic cron uses the server's local time zone. Kubernetes CronJobs use the controller's zone unless you set spec.timeZone, and GitHub Actions schedules always run in UTC. This page shows next runs in your browser's zone, so convert if your scheduler differs.

How do I run a cron job every 15 minutes?

Use */15 * * * *. The step value /15 means every 15th minute starting from 0, so it fires at :00, :15, :30 and :45 every hour. To limit it to working hours on weekdays, use */15 9-16 * * 1-5.

Why does my cron job run on extra days?

When both day of month and day of week are restricted, Unix cron runs the job when either one matches. 0 9 1 * 1 therefore runs on the 1st of every month and on every Monday. Leave one of the two fields as * unless you want that OR behaviour.

Is there an in-depth guide to the Cron Expression Validator?

Yes. “Crontab Syntax & Cron Expressions: The Complete Guide” covers the background, how it works, common pitfalls and worked examples. Read the full guide.