About the Handiwork Cron Expression Explainer
The Cron Expression Explainer decodes standard Unix cron schedules into plain English. Paste a five- or six-field expression, try a preset example, and read an overall summary plus what each field — minute, hour, day of month, month, and day of week — actually means.
How to use the Handiwork Cron Expression Explainer
- Paste or type a cron expression in the input field.
- Click an example preset if you are learning the format.
- Read the summary and per-field breakdown to confirm the schedule.
Cron field order
A typical five-field cron expression is: minute (0–59), hour (0–23), day of month (1–31), month (1–12), day of week (0–7, where 0 and 7 are Sunday). Some systems add a sixth seconds field at the start. Asterisks mean “every” and slashes define steps like */15 for every 15 minutes.
What this tool does and does not do
The explainer validates common numeric patterns and translates them into readable language. It does not execute jobs, connect to your server, or compute the next run time. Named months, L/W/# tokens, and Quartz-specific extensions are not supported.
How the plain-English summary is built
Each field is explained individually, then combined into one summary sentence: a time portion from the minute and hour fields, followed by a date portion from the day-of-month, month, and weekday fields when they are not left as "every." A Monday-through-Friday weekday range is special-cased to read "on weekdays" rather than spelling out all five days.
Validation and field ranges
Every value, range, list, and step is checked against its field’s valid range — 0–59 for minutes and seconds, 0–23 for hours, 1–31 for the day of month, 1–12 for the month, and 0–7 for the day of week (both 0 and 7 mean Sunday). An out-of-range or malformed value is reported with which field caused the problem, rather than failing silently.
Continue this workflow
Use the adjacent tool when the next step calls for a different input, output, or method.
Assumptions and limitations
- This tool only explains a schedule in plain English — it does not run jobs, connect to a server, or compute the actual next execution time.
- Named months and weekdays written as text (JAN, MON), and extended tokens such as L, W, and # from Quartz-style schedulers, are not recognized — use the numeric equivalents instead.
- How a schedule actually behaves — its time zone, whether a missed run fires on wake, and daylight-saving handling — depends on the specific system running it. Confirm those details on the platform where the job executes.
Sources and standards
These authoritative references were used to verify the method and guidance on this page.
Frequently asked questions
Does this run or validate cron jobs on my server?
No. It explains what an expression means in plain English. It does not execute jobs or connect to your crontab.
Which cron format is supported?
Standard five-field Unix cron (minute hour day month weekday) and optional six-field expressions with a leading seconds field.
Why might my server schedule differ slightly?
Cron implementations vary by platform and timezone. Always confirm schedules in the environment where jobs actually run.
Can I use named months or weekdays like JAN or MON?
Not currently — the parser expects numeric values, ranges, lists, and steps (such as 1-5, */15, or 0,30). Convert named months and weekdays to their numeric equivalents before pasting the expression in.