Cron expression generator
Type a cron expression to have it explained in plain English, with the next times it will run.
Next runs (your time zone)
This free crontab helper works in your browser. All inputs and calculations run locally on your device without server uploads; details on browser processing and storage are set out in the privacy policy.
The five fields
| Field | Allowed | Example |
|---|---|---|
| Minute | 0–59 | 30 |
| Hour | 0–23 | 9-17 |
| Day of month | 1–31 | 1,15 |
| Month | 1–12 or JAN–DEC | */3 |
| Day of week | 0–7 or SUN–SAT (0 and 7 are Sunday) | MON-FRI |
Symbols
| Symbol | Means |
|---|---|
* | Every value |
, | A list: 1,15 |
- | A range: 9-17 |
/ | A step: */10 is every 10th |
@daily etc. | Shortcuts: @yearly, @monthly, @weekly, @daily, @hourly |
When both day of month and day of week are restricted, standard cron runs when either matches. That surprises many people, and the next-runs list shows its effect.
Time zones
Cron runs in the server’s time zone, which is often UTC. The next runs above are shown in your own time zone, as if the server were set to it. Cloud schedulers such as GitHub Actions and AWS EventBridge use UTC.
Worked example: Reading and building a weekday schedule (`15 9,17 * * 1-5`)
Suppose you want a backup or report script to run at 9:15 AM and 5:15 PM every Monday through Friday:
- Field 1 — Minute (
0–59):15(at 15 minutes past the hour). - Field 2 — Hour (
0–23):9,17(at 09:00 and 17:00 in 24-hour time). - Field 3 — Day of month (
1–31):*(every day of the month). - Field 4 — Month (
1–12):*(every month of the year). - Field 5 — Day of week (
0–6, Sunday=0):1-5(Monday through Friday).
Complete expression: 15 9,17 * * 1-5. If evaluated on Friday 14 November 2026 at 11:10, the next five scheduled runs are Fri 14 Nov 17:15, Mon 17 Nov 09:15, Mon 17 Nov 17:15, Tue 18 Nov 09:15, and Tue 18 Nov 17:15.
Limits and what this tool cannot do
- Standard 5-field POSIX/Vixie cron syntax only: This tool uses the classic 5-field Unix crontab format (
min hour dom month dow). It does not parse 6-field or 7-field Quartz/AWS EventBridge expressions that add a leading Seconds field or a trailing Year field, nor non-standard characters likeL(last day of month),W(nearest weekday), or#(5#3for third Friday). - The Day-of-Month + Day-of-Week 'OR' trap: In standard Unix cron, if *both* Field 3 (Day of Month) and Field 5 (Day of Week) are set to something other than
*(for example0 9 13 * 5, hoping for 'Friday the 13th'), Vixie cron treats them as a boolean **OR**—running on the 13th of every month *and* on every Friday! - Step values (
*/13) reset at the end of each hour/day:*/13in the minute field runs at:00, :13, :26, :39, :52and then fires again 8 minutes later at:00of the next hour.
Questions
Does it support seconds?
No. Standard cron has five fields. Quartz and some schedulers add a sixth field for seconds, which is not supported here.
How do I run a job every 2 hours?
Use 0 */2 * * *.
How do I run on the last day of the month?
Standard cron cannot say “last day”. Run on days 28–31 and check the date in your script, or use a scheduler that supports L.
How do I run a cron job every 5 minutes?
Enter */5 * * * *. That runs at minutes 0, 5, 10, 15, ..., 55 of every hour, every day.
Does 0 or 7 stand for Sunday in the Day-of-Week field?
In standard POSIX cron, 0 is Sunday and 1 through 6 are Monday through Saturday (many Linux Vixie cron implementations also accept 7 as Sunday, but 0 is portable across all Unix systems).
How do I express 'every 2 hours between 8 AM and 6 PM'?
Combine a range and a step in the Hour field: 0 8-18/2 * * *, which runs at 08:00, 10:00, 12:00, 14:00, 16:00, and 18:00.