Skip to content

Cron expression explainer

Paste a cron expression and see what it means in plain language, with warnings about common traps and the next 10 runs in your time zone.

AvailableIn your browserInput: Text

How to use: Cron expression explainer

  1. Type or paste your cron expression (5 fields, or 6 with seconds first) or pick a quick example.
  2. Read the plain-language explanation and check any warnings that appear.
  3. Choose the time zone and check the next 10 runs; use “Start from” to look at another date.

What it accepts and what you get

Input
A classic 5-field cron expression (minute, hour, day of month, month, weekday), a 6-field one with seconds first, or a shortcut such as @daily.
Output
A sentence explaining when it runs, warnings about common traps and the list of the next 10 runs in the chosen time zone.
Where your data is processed
Your data is processed in your browser and is not sent to our servers.

Limitations and notes

  • It follows classic (Vixie) cron semantics. Quartz symbols (? L W #) are not supported and you are told why.
  • If you set both day of month and weekday, cron runs when either one matches, not both.
  • Times that do not exist because of a clock change are skipped and repeated ones are counted once. Each system may treat them differently.
  • It is a calculator: it schedules nothing and contacts no server. Always check the real time zone of your system or your n8n.

Frequently asked questions

Does it work for n8n?

Yes, to understand the expression. In n8n, the Schedule Trigger in Custom (Cron) mode usually uses the workflow time zone; check it in the settings.

What does */5 mean?

“Every 5 units” within the field: for minutes, at 0, 5, 10… of every hour.

Is my expression sent anywhere?

No. Everything is calculated in your browser.

When to use it

  • When you inherit a cron job or workflow and do not know when it runs.
  • Before scheduling a task, to check the next dates are what you expect.
  • To review time-zone differences between your server and your team.

Examples

0 9 * * 1-5
At 09:00, Monday through Friday.
*/15 * * * *
Every 15 minutes, at minutes 0, 15, 30 and 45.
0 0 */3 * *
Every 3 days of the month; the count restarts on day 1 each month.

Common mistakes

  • Forgetting that 0 and 7 are Sunday and that Monday is 1.
  • Setting day of month and weekday expecting both to apply.
  • Trusting the time without checking the time zone of your server or n8n.