Developer Tool · 100% Client-Side

Cron Expression Builder

Build and validate 5-field or seconds-aware 6-field cron expressions, preview timezone-correct previous and upcoming runs, and copy compatible scheduler snippets—all locally in your browser.

Visual Builder
Next Run Preview
Timezone Support
Presets Gallery
Raw Editor
100% Free
Live Expression

Human-readable

At 09:00 AM, Monday through Friday

Quick Presets

Minute

Values 0–59

Cron part

0
036912151821

Quick hour pick

09:00

Next Runs

Detecting timezone…

Calculating next runs…

Export snippets

Unix cron expression

0 9 * * 1-5

GitHub Actions

on: schedule: - cron: '0 9 * * 1-5' timezone: 'UTC'

Kubernetes CronJob fields

schedule: "0 9 * * 1-5" timeZone: "UTC"

Cron Field Reference

FieldRangeSpecialExample
Minute0–59* , - /*/15 = every 15 min
Hour0–23* , - /9 = 9 AM
Day of month1–31* , - /1 = first of month
Month1–12* , - /1,4,7,10 = quarterly
Day of week0–6 (Sun=0)* , - /1-5 = weekdays

100% client-side. Cron parsing and next-run calculations use open-source libraries in your browser. No expressions or schedules are uploaded.

What Is a Cron Expression?

A cron expression describes a recurring schedule with compact fields for minute, hour, day of month, month, and day of week. The standard five-field expression 0 9 * * 1-5 means 9:00 AM from Monday through Friday.

Some libraries add a leading seconds field, producing a six-field expression. That extension is useful in compatible application schedulers, but it is not interchangeable with POSIX crontab, GitHub Actions, or Kubernetes CronJob schedules.

How to Build a Cron Schedule

  1. Choose a preset or select each cron field in the visual builder.
  2. Pick the timezone used by the target scheduler and review the previous and next run times.
  3. Copy the generic expression or a compatible GitHub Actions or Kubernetes snippet.

Raw mode accepts expressions supported by the parser. Syncing to visual mode is intentionally limited to syntax the controls can preserve without changing its meaning.

Five Fields vs Six Fields

TargetFieldsTimezone
POSIX crontab5 schedule fieldsImplementation or system setting
GitHub Actions5 fieldsUTC by default; IANA timezone supported
Kubernetes CronJob5 fields.spec.timeZone
Compatible librariesOften 5 or 6Library-specific

Timezone and DST Behavior

Cron fields represent wall-clock time in the scheduler’s timezone. Selecting the correct IANA timezone matters because daylight-saving transitions can skip a local time or make it occur twice. The preview formats every run in the selected zone and also stores its unambiguous UTC ISO timestamp in the downloaded report.

If both day-of-month and day-of-week are restricted, traditional cron implementations commonly match when either field matches. For predictable schedules, restrict one of those fields and leave the other as * unless the target scheduler documents different semantics.

Related Scheduling and Developer Tools

Compare dates across regions with the Time Zone Converter, inspect epoch values with the Unix Timestamp Converter, format infrastructure configuration using the JSON Formatter, or test validation patterns with the Regex Tester.

Official Cron and Scheduler References

Frequently Asked Questions

Deployment note: Always verify the expression, timezone, minimum interval, daylight-saving behavior, and supported syntax in the documentation for the scheduler that will execute the job.