Maaz Zindani

Loading the index…

↑↓ move↵ openesc close3993 pages

Free tool · Developer tools

Cron expression generator

Type a cron expression or pick a preset to get a plain-English description and the next run times in your own time zone. Edit the five fields one by one if you prefer.

  • Free
  • No sign-up
  • Runs in your browser

By Maaz Zindani · Updated

Five fields: minute, hour, day of month, month, day of week. Or type a shortcut such as @daily.
Edit one field at a time
Minute 0-59, hour 0-23, day 1-31, month 1-12 or JAN-DEC, weekday 0-6 or SUN-SAT.
Result

At 09:00, Monday through Friday0 9 * * 1-5

  • Valid 5-field cron
  • Times in UTC
Minute
0
Hour
9
Day of month
*
Month
*
Day of week
1-5
Example: the first 10 runs after 1 Jan 2026 (UTC). Your own times appear once the page loads.
WhenFrom now
Thu 2026-01-01 09:00in 9 h
Fri 2026-01-02 09:00in 33 h
Mon 2026-01-05 09:00in 4 days
Tue 2026-01-06 09:00in 5 days
Wed 2026-01-07 09:00in 6 days
Thu 2026-01-08 09:00in 7 days
Fri 2026-01-09 09:00in 8 days
Mon 2026-01-12 09:00in 11 days
Tue 2026-01-13 09:00in 12 days
Wed 2026-01-14 09:00in 13 days

* any value, , a list, - a range, / a step. Day of week: 0 or 7 is Sunday. Names such as MON and JAN work.

How to use the Cron Expression Generator

  1. Type an expression in Cron expression, or choose one under Start from a preset.
  2. Change one part at a time in Edit one field at a time: minute, hour, day, month and weekday. The expression updates as you type.
  3. Pick Show run times in your device time zone, UTC or a city, and choose how many runs to list.
  4. Read the sentence, the five fields and the run times under Result. Press Copy expression to copy it.

What does */5 * * * * mean, and how do the five fields work?

A standard cron expression has five fields separated by spaces: minute (0-59), hour (0-23), day of month (1-31), month (1-12 or JAN-DEC) and day of week (0-7 or SUN-SAT, where both 0 and 7 mean Sunday). A job runs when the clock matches all five. So */5 * * * * means: every minute that is a multiple of five, in every hour, on every day. It runs at minute 0, 5, 10 and so on, which is every 5 minutes.

Each field accepts a star for every value, a number, a list such as 1,15, a range such as 1-5, and a step such as */10 or 0-23/2. Names work too: 0 9 * * MON-FRI. A step always counts from the start of its field, so */35 * * * * runs at minute 0 and minute 35 of every hour, not every 35 minutes.

To test an expression, paste it above and read the sentence and the run times. If the description is not what you meant, change one field and watch it update. The shortcuts @hourly, @daily, @weekly, @monthly and @yearly are accepted and shown as the five-field form they stand for.

How do I run a cron job every 5 minutes, daily at midnight or on weekdays?

Pick the closest preset and adjust it. Every 5 minutes is */5 * * * *. Daily at midnight is 0 0 * * *. Weekdays at 9:00 is 0 9 * * 1-5, which the tool describes as "At 09:00, Monday through Friday". Every Monday at 8:30 is 30 8 * * 1, the first day of each month at midnight is 0 0 1 * *, and every 6 hours is 0 */6 * * *.

When you set both the day of month and the day of week, cron runs the job when either one matches. 0 0 13 * 5 runs at midnight on the 13th of every month and also on every Friday, not only on Friday the 13th. If one of the two day fields is a star, both must match, so 0 0 * * 1 runs only on Mondays. The result shows a note whenever both fields are set.

Some dates never come up. 0 0 31 2 * asks for 31 February, so the tool tells you that no run is found in the next 9 years. A schedule for 29 February is valid and gives the next leap day.

Which time zone does cron use, and what about 6-field cron?

A cron expression has no time zone of its own. It is read by a scheduler, and the scheduler decides. GitHub Actions, for example, runs scheduled workflows in UTC by default. A scheduler on your own server follows that server's settings, so check which zone it uses. That is why the run times above are shown in a zone you choose: your device zone by default, which the page labels with its UTC offset, or UTC, or one of the listed cities. Compare against your scheduler by picking its zone.

Clock changes matter in zones that use daylight saving time. The cron manual says a time that does not exist when the clocks go forward never matches, so a job set for 02:30 on that night does not run. The tool skips such times the same way, and marks a run whose UTC offset differs from the first one in the list. A time that happens twice when the clocks go back is listed once; your scheduler may run it twice.

This tool reads the five-field format that Linux cron, GitHub Actions and Kubernetes CronJobs use. Some schedulers add a seconds or a year field, which makes six or seven fields. If you paste one, the tool says how many fields it found and asks for five. GitHub Actions also states that the shortest interval it runs is every 5 minutes, so a one-minute expression there will not run as often as it reads.

Use it with

Questions

What does */5 * * * * mean?

Run every 5 minutes: at minute 0, 5, 10 and so on of every hour, every day. The first field is the minute, and */5 means every fifth value.

How do I run a cron job every day at midnight?

Use 0 0 * * *: minute 0 of hour 0, every day. The shortcut @daily means the same.

Which time zone does cron use?

The expression has none. The scheduler decides: GitHub Actions uses UTC by default, and a scheduler on your own server follows that server's settings. This tool lets you choose the zone to see run times in.

Is Sunday 0 or 7 in cron?

Both are accepted in the standard format: 0 and 7 mean Sunday. Some tools only accept 0 to 6, so 0 is the safer choice. Names like SUN also work.

What is the difference between 5-field and 6-field cron?

The standard format has 5 fields from minute to day of week. Some schedulers add a seconds field, or a year, to make 6 or 7. This tool reads the 5-field format and tells you when it finds more.

What happens to a cron job when the clocks change?

A time that does not exist, such as 02:30 on the night the clocks go forward, never matches, so the job does not run. This tool skips it too and shows the UTC offset when it changes.

How this page was made: the tool's results are computed in your browser by the code on this page, using the sources listed above; the explanations were drafted with AI help and checked against the tool's own output.