About this tool
This editor builds and validates standard five-field Unix cron expressions, explains each field in plain language and previews the next five run times in UTC. Developers and system administrators use it to check schedules before adding them to crontab, CI pipelines or job schedulers. A cron expression is a string of five fields, minute, hour, day of month, month and day of week, that defines when a recurring job runs.
How it works
Edit the expression directly, select a preset or change the five individual fields: minute (0–59), hour (0–23), day of month (1–31), month (1–12) and day of week (0–7). Commas list values, hyphens define inclusive ranges and slashes set steps, so 1-5 means Monday to Friday and */10 means every tenth value. Names JAN–DEC and SUN–SAT are accepted.
Supported aliases include @hourly, @daily, @midnight, @weekly, @monthly, @yearly and @annually. As you edit, the tool explains the schedule in words, flags invalid fields and lists the next five run times in UTC. Copy the expression once the preview matches what you expect.
Example
The expression 0 9 * * 1-5 runs at 09:00 UTC each Monday through Friday. The expression */15 * * * * runs at minutes 0, 15, 30 and 45 of every hour.
Steps can also apply to a range. With 0 8-18/2 * * 1-5, a job runs on the hour at 08:00, 10:00, 12:00, 14:00, 16:00 and 18:00 on weekdays. A weekly backup at 02:30 every Sunday is 30 2 * * 0, and you could write the weekday as SUN or 7 with the same result.
Assumptions and limits
Only the five-field Unix syntax and the listed @ aliases are supported; seconds and year fields, Quartz characters such as L, W, # and ?, and @reboot are rejected. Previews use UTC, not your server's time zone or daylight-saving rules. Some schedulers differ in dialect, so confirm against your platform's documentation.
Frequently asked questions
How do the two day fields interact?
In Unix cron, restricted day-of-month and weekday fields use OR. For example, 0 9 1 * MON matches the first of the month and Mondays. If either day field begins with *, including */2, both day rules must match.
Does this support Quartz or local daylight-saving time?
No. This is a five-field Unix cron editor with UTC previews. Six- or seven-field formats, special Quartz day syntax and @reboot are rejected. Check your scheduler's timezone and dialect before using the expression.
How do I run a cron job every 5 minutes?
Use */5 * * * *. The step value in the minute field matches minutes 0, 5, 10 and so on through 55 of every hour, which is 12 runs per hour. To limit it to working hours, restrict the hour field as well, for example */5 9-17 * * *.
Is Sunday 0 or 7 in cron?
Both. The day-of-week field accepts 0 through 7, where 0 and 7 both mean Sunday, and the names SUN through SAT are also accepted. Using names makes an expression easier to read later, for example MON-FRI instead of 1-5.
How do I run a job at midnight on the first day of every month?
Use 0 0 1 * *, or the equivalent alias @monthly. Both run at 00:00 on day 1 of each month. Remember that this tool previews in UTC, so if your server runs on local time the job fires at local midnight instead.
Link with your values
Add these parameters to this page’s address to open it with the values filled in, for example to share a calculation or to link to it from an AI assistant. The result is calculated in the browser: the page HTML shows an example for the default values, and the tool sets the data-url-params attribute once the link’s values are applied.
| Parameter | Value | If omitted |
|---|---|---|
expressionCron expression | text in the tool's notation, see the examples | required |
Examples
?expression=0+9+*+*+1-5?expression=@monthly?expression=30%202%201,15%20*%20*
Write decimals with a point. Encode a space as %20, + as %2B, # as %23 and & as %26.
Result elements: [data-result-block="cron"]