Free cron tools

The Complete Cron Expression Toolkit

Build a schedule, check it, and get output for the platform you deploy to: Linux, Kubernetes, GitHub Actions, AWS EventBridge, Vercel or Quartz.

Open the Generator Parse an expression
  • Runs in your browser
  • No account
  • Next runs in your time zone

Shortcuts: Alt+G Generator, Alt+P Parser, Alt+A Assistant

Try itReads Linux, AWS, Quartz, Kubernetes, GitHub and Vercel syntax
Tools

Six tools, one engine

Each tool has its own page. They share one cron engine, so a schedule reads the same everywhere.

Cron Expression Generator
Build a schedule from options or plain English, with output for each platform.
Open →
Cron Expression Parser
See every field resolved, the next runs and a weekly heatmap.
Open →
Cron Expression Validator
Check one expression against six platforms and see why it fails.
Open →
Cron Explainer
A plain-English sentence and field breakdown for reviews and runbooks.
Open →
Human Readable Cron
Translate cron into everyday language and browse common schedules.
Open →
Cron Examples
Copy common schedules or open them in the Generator.
Open →
Platforms

Output that follows each platform's rules

Cron is not one syntax. CronWave knows where these six differ and writes your schedule accordingly.

Linux / Unix
Five-field crontab. When both day fields are set, either one matches.
AWS EventBridge
Six fields with a year. ? is required in one day field. Rules run in UTC.
Kubernetes
CronJob spec.schedule with optional spec.timeZone.
GitHub Actions
schedule.cron in workflow YAML. UTC by default, five-minute minimum.
Vercel
Cron jobs in vercel.json. UTC, no day names, one day field at a time.
Quartz
Seconds first, six or seven fields, with ? L W #.
Learn

Cron basics, in plain language

Start with what a cron expression is, then the syntax and the special characters. Each guide has a live example.

What is a cron expression?The plain definition, how to read one, and examples.Crontab syntaxThe five fields, operators, names, macros and the day-field rule.Cron special characters*, comma, hyphen, slash, ?, L, W and #, and where each works.Cron timezone converterConvert a schedule between your time zone and UTC.
Schedules

The schedules people look up most

Every 5 minutes, hourly, daily, weekdays and monthly, with variants, platform limits and the mistakes to avoid. More are in the cron examples.

Cron every 5 minutes*/5 and its variants, platform limits, overlapping runs.Cron every hourHourly and every 2, 4, 6, 12 hours, plus the common hourly mistake.Cron every dayDaily at a set time, twice and three times a day, DST advice.Cron every weekday1-5, every Sunday and Monday, numbering by platform, the OR trap.Cron first day of month0 0 1 * *, the 15th, the last day, quarterly runs.
What you get

Details that save a debugging session

  • Plain-English output
    Every expression comes with a sentence you can paste into a review.
  • Next runs in your time zone
    Pick the zone; UTC platforms are converted and DST changes are flagged.
  • Weekly heatmap
    A 7 × 24 grid of when a schedule fires, in the Parser.
  • Platform checks
    See which of six platforms accept an expression and why the others do not.
  • Runs in your browser
    Parsing, validation and the Assistant run locally. Nothing you type is sent to CronWave.
  • Keyboard friendly
    Alt+G, Alt+P and others jump between tools. Alt+A opens the Assistant.
Field reference

Standard cron: five fields

The common core used by Linux and other Unix cron daemons. Order: minute, hour, day of month, month, day of week.

FieldAllowed valuesSpecial charactersExample
Minute0-59* , - /*/15 every 15 minutes
Hour0-23* , - /9-17 9:00 to 17:59
Day of month1-31* , - /1,15 the 1st and 15th
Month1-12 or JAN-DEC* , - /1,4,7,10 each quarter
Day of week0-6 (0 = Sunday; 7 also Sunday on many systems) or SUN-SAT* , - /1-5 Monday to Friday

These five fields are the common core, as used by Linux and other Unix cron daemons. Names and some details depend on the implementation.

Where platforms differ

Other schedulers add fields or symbols, or restrict what is allowed. These are extensions of the standard form, not part of it.

PlatformFieldsWeekdaysExtra symbolsTime zone
Linux / Unix50-7 or namesnone (plus @daily-style macros)The system's
Kubernetes CronJob50-6 or names? accepted like *; macrosController's, or spec.timeZone
GitHub Actions50-6 or namesnoneUTC by default (optional timezone key); shortest interval 5 minutes
Vercel50-6, no namesnone; cannot restrict day-of-month and day-of-week togetherUTC
AWS EventBridge6, ending with a year1-7 (1 = Sunday) or names? required in one day field; L W #UTC for rules
Quartz6 or 7, starting with seconds1-7 (1 = Sunday) or names? required in one day field; L W #The scheduler's, or per trigger

The question mark and the L, W and # symbols are extensions, not part of standard five-field cron. Details can differ between versions, so check the documentation of the platform you deploy to.

FAQ

Questions

CronWave is a set of browser-based tools for working with cron schedules: a generator, parser, validator, explainer, a plain-language schedule lookup and a library of examples. All of them use one shared cron engine, so they agree with each other.
No. Parsing, validation, next-run calculation and the Assistant all run as JavaScript in your browser. When you move an expression from one tool to another it travels in the part of the URL after the #, which browsers do not send to servers. As with any website, the host may keep ordinary access logs of which pages were requested. See the privacy page for details.
Linux and Unix five-field cron, Kubernetes CronJob schedules, GitHub Actions, AWS EventBridge (six fields, including a year), Vercel cron jobs and Quartz (seconds first). The validator shows how one expression is read on each of them.
You choose it. The default is your browser's time zone. GitHub Actions (by default), Vercel and EventBridge rules run in UTC, so for those CronWave converts your local time to UTC and warns you when daylight saving time will move the local run time.
No. It is a rules-based helper that runs locally. It recognises a fixed set of requests, answers them with the same engine as the tools, and says so when it cannot help. It does not call any model or server. More about the Assistant.
Standard five-field cron has no question mark. AWS EventBridge and Quartz use ? to mean "no specific value" and require it in either the day-of-month or the day-of-week field. Kubernetes accepts it as another way of writing *.