Skip to main content
GARGLOO

Cron Expression Generator – Build & Explain Cron

Build it, read it in plain English, see the next runs.

Runs on your device

At a glance

Input:
Five fields you pick, or an expression you paste
Processing:
Runs locally in your browser
Privacy:
Nothing you type is sent to a server

Last updated: 2026-11-10

Common use cases

  • Scheduling a backup every weekday at 09:00 without guessing the field order
  • Checking that "0 0 1 * 1" really means the 1st or Mondays before it runs too often
  • Reading a pasted crontab line in plain English before editing it
  • Finding the next February 29 run for a leap-day job

About this tool

Pick the five cron fields with buttons and chips, or paste an expression and watch the builder fill itself in. Every schedule gets a plain-English description and the next five run times in your browser's local timezone. Two traps are called out on the page: cron runs in your server's timezone, not yours, and day-of-month plus day-of-week means OR in standard cron, not AND. Standard 5-field crontab only — Quartz 6–7 fields are rejected with a named error. Nothing is uploaded.

How to use it

  1. Load a preset (every 15 minutes, weekdays at 09:00, monthly on the 1st) or set the five fields yourself.
  2. Read the plain-English description — it says OR out loud when both day fields are set.
  3. Check the next five run times, in your browser's timezone, against the schedule you meant.
  4. Copy the expression into your crontab — and check your server's timezone before you trust the hour.

Worked examples

Input: 0 9 * * 1-5

Output: At 09:00, from Monday to Friday. Next runs: Tue 2026-11-10 09:00, Wed 2026-11-11 09:00, Thu 2026-11-12 09:00.

From Monday 2026-11-09 12:00 local — the first three of the next five runs.

Input: 0 0 1 * 1

Output: At 00:00, on the 1st of the month or on Mondays — standard cron runs when EITHER matches, not both. Next runs: Mon 2026-11-16 00:00, Mon 2026-11-23 00:00, Mon 2026-11-30 00:00.

From Monday 2026-11-09 12:00 local — the first three runs are all Mondays; the 1st of December (a Tuesday) follows. That is the OR rule: the 1st and Mondays each trigger a run.

Input: 0 0 29 2 *

Output: At 00:00, on the 29th of the month, in February. February 29 only happens in leap years. Next run: Tue 2028-02-29 00:00.

From Monday 2026-11-09 12:00 local — the next February 29 is in the leap year 2028; there is no February 29 in 2027.

Practical tips

  • Start from a preset and change one field — it is faster than typing five fields from scratch.
  • Read the next five runs before you save a schedule — they catch a wrong field faster than the description does.
  • Use 1-5 for weekdays and 0,6 for weekends instead of listing days one by one.
  • When the hour matters, check the server's timezone first — a 09:00 job on a UTC server is not 09:00 in Casablanca.

Common mistakes

  • Setting day-of-month and day-of-week and expecting AND — standard cron runs on EITHER, so "0 0 1 * 1" fires on Mondays and on the 1st.
  • Pasting a Quartz expression with seconds — the first field is seconds there, so "0 0 0 * * *" would silently mean something else; this page rejects it instead.
  • Writing "* * * * *" for a daily job — that runs every minute, 1,440 times a day.
  • Scheduling February 30 or April 31 — those dates never come, so the job never runs.

How this compares

crontab.guru is the classic explainer: paste an expression, read it in plain English. This page is the builder around the same idea — pick the fields with buttons, load presets, and see the next five runs in your own timezone, with the two classic traps (server timezone, the OR rule) called out in words. The tradeoff: no seconds field and no Quartz, and the preview is in your browser's timezone, not your server's — crontab.guru has the same timezone caveat, so check the server either way.

Good to know

  • Standard 5-field crontab only — no seconds field, no Quartz, no L, W or #.
  • The next-run preview looks up to 5 years ahead (so February 29 is always found) and shows the first 5 runs.
  • Preview times are in your browser's local timezone — your server may use a different one.
  • Day-of-month and day-of-week together mean OR in standard cron — the description says so, but your scheduler follows the same rule.

Frequently asked questions

What timezone does cron use?

Your server's, not yours. A cron job runs on the machine that owns the crontab, in that machine's timezone. This page previews the next runs in your browser's local timezone and names it, so you can spot a mismatch — but always check your server's timezone setting before you trust the hour.

What happens when I set both day-of-month and day-of-week?

The job runs when EITHER matches — that is the standard (Vixie) cron rule, not AND. "0 0 1 * 1" runs on the 1st of the month or on Mondays, so it fires on three Mondays and then on the 1st of December, not only on a Monday that is the 1st. The plain-English description on this page says OR explicitly whenever both fields are set.

Does this support Quartz or seconds?

No — standard 5-field crontab only (minute hour day-of-month month day-of-week). A 6- or 7-field expression, where the first field is seconds, is rejected with a named error instead of being silently misread. Quartz extensions like L, W and # are rejected the same way.

What syntax can I use in a field?

* for every value, lists (1,15), ranges (1-5), steps (*/15, 2/5) and names (JAN–DEC, MON–SUN; 7 is Sunday too). February 30 and April 31 are rejected as impossible dates — February 29 is found in the next leap year instead.

Is my expression uploaded?

No. The builder, the plain-English description and the next-run preview all run in your browser — the expression never leaves this tab.

All developer tools
Cron Expression Generator – Build & Explain Cron | GARGLOO