Cron Expression Parser

Paste a cron schedule to see what it means in plain English and exactly when it will run next.

🔒 100% private — nothing is uploaded

Five fields, separated by spaces: minute hour day-of-month month day-of-week

Try:

How it works

A cron expression is five fields that together describe a repeating schedule. This tool reads each field, describes the whole thing in words, and simulates the clock forward to find the upcoming matches.

1

Type an expression

Enter a standard 5-field cron string. Ranges (1-5), steps (*/15), lists (1,15) and names (MON, JAN) are all understood.

2

Read it in English

Each field is translated into a human sentence, so you can confirm the schedule does what you intended — no guesswork.

3

See the next runs

The upcoming fire times are computed in your local time zone by stepping the clock forward minute by minute until it matches.

Cron field reference

FieldAllowed valuesSpecial characters
Minute0–59* , - /
Hour0–23* , - /
Day of month1–31* , - /
Month1–12 or JAN–DEC* , - /
Day of week0–7 or SUN–SAT (0 and 7 = Sunday)* , - /

An asterisk * means "every value". A slash sets a step, so */15 in the minute field means every 15 minutes. A hyphen makes a range (9-17), and commas build a list (0,30). When both day-of-month and day-of-week are restricted, standard cron fires when either matches.

🔒

Private by design. Parsing and the next-run calculations happen entirely in your browser with plain JavaScript. Your cron expression is never uploaded or stored — we never see it.

Frequently Asked Questions

What are the five fields in a cron expression?
In order: minute, hour, day-of-month, month, and day-of-week, each separated by a space. For example, 30 8 * * 1-5 means 8:30 in the morning on weekdays.
What do the symbols like * / - and , mean?
An asterisk * means every value. A slash sets a step, so */15 is every 15. A hyphen makes a range like 9-17, and commas build a list like 1,15.
Can I use names like MON or JAN?
Yes. Three-letter month names (JANDEC) and weekday names (SUNSAT) are understood in the month and day-of-week fields.
What time zone are the next run times shown in?
They're calculated in your device's local time zone, which is shown above the list. Keep in mind that your actual server may run cron in UTC or a different zone.
Why does it say no run times were found?
That usually means the schedule is impossible — for example asking for February 30th, a date that never occurs. Double-check the day and month fields.
Is my cron expression sent anywhere?
No. Parsing and the next-run calculations happen entirely in your browser on your own device. Your expression is never uploaded or stored, and we never see it.