Cron Expression Parser
Parse, validate and understand any cron expression instantly
Plain English
Runs every 5 minutes
Field Breakdown
Next 5 Scheduled Runs
Thu, Sep 10, 2026
07:10 AM
Thu, Sep 10, 2026
07:15 AM
Thu, Sep 10, 2026
07:20 AM
Thu, Sep 10, 2026
07:25 AM
Thu, Sep 10, 2026
07:30 AM
Common Presets
Syntax Reference
*every value*/nevery n units-range (e.g. 1-5),list (e.g. 1,3,5)About the Cron Expression Parser
This cron expression parser explains a schedule in plain English and lists the next run times. Seeing the actual upcoming dates is the only reliable way to confirm a cron line does what you meant.
A cron expression parser exists because the format is compact and unforgiving. Five fields — minute, hour, day of month, month, day of week — and no feedback until the job either runs or does not.
The upcoming run times are the useful output. `0 0 * * 0` reads plausibly as "midnight daily" to someone skimming, but the trailing 0 restricts it to Sundays. A list of the next five dates makes that obvious before the job silently fails to run for six days.
The classic trap is combining day-of-month and day-of-week. When both are restricted, cron treats them as OR rather than AND, so `0 0 1 * 1` runs on the 1st of the month *and* every Monday. Almost nobody intends that, and the parsed explanation surfaces it.
How to use the Cron Expression Parser
- Paste your cron expression. Enter the five-field schedule.
- Read the explanation. See the schedule described in plain English.
- Check the next runs. Confirm the upcoming dates match your intent.
- Adjust and re-check. Edit the fields and verify the schedule again.
Cron Expression Parser features
- Plain-English description of any cron expression
- The next scheduled run times listed
- Each field editable separately: minute, hour, day of month, month, day of week
- Presets for the common schedules
- Copy the expression
Frequently asked questions
What do the five fields mean?
In order: minute, hour, day of month, month, and day of week. An asterisk means every value, so 0 9 * * 1 is nine o'clock on Mondays.
Why check the next run times?
Because cron syntax is easy to write and hard to read. Seeing the actual upcoming dates is the only reliable way to confirm a line means what you intended — most cron mistakes are silent until the job runs at the wrong time.
What is the classic cron mistake?
Setting both day of month and day of week. Cron treats them as OR, not AND, so 0 0 1 * 1 runs on the first of the month and on every Monday — not on Mondays that fall on the first. Leave one as an asterisk.
How do I run something every fifteen minutes?
Use a step value in the minute field: */15 * * * *. Listing 0,15,30,45 does the same thing and is arguably clearer to whoever reads it next.
Which time zone do the times use?
The next run times are worked out in your browser's local time zone, and no zone conversion is offered. Your server will use its own zone — usually UTC — so check that before relying on an exact hour.