Skip to content

Cron expression explainer

Read cron expression in plain English and see its next run times.

*/15
Minute
9-17
Hour
*
Day (month)
*
Month
1-5
Day (week)

“Every 15 minutes during hour 9 through 17, on Monday through Friday.”

Cheat sheet
*
any value
,
a list: 1,15
-
a range: 1-5
/
a step: */10 every 10, 5-55/10
JAN–DEC, SUN–SAT
names work for months and weekdays; 0 and 7 are both Sunday
@daily …
@hourly, @daily, @weekly, @monthly and @yearly

If both day fields are set, cron runs when either matches. This is standard 5-field cron (Linux, GitHub Actions, Kubernetes). Quartz's 6- or 7-field format isn't supported.

Your files are open only in this tab. Nothing is uploaded.

Next runs

In your time zone (UTC). GitHub Actions and most servers use UTC.

  1. Mon, Nov 16, 2026, 09:00 AM in 16 hours
  2. Mon, Nov 16, 2026, 09:15 AM in 16 hours
  3. Mon, Nov 16, 2026, 09:30 AM in 16 hours
  4. Mon, Nov 16, 2026, 09:45 AM in 17 hours
  5. Mon, Nov 16, 2026, 10:00 AM in 17 hours
  6. Mon, Nov 16, 2026, 10:15 AM in 17 hours
  7. Mon, Nov 16, 2026, 10:30 AM in 17 hours
  8. Mon, Nov 16, 2026, 10:45 AM in 18 hours

How to use Cron expression explainer

  1. Enter a schedule. Type any 5-field expression or @macro into Cron expression, or click one of the eight preset pills.
  2. Verify the translation. Read the plain-English summary and inspect the five-column field breakdown below the input.
  3. Check upcoming runs. Review the Next runs panel for the next eight execution dates in your local time zone.
  4. Inspect edge cases. Open Cheat sheet to confirm operator rules for lists, ranges, steps, and dual day-field OR logic.

Everything runs in this browser tab. Nothing you paste or open is uploaded or logged, so it's safe for keys, tokens and private data.

Standard 5-field cron syntax and Vixie macros

Every standard crontab line uses five space-separated fields in strict order: minute, hour, day of the month, month, and day of the week. Typing */15 9-17 * * 1-5 into Cron expression displays each token directly above its field name and translates the schedule into plain English immediately.

Field order, allowed ranges, and named months or weekdays

Minute values span 0 through 59 and hour values span 0 through 23 on a 24-hour clock. Day of the month accepts 1 through 31, month accepts 1 through 12 or three-letter names JAN through DEC, and day of the week accepts 0 through 7 or SUN through SAT where both 0 and 7 represent Sunday.

Field Allowed values Wildcards & operators Example
Minute 0–59 *, ,, -, / */15 (every 15 min)
Hour 0–23 *, ,, -, / 9-17 (9 AM to 5 PM)
Day (month) 1–31 *, ?, ,, -, / 1,15 (1st and 15th)
Month 1–12 or JAN–DEC *, ,, -, / JAN-MAR (Q1)
Day (week) 0–7 or SUN–SAT *, ?, ,, -, / 1-5 (Mon through Fri)

If you are building log parsers or validation rules alongside your scheduled jobs, test matching strings with the JavaScript regex pattern tester in another tab.

Vixie cron macros and the POSIX crontab standard

The parser follows the POSIX.1-2017 crontab Utility Specification for numeric fields and also expands seven Vixie cron shorthand macros: @yearly, @annually, @monthly, @weekly, @daily, @midnight, and @hourly. Entering @daily expands internally to 0 0 * * *, while @reboot displays a clear notice explaining that startup triggers have no recurring calendar schedule.

Cron schedule next run times and UTC time zones

Reading a schedule in plain English catches syntax mistakes, yet seeing concrete calendar dates prevents off-by-one-hour bugs across time zones and daylight saving transitions. The Next runs card calculates the next 8 execution timestamps and refreshes every 30 seconds as the clock advances.

Previewing eight upcoming runs in your local time zone

Each entry in Next runs formats the weekday, date, hour, and minute in your browser’s active IANA time zone alongside a relative countdown such as in 12 minutes. When an expression targets an impossible calendar date such as 0 0 30 2 * for February 30, the panel reports that the job never runs instead of hanging.

