The Cron Expression Generator is a developer tool designed to create, parse, and validate standard cron schedules. A cron expression is a string comprising five or six fields separated by white space that represents a set of times, normally as a schedule to execute a routine in Unix-like computer operating systems or application job schedulers.

Standard Cron Syntax

A standard cron expression consists of five required fields, evaluated from left to right:

Minute: 0-59
Hour: 0-23 (using 24-hour time)
Day of Month: 1-31
Month: 1-12 (or JAN-DEC)
Day of Week: 0-6 (where 0 is Sunday, or SUN-SAT)

Note: Some implementations (like AWS EventBridge or Quartz) include a 6th field for "Year" or a leading field for "Seconds," but the 5-field format is the universal POSIX standard.

Special Characters Explained

Cron uses specific operators to define complex schedules:

Asterisk (*): Represents "all values". Putting an asterisk in the Hour field means "every hour".
Comma (,): Used to separate items in a list. 1,15 in the Minute field means "at minute 1 and minute 15".
Hyphen (-): Defines a range. 9-17 in the Hour field means "every hour from 9 AM to 5 PM".
Slash (/): Defines step values (increments). */15 in the Minute field means "every 15 minutes". 0/2 in the Hour field means "every 2 hours, starting at midnight".

Common Cron Expression Examples

Every minute: * * * * *
Every 5 minutes: */5 * * * *
Every day at midnight: 0 0 * * *
Every day at 2:30 PM: 30 14 * * *
Every Monday at 9:00 AM: 0 9 * * 1
On the 1st and 15th of every month at midnight: 0 0 1,15 * *
Every weekday (Mon-Fri) at 8:00 AM: 0 8 * * 1-5

Parsing and Validation Logic

When you enter a human-readable schedule, the generator maps those inputs directly to the corresponding numeric or wildcard values. Conversely, when parsing an existing expression, the tool applies a reverse-mapping algorithm to translate the syntax back into plain English, ensuring you haven't accidentally scheduled a task to run 60 times an hour when you meant once an hour.

Frequently Asked Questions

What timezone does a cron expression use?

Cron expressions themselves do not contain timezone data; they are just raw strings. The timezone is determined by the environment executing the cron job. If you run a cron job on a Linux server, it uses the server's local system time (usually UTC in modern cloud environments). If you are using a cloud scheduler, you often have to specify the timezone explicitly in the configuration alongside the expression.

Why do some cron generators have 6 fields instead of 5?

The original Unix cron utility uses 5 fields. However, advanced job scheduling libraries (like Quartz for Java) or cloud services (like AWS CloudWatch Events) introduced a 6th (and sometimes 7th) field to support "Seconds" or "Years". You should verify which standard your specific runtime environment expects before deploying the expression.

Can I schedule a job for the "last Friday of the month"?

Standard 5-field POSIX cron does not support a "last Friday of the month" operator out of the box. You typically have to schedule it for every Friday and then add conditional logic to your actual script to check if it's the last Friday before executing. However, extended syntax (like Quartz) supports the L character, allowing expressions like * * * * 5L to achieve this.

Cron Expression Generator