How to Read a Cron Expression in Plain English

You’ve opened a crontab file — maybe one you inherited, maybe one you wrote six months ago — and you’re staring at 0 3 * * 1-5 trying to remember whether that runs on weekdays or weekends, and at what time in which timezone. Cron syntax is compact by design, five fields packed with asterisks, ranges, and step values, and that compactness is exactly what makes it unreadable at a glance for anything beyond the simplest schedules.

The five fields (minute, hour, day of month, month, day of week) each accept their own syntax for ranges, lists, and steps, and the rules interact in ways that aren’t obvious — a day-of-month and day-of-week field combined uses OR logic, not AND, which trips people up constantly.

What reading a cron expression actually involves

Each field in a standard cron expression is evaluated independently against the current time: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is typically Sunday). Asterisks mean “every value,” commas separate lists, hyphens define ranges, and a slash defines a step interval. Translating the combination into an actual sentence — “at 3:00 AM, Monday through Friday” — means parsing all five fields together and accounting for the special OR-logic case when both day fields are restricted at once.

Why people get stuck here

• Forgetting cron’s minute-first field order. It’s easy to misread the first two fields, especially coming from other scheduling formats that order fields differently.
• The day-of-month/day-of-week OR trap. When both fields are restricted (not left as *), cron runs the job if either condition matches, not only when both do — this catches almost everyone at least once.
• Step values and ranges combined. An expression like */15 9-17 * * * (every 15 minutes, but only during business hours) is common but genuinely hard to parse visually without practice.
• Timezone assumptions. Cron expressions don’t carry timezone information themselves — the same expression runs at a different wall-clock time depending on the system’s configured timezone, which is easy to forget when reading someone else’s crontab.

What a good cron explainer looks like

Translates the whole expression into one readable sentence

“At 3:00 AM, Monday through Friday” is immediately understandable in a way that 0 3 * * 1-5 isn’t, especially to someone who doesn’t read cron syntax daily.

Breaks down each field individually

Alongside the plain-English sentence, showing what each of the five fields evaluated to individually helps you verify the interpretation matches what you intended, field by field.

Handles the day-of-month/day-of-week edge case correctly

Explaining the OR-logic special case explicitly, rather than silently getting it wrong, is what separates a genuinely useful explainer from one that only handles the simple cases.

Common mistakes to avoid

• Writing a schedule you think is right without checking the actual generated explanation, especially for anything involving both day fields.
• Forgetting that cron doesn’t carry timezone context — a schedule written and tested in one timezone runs at a different local time on a server configured differently.
• Confusing */5 in the minute field (every 5 minutes) with 5 alone (only at the 5th minute of the hour) — visually similar, functionally very different.
• Assuming day-of-week 0 and 7 are different values — most cron implementations treat both as Sunday.
• Deploying a schedule copied from a tutorial without re-reading it in the context of your own intended run time.

How to do it with Cron to Human Sentence

Online Tool Store’s Cron to Human Sentence explains your expression entirely in your browser.

1. Open the Cron to Human Sentence tool.
2. Paste your 5-field cron expression.
3. Read the plain-English sentence explaining when it runs.
4. Check the field-by-field breakdown to confirm each part matches your intent.

Frequently asked questions

Why does my cron job run more often than I expected?

The most common cause is the day-of-month/day-of-week OR-logic trap — if both fields are restricted, the job runs whenever either condition is true, not only when both match. Leave one of the two fields as * if you only want the other to apply.

Does a cron expression include timezone information?

No — a standard 5-field cron expression only defines a schedule relative to the system clock it’s evaluated on. The same expression can run at different real-world times depending on the server or scheduler’s configured timezone, so always confirm that separately.

What’s the difference between */15 and 15 in the minute field?

*/15 means “every 15 minutes” (so at :00, :15, :30, :45), while 15 alone means “only at the 15th minute of the hour” (so once per hour, at :15). They look similar but produce very different schedules.

Final thought

Cron syntax rewards fluency but punishes assumption — before deploying a schedule, translate it back into a sentence and check it says what you actually meant, especially anywhere both day fields are involved.

Try the free Cron to Human Sentence tool