Cron expression translator

Paste a cron expression and read it in plain English, see exactly when it fires next in your time zone — daylight-saving changes included — and build a new schedule from tabs instead of remembering which field is which. Copy the expression bare, as a crontab line, or as a GitHub Actions schedule: block. Standard five-field cron, the kind crontab, Kubernetes and GitHub Actions read. No account needed.

At 09:00 on Monday through Friday

Field by field

FieldValueMeaning
Minute0–590Minute 0
Hour0–239Hour 9
Day of month1–31*Every day
Month1–12*Every month
Day of week0–71-5Monday through Friday

Next 10 runs

Computing the next runs…

Evaluated on UTC's wall clock. This tool's rule for daylight-saving changes: a time the clock skips is listed as skipped, and a time that repeats is listed once. Vixie cron and cronie differ there — they run a skipped fixed-time job right after the change and run sub-hourly jobs through both copies of a repeated hour.

Build one instead

Schedule
Days
Hour
Minute
# At 09:00 on Monday through Friday
0 9 * * 1-5 /path/to/command
# Generated with Nodlume — https://nodlume.dev/cron-translator

Paste into crontab -e and replace the command. The expression is copied bare by the button above; these lines add the English as a comment.

English a person would write

“At 09:00 on Monday through Friday”, “Every 15 minutes between 09:00 and 17:59”, “At 00:00 on Sunday and on day 1 of the month” — the sentence says what the schedule does, including the either-day rule most readers miss.

Next runs, on a real clock

The next ten runs are computed on the wall clock of any IANA time zone, not a naive date loop: a leap day is found four years out, a spring-forward gap is shown as skipped and a repeated hour is listed once. Cron daemons handle those two edges their own way, and the tool says so beside the list.

Errors that name the field

A value out of range, a backwards range, a stray comma — each is reported against the field it sits in. Quartz syntax (L, W, #, a seconds field) is refused by name rather than silently reinterpreted.

Cron syntax reference

The five fields

In order, separated by spaces: minute hour day-of-month month day-of-week.

The five cron fields and their ranges
FieldAllowedNote
Minute0–590 means the top of the hour
Hour0–2324-hour clock; 0 is midnight
Day of month1–31Days a month lacks are skipped
Month1–12 or JAN–DECThree-letter names, any case
Day of week0–7 or SUN–SAT0 and 7 are both Sunday

Special characters

Any field can combine lists, ranges and steps: 0,30 9-17/2 * * * is valid.

The cron special characters
CharacterMeaningExample
*Every value* * * * * runs every minute
,A list1,15 in day of month: the 1st and the 15th
-A range, inclusive9-17 in hour: 9 through 17
/A step over a range or the whole field*/15: every 15 minutes; 1-31/2: every odd day
?Quartz for "no specific value"; read as * in the two day fields0 12 ? * MON-FRI

When both day fields are set

If day-of-month and day-of-week are both restricted, a day qualifies when either matches: 0 0 1,15 * 3 runs on the 1st, the 15th and every Wednesday. The one exception comes from Vixie cron, which most systems descend from: a field whose token begins with * (such as */2) counts as unrestricted, so 0 0 */2 * 1 runs only on Mondays that are odd-numbered days — both must match. The translator says which rule applies to the expression you typed.

Macros

Shorthands most crons accept in place of the five fields. @reboot also exists but runs once at daemon start and is not a schedule. GitHub Actions accepts none of them.

Cron macros and their expansions
MacroExpands to
@yearly, @annually0 0 1 1 *
@monthly0 0 1 * *
@weekly0 0 * * 0
@daily, @midnight0 0 * * *
@hourly0 * * * *

How Quartz cron differs

Quartz (Java, Spring, and libraries that copied it) has six or seven fields — a seconds field first and an optional year last — and uses ? to leave one of the two day fields unspecified, which is required there because Quartz cannot set both. It numbers weekdays 1–7 from Sunday, and adds L (the last day of the month, or in the weekday field the last such weekday — 6L is the last Friday), W (nearest weekday to a date) and # (the nth weekday, MON#2). None of those exist in standard cron, so this tool reports them as Quartz instead of guessing. To convert, drop the seconds and year fields, replace ? with *, and move last-day and nth-weekday logic into the job itself.

Cron expressions, answered

What do the five fields in 0 0 * * 1-5 mean, and why is that weekdays?
Left to right: 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, with 0 and 7 both Sunday). An asterisk means every value. So 0 0 * * 1-5 is minute 0 of hour 0 — midnight — on any day of any month, restricted by the last field to days 1 through 5, Monday through Friday. The translator above reads it as "At 00:00 on Monday through Friday".
What does */5 mean in a cron expression?
A step. */5 in the minute field means every fifth minute starting from 0: :00, :05, :10 and so on. A step can follow a range too — 9-17/2 in the hour field is every second hour from 9 through 17. Steps that do not divide the field evenly restart at the top: */7 fires at :00, :07 … :56 and then :00 again, so the last gap is four minutes, not seven. The tool flags that.
How do day-of-month and day-of-week combine?
When only one of them is set, it alone decides the day. When both are set — 0 0 1,15 * 3 — standard cron runs on days that match either one: the 1st, the 15th, and every Wednesday, not only Wednesdays that fall on the 1st or 15th. One subtlety from the original Vixie implementation: a field that starts with an asterisk, such as */2, counts as unset for this rule, so 0 0 */2 * 1 requires both — odd-numbered days that are also Mondays. The tool names which rule is in play.
Does cron support seconds?
Standard cron does not; its smallest unit is the minute, and the five fields have no seconds slot. Six-field expressions with seconds first (and seven-field ones with a year last) are Quartz syntax, used by Java schedulers, Spring and some JavaScript libraries. So are the L, W and # tokens. This tool translates the standard five-field form and tells you when an expression is Quartz instead of guessing at it.
What time zone does cron use?
The clock of the machine running the daemon — usually the server's local time, which on cloud hosts is often UTC. Kubernetes CronJobs default to the controller's zone unless timeZone is set; GitHub Actions schedules are always UTC. This page evaluates the next runs on whichever zone you pick, defaulting to your own, so you can check what "0 9" means for a server in another region before you deploy it.
How do I run a job every 90 minutes?
Not with one expression: cron fields describe positions in an hour, day, month and week, not intervals that carry across an hour boundary. */90 is rejected because the minute field only reaches 59. Two lines come close — 0 0-21/3 * * * and 30 1-22/3 * * * together fire at 00:00, 01:30, 03:00 … 22:30 — or the job can sleep and reschedule itself. The same limit applies to every 45 minutes, every 36 hours and other intervals that do not divide the cycle evenly.
Does this tool send my cron expression anywhere?
No. Parsing, the English, the next-run calculation and the time-zone arithmetic all run in your browser with the Intl API; nothing is posted to Nodlume or anyone else, nothing is stored, and no account is needed. Reload and the page starts from the example again.

Where the schedule goes next

A scheduled job usually calls something — an API route that rebuilds a report, a script that validates a payload. In the Nodlume workspace you design the route tree and the data model those jobs touch on a canvas and export a real Next.js project. Meanwhile the Zod schema builder types the payload a job produces, and the MCP server generator gives an agent a tool to call on that schedule.

We'd like to use Google and Microsoft Clarity cookies to understand how Nodlume is used (including masked session replays) and to measure our advertising. Optional cookies only load if you accept, and declining does not affect anything in the app.