Account

What new tool do you want?

Developer Tools

Cron Expression Explainer

Translate cron expressions into plain English and list the next run times — supports ranges, steps, names and @daily-style macros.

How to use

  1. 1Type a cron expression, e.g. */15 9-17 * * 1-5.
  2. 2Read the plain-English schedule and check the upcoming run times.

How it's calculated

Fields: minute (0–59), hour (0–23), day of month (1–31), month (1–12 or JAN–DEC), day of week (0–7 or SUN–SAT, 0 and 7 are Sunday). When both day fields are restricted, a run happens if either matches (standard cron behavior).

Frequently asked questions

What does */5 mean in cron?

'Every 5th' value of that field, starting from the lowest. */5 in the minute field runs at 0, 5, 10 … 55 minutes past each hour.

How do I run a job every weekday at 9am?

Use 0 9 * * 1-5 — minute 0, hour 9, any day of month, any month, Monday to Friday.

Which time zone does cron use?

The server's time zone, unless your scheduler sets one (e.g. CRON_TZ, or UTC on most cloud schedulers). Choose UTC or local here to match.

A worked example that shows why both day fields matter

30 4 1,15 * 5 reads as "run at 4:30 AM on the 1st and 15th of every month, and also every Friday" — starting from 2024-03-01T05:00:00Z, the next run lands on 2024-03-08T04:30:00Z, which is a Friday, not the 1st or 15th. This is standard cron behavior that trips people up constantly: when both the day-of-month and day-of-week fields are restricted (not left as *), a run happens if either one matches, not only when both match simultaneously — so this schedule fires more often than someone might expect from reading "1,15" and "Friday" as if they needed to coincide.

Why a Feb 29 schedule can jump years ahead

The expression 0 0 29 2 * (midnight on February 29th) starting from 2024-03-01 doesn't run again until 2028-02-29 — a 4-year gap — because February 29th simply doesn't exist in non-leap years, and cron has no special handling for that; it just never matches on those years. This is exactly the kind of edge case that's easy to miss when writing a cron schedule by hand and only discover when a job that was supposed to run annually goes silent for years, which is precisely why checking the "next run" output here before deploying a schedule is worth the extra minute.

Why checking the time zone setting matters as much as the expression itself

Cron itself has no inherent concept of time zone — it runs against whatever clock the host machine (or the scheduler's CRON_TZ setting) uses, which varies by platform: many cloud schedulers (GitHub Actions, most container cron jobs) default to UTC, while a traditional Linux server's crontab uses the system's local time zone. The same expression, 0 9 * * 1-5, means something different in practice depending on which clock it's evaluated against, which is exactly why this tool lets you toggle between local and UTC — always confirm which one your actual production scheduler uses before trusting the "next run" time shown here as the real-world trigger time.

The description uses 24-hour time, and I only see eight upcoming runs

The expression box opens on a weekday pattern: every 15 minutes from 9 through 17, Monday to Friday. The plain-language line is written in 24-hour time. If that description cannot be built, I see a dash instead of a sentence. Show times in opens on my local time, with UTC as the other choice. The start box is optional. Leaving it empty starts the list from now. A start I cannot read stops with a message asking for a format like 2025-01-01T00:00Z. The list under the description is the next eight times, not an open-ended calendar.

Related tools

More: Developer Tools