How to use it 01 Type an expression or pick a preset; the read-back, field table and upcoming list update as you type. 02 Check the field table for the expanded values of each field. 03 Copy 1–50 upcoming runs, or export them as .ics. 04 Build an expression from the pickers when you would rather not type one.
Worked readouts
*/15 9-17 * * 1-5 reads "every 15 minutes during hour 9–17, on Monday–Friday". From Monday 28 September 2026, 10:30 local, the next four runs are 10:45, 11:00, 11:15, 11:30 .
0 0 13 * 5 reads "00:00, on day 13 of the month or on Friday"; from 1 October 2026 the list runs Friday 2, Friday 9, Tuesday 13 , Friday 16.
0 0 29 2 * answers 2028-02-29 , the next leap day.
30 0 3 * * * reads "03:00, at second 30, every day" — a six-field expression.
0 0 31 2 * finds nothing in the 12-year window and reports "no occurrence" instead of silence.
The picker set to 09:00 builds 0 9 * * *.
The day fields are ORed Cron matches each field independently and ANDs them, except the day-of-month and day-of-week pair: when both are restricted, a run fires when either matches. Names are case-insensitive, ranges may wrap (22-2), 7 is Sunday alongside 0, and a step applies to a range or to *. The panel looks ahead twelve years, which is why impossible dates end with an explicit no-occurrence message.
Limits
Vixie dialect only. Quartz extensions (L, W, #, ?) are not accepted; seconds are a sixth field, not a Quartz field.
Local time. Times are in the machine's zone, while servers commonly run UTC — convert before moving a schedule across. What it does not do. It does not run or schedule jobs and does not read crontab files; it only parses and previews. JWT decodes tokens and Text diff compares texts.
Friday the 13th is not a cron expression 0 0 13 * 5 fires every Friday and every 13th, not only Friday the 13th — the panel warns "it fires when either matches", because the AND belongs inside the job, not the expression. The time zone is the other trap: a schedule that reads 09:00 locally is a different instant on a UTC server, and the upcoming list changes with the machine's zone.
Where it is used Checking a schedule before editing crontab Read the expression back, count the expanded values and cross a weekend in the upcoming list before saving the file.
Dropping a reminder into a calendar Export the next runs as .ics and open them in a calendar to see the schedule as dates.
Privacy Expressions and generated schedules are parsed in your browser; nothing is uploaded, stored or logged.
References
Michael Kerrisk, crontab(5) — Linux manual page , man7.org (访问日期:2026-10-07)— field syntax and the day-field OR rule.
Wikipedia, Cron , en.wikipedia.org (访问日期:2026-10-07)— dialects, names and macros.
IETF, RFC 5545: iCalendar , rfc-editor.org (访问日期:2026-10-07)— the calendar format used by the .ics export.
Calculators in this hub
Hand-picked tools, one click away. The mini versions compute live and carry your values into the full calculator.
Sources & review
Reviewed by CalcX Editorial Team
Updated 2026-10-07