Cron Parser
Explain a cron expression in plain words, field by field, and list its next 10 run times in any time zone.
5 fields: minute hour day month weekday. With 6 fields, seconds come first.
Shortcut: Ctrl/⌘ + Enter to load an example
Description
Standard 5-field format
Fields
| Field | Value | Meaning | Allowed values |
|---|---|---|---|
| Minute | 0 | minute 0 | 0–59 |
| Hour | 9 | 9:00 | 0–23 |
| Day of month | * | every day | 1–31, L (last day) |
| Month | * | every month | 1–12 or JAN–DEC |
| Day of week | 1-5 | Monday through Friday | 0–7 or SUN–SAT (0 and 7 are Sunday), 5L, 1#2 |
Next 10 runs
How to use
- Type a schedule into “Cron expression”, such as 0 9 * * 1-5, or pick one from “Common schedules”.
- A sentence explains what the schedule means, and the table below explains each field.
- Choose a time zone, and “Next 10 runs” lists when the schedule actually fires there, along with how far away each run is.
- If the expression is invalid, the message below the field names the field and value at fault and what is allowed.
FAQ
Is my input uploaded?
No. Parsing and run time calculations happen in your browser, and your expression never leaves your device.
What are the five fields of a cron expression?
In order: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC) and day of week (0–7 or SUN–SAT, where both 0 and 7 are Sunday). * means any value, commas list values (1,15), a hyphen gives a range (1-5) and a slash a step (*/15 is every 15 minutes).
What is the 6-field format?
With six fields, a seconds field (0–59) comes first, so */30 * * * * * runs every 30 seconds. Spring, Quartz and node-cron support it; Linux crontab only supports five fields. The tool detects the format from the number of fields.
What happens when both day of month and day of week are set?
Standard cron treats them as OR: 0 0 1 * 1 runs on the 1st of every month and on every Monday, not only on Mondays that fall on the 1st. The tool points this out when it happens. To restrict just one of them, set the other to * or ?.
Which special characters are supported?
L (day of month: the last day), 5L (day of week: the last Friday of the month), 1#2 (the second Monday of the month), ? (no specific value in a day field), plus shortcuts such as @yearly, @monthly, @weekly, @daily, @hourly and @reboot. The nearest weekday (15W), L-3 and Jenkins-style H are not supported and are reported as errors.
How are time zones and daylight saving time handled?
Run times are calculated in the time zone you choose, your device’s by default. Cron on a server usually uses the server’s time zone (often UTC), so pick the same zone to check. When daylight saving time starts, a time that does not exist (such as 2:30 on that March day in New York) moves to just after the change.
Why does the description take a moment to appear?
The code that writes descriptions and calculates run times is fairly large, so it loads after the page opens to keep the page fast. Once it has loaded, results update instantly.
Related tools
Unix Timestamp Converter
Convert Unix timestamps to dates and back. Detects seconds or milliseconds and shows ISO 8601, relative time and multiple time zones.Time Zone Converter
Convert a time to cities around the world, with UTC offsets, daylight saving time and a 24-hour meeting planner.Regex Tester
Test JavaScript regular expressions live: highlight matches, list groups, preview replacements, with a syntax explainer and common patterns.