To align server logs or Unix epoch fields with those scheduled timestamps, convert UTC epoch timestamps to local time directly in your browser.

GitHub Actions and Kubernetes CronJob UTC offsets

GitHub Actions workflow schedule triggers and default Kubernetes CronJob Schedule Documentation controllers evaluate expressions in UTC unless a cluster timeZone field is explicitly configured. Because Next runs renders in your local device time zone, subtract or add your UTC offset before deploying 0 9 * * 1-5 to a cloud pipeline.

Six-field Quartz expressions that prepend seconds or append a year fail validation intentionally with an explicit field-count error so you never deploy an incompatible string to a 5-field runner.

How does cron day-of-month and day-of-week OR logic work?

When both the third field (day of the month) and fifth field (day of the week) are restricted rather than left as *, standard cron combines them with OR logic rather than AND logic. A schedule such as 0 0 15 * 5 runs on the 15th of every month and also on every Friday, not solely on Fridays that land on the 15th.

Why restricting both day fields runs more often than expected

As documented in the Linux crontab(5) Manual Page, day-of-month and day-of-week are unioned whenever neither field is a wildcard. Leaving one of the two day fields as * avoids accidental extra runs, and any combined condition such as “first Monday of the month” should be checked inside the executed script.

Tip: Never write */0 or backwards numeric ranges like 17-9; the parser catches zero steps and inverted ranges immediately before they fail silently in production crontabs.

Step values in the cron minute field and boundary resets

Step expressions such as */15 in the minute field reset at the top of every hour, firing at minutes 0, 15, 30, and 45 rather than counting 15 min from when the daemon started. Similarly, */7 in the minute field fires at 0, 7, 14, 21, 28, 35, 42, 49, and 56, followed by a shorter 4 min gap to 00 of the next hour.

When documenting a deployment runbook or team wiki, you can export crontab and workflow snippets as PNG cards for clear visual reference.

Verifying schedules with presets before production deploy

Eight clickable preset pills sit directly under the plain-English readout: Every minute, Every 5 minutes, Hourly, Daily at midnight, Weekdays 09:30, Weekly (Sunday), Monthly, and Yearly. Clicking any pill populates Cron expression with a known-good baseline that you can adjust one field at a time.

Expanding Cheat sheet reveals a compact reference for *, ,, -, /, JAN-DEC, SUN-SAT, and @daily macros without leaving the workspace. Testing edge cases such as 30 9 * * 1-5 or 0 0 29 2 * before committing helps confirm whether a schedule runs every weekday or only once every four leap years.

Before editing a live production crontab file or CI YAML trigger, compare your old and updated configuration lines side by side with Text diff so accidental field shifts stand out immediately. Every expression is parsed locally in JavaScript with zero server requests, keeping internal deployment schedules private.

Questions

Which cron format does this explainer support?

It parses standard 5-field cron expressions used by Linux crontab, GitHub Actions, and Kubernetes CronJobs. Six-field Quartz expressions with a leading seconds field or trailing year field are rejected with an explicit message.

What happens if both day of month and day of week are set?

Standard cron uses OR logic when both day fields are restricted, so the job fires whenever either the day of the month or the day of the week matches. To target only Fridays that fall on the 13th, filter inside the script itself.

Are 0 and 7 both Sunday in crontab syntax?

Yes. Both 0 and 7 map to Sunday in the day-of-week field, and ranges such as MON-SUN or 1-0 are normalized cleanly so Sunday sits at the end of a Monday-to-Sunday span.

Why did my GitHub Actions schedule fire at an unexpected hour?

GitHub Actions and most cloud runners evaluate cron schedules in UTC rather than your local time zone. Check the UTC offset against your browser time zone shown in the Next runs panel before committing.

Does a step interval like */15 run continuously across hours?

No. Step values reset at the start of each parent unit, so */15 in the minute field fires at minutes 0, 15, 30, and 45 of every hour rather than drifting across hour boundaries.

Why does @reboot show no upcoming schedule?

The @reboot macro runs once at system startup rather than on a recurring calendar interval. Because boot events depend on machine restarts, there are no fixed future timestamps to calculate.

Updated