Read the line that is already in the repo
A Linux crontab schedule is five fields separated by spaces: minute, hour, day of month, month, day of week. In 0 2 * * * the minute is 0, the hour is 2, and the three stars leave the calendar open.
Cron Expression opens on Parse expression with 0 */2 * * * in the box. Replace that sample, then choose Explain; The description is one clause per field, joined by commas, starting with "At".
For 0 2 * * * the page prints: At Minute 0, Hour 2, every Day, every Month, every Weekday.
The sentence restates the tokens; It does not collapse them into "02:00 every day" and it does not name a time zone. The zone belongs to the host that runs cron; some daemons also honor CRON_TZ. Field order and Sunday as 0 or 7 are in crontab(5): https://man7.org/linux/man-pages/man5/crontab.5.html
Ranges stay literal in the sentence
*/15 9-18 * * 1-5 prints: At every 15 Minute, Hour 9-18, every Day, every Month, Weekday 1-5.
Month and weekday names appear only when that field is a single integer. A range or a list is copied through, so you see Hour 9-18 and Weekday 1-5 rather than "Monday to Friday" or a clock window. On a typical cron, hour 9-18 includes hour 18. With minute */15, fires land on minute 0, 15, 30, and 45 of those hours, through 18:45. The page does not list those times.
30 3 * * 0 prints: At Minute 30, Hour 3, every Day, every Month, weekday Sun. Digits 0 through 6 map to Sun through Sat; crontab(5) also allows 7 for Sunday. This page has names for 0–6 only; 7 passes the numeric check and does not receive the Sunday label. Use 0 when you want that label, then confirm the daemon treats 7 as Sunday.
0 8 1 * * prints: At Minute 0, Hour 8, Day 1, every Month, every Weekday. The weekday is open, so the calendar limit is day 1.
Rebuild the same line from the five boxes
Build expression shows minute, hour, day, month, and weekday, each starting as *. Generate joins the boxes with spaces and runs the same check used by Explain.
Every six hours at minute 0 is 0, */6, *, *, *. The description is: At Minute 0, every 6 Hour, every Day, every Month, every Weekday. The step sits on the hour; When the daemon counts from 0, the fires are 00:00, 06:00, 12:00, and 18:00. The page stops at "every 6 Hour".
Parse and build share one checker
Either mode ends on the same description; Treat that sentence as the page's reading of the tokens, then compare it with the schedule you meant.
When the job ran on the wrong day
Any field count other than 5 or 6 produces the message that a cron expression requires 5 or 6 fields.
With six fields the page keeps the last five and reads them as minute, hour, day, month, and weekday. There is no seconds box; A line such as */10 * * * * * — every 10 seconds if the first field is seconds — is explained as the remaining * * * * *. The page prints: At every Minute, every Hour, every Day, every Month, every Weekday. The */10 never reaches the description; Quartz and some cloud schedulers put seconds first; this page's six-field behavior is not their semantics.
MON, JAN, ?, L, and W fail the field check. Accepted pieces are *, an integer, */n, n-m, and commas joining those pieces. A list such as 1,15 stays literal, so the day clause reads Day 1,15.
When both day-of-month and day-of-week are restricted, the description still prints both clauses side by side. crontab(5) runs the command when either field matches. 30 4 1,15 * 5 runs at 04:30 on the 1st, on the 15th, and on every Friday. This page prints: At Minute 30, Hour 4, Day 1,15, every Month, weekday Fri. The weekday is a single digit, so it becomes the name Friday. The sentence still does not apply that OR; Kubernetes CronJob and other hosted schedulers document their own combination rule.
Numbers outside a calendar range can still look valid here. Hour 99 receives a description; Before the line goes into crontab, keep minutes in 0–59, hours in 0–23, days of month in 1–31, months in 1–12, and weekdays inside the range that daemon documents (often 0–7 on Linux crontab).
The expression only chooses the fire time
The command path, an overlap lock, and failure alerts belong in the command half of the crontab entry. This page does not install the job or run it. Parsing happens in the browser; the component does not post the expression to an API.
When the log line you are comparing is a Unix timestamp, Timestamp separates seconds from milliseconds and shows UTC beside local time.
When the scheduled command is a docker run that still needs to become Compose, do that on Turn docker run into Compose. The schedule and the container flags are separate edits.
Related utilities are on Developer tools. The Chinese version of this guide is . More guides are on Guides.
Side-by-side checks
| Expression | Sentence from the page | Check outside the page | 0 2 * * * | At Minute 0, Hour 2, every Day, every Month, every Weekday | Host time zone | |
|---|---|---|---|---|---|---|
*/15 9-18 * * 1-5 | At every 15 Minute, Hour 9-18, every Day, every Month, Weekday 1-5 | Hour 18 is included | ||||
30 3 * * 0 | At Minute 30, Hour 3, every Day, every Month, weekday Sun | 7 has no weekday name here | ||||
*/10 * * * * * | At every Minute, every Hour, every Day, every Month, every Weekday | The leading */10 is dropped | ||||
30 4 1,15 * 5 | At Minute 30, Hour 4, Day 1,15, every Month, weekday Fri | crontab(5) also fires when the day matches |
References
Field order, Sunday as 0 or 7, and the OR when both day-of-month and day-of-week are restricted: crontab(5), https://man7.org/linux/man-pages/man5/crontab.5.html
FAQ
Does 0 2 * * * mean 02:00 in my time zone: The five fields carry no zone.
Six fields */10 * * * * * every ten seconds: This page keeps the last five; the seconds field is dropped and the sentence reads “every minute.” Quartz uses different rules.
Both day-of-month and weekday restricted: Classic crontab(5) OR logic; the page lists both clauses without saying OR—read man crontab(5) before you trust side effects.
Log timestamps do not line up with cron: Timestamp Converter for UTC vs local, then compare to the host that runs 0 2 * * *.
Worked example (step by step)
1. Goal: every 15 minutes 09:00–18:00 weekdays → draft */15 9-18 * * 1-5.
2. Paste into Cron Expression Explain → At every 15 Minute, Hour 9-18, every Day, every Month, Weekday 1-5.
3. Remember hour 18 is inclusive—last fire 18:45.
4. Build expression boxes: */15, 9-18, *, *, 1-5; generated line matches.
5. First of month 08:00: 0 8 1 * * with weekday *.
6. Mis-paste six fields 0 30 2 * * *; page explains 30 2 * * *—confirm the seconds field dropped.
7. Backup runs docker compose from Docker run to Compose; schedule stays 0 3 * * * separately.
8. Log 1732060800 in Timestamp Converter to see if it sits in the 02:00 window.