Fill in minute, hour, day, month and weekday (or pick a preset) to get a standard five-field cron expression with a plain-English summary. Runs in your browser.
Cron is the time-based job scheduler found on Linux, macOS and most Unix-like servers, and its five-field syntax has been borrowed by GitHub Actions, Kubernetes CronJobs, cPanel, many CI systems and countless libraries. The syntax is compact, which is why it is easy to get wrong: 0 2 * * 1 runs at 2:00 a.m. on Mondays, while 2 0 * * 1 runs at 12:02 a.m.
This tool lets you fill in the five fields (or start from a preset), joins them into one expression you can copy, and shows a plain-English summary to catch obvious mistakes. It runs entirely in your browser; nothing you type is sent to a server.
| Position | Field in the tool | Allowed values | Example |
|---|---|---|---|
| 1 | Minute | 0-59 | 30 = half past |
| 2 | Hour | 0-23 (24-hour clock) | 14 = 2 p.m. |
| 3 | Day | 1-31 (day of the month) | 1 = the 1st |
| 4 | Month | 1-12 | 12 = December |
| 5 | Weekday | 0-6, Sunday = 0 | 1-5 = Monday to Friday |
Inside any field you can use the operators defined for standard cron: * (every value), a list such as 1,15, a range such as 9-17, and a step such as */15 (every 15th value). The step syntax is a widely supported extension documented in the Linux crontab(5) manual; the base format is defined in the POSIX crontab specification.
*, so you only change the fields that matter. An empty box is treated as *.0 * * * *), Daily Midnight (0 0 * * *), Weekdays 9am (0 9 * * 1-5), Weekly Sunday (0 0 * * 0), Monthly 1st (0 0 1 * *), Every 5 Min, Every 15 Min and Yearly Jan 1 (0 0 1 1 *). A preset fills all five boxes and generates the result immediately.30 2 * * 1-5 /usr/local/bin/backup.sh in crontab -e, or inside the cron: key of a scheduler config.Say you want a database dump to run at 2:30 every morning, Monday to Friday, when traffic is lowest. Enter Minute 30, Hour 2, leave Day and Month as *, and set Weekday to 1-5. After you press Generate, the tool returns:
30 2 * * 1-5The summary means minute 30 of hour 2, i.e. 02:30. Saved on a Friday at 10:00, it next fires at:
| Run | Day | Time |
|---|---|---|
| 1 | Monday | 02:30 |
| 2 | Tuesday | 02:30 |
| 3 | Wednesday | 02:30 |
| 4 | Thursday | 02:30 |
| 5 | Friday | 02:30 |
Saturday and Sunday are skipped because 6 and 0 are outside the range 1-5. (Run times calculated with a standard cron parser.)
The Cron Expression box is the part that matters: it is exactly the five values you entered, joined by spaces. The Human Readable line is a quick sanity check written for simple patterns. It handles *, steps like */15, single numbers and a weekday range such as 1-5. For lists or ranges in other fields it repeats your value as typed (for example "on day 1,15"), and for a weekday list such as 1,3,5 it only names the first day, so with complex patterns trust the expression and the rules on this page over the summary.
The Next 5 Runs list counts forward one minute at a time from your current local clock. It is not calculated from the expression, so do not use it to confirm a schedule. To check real run times, compare with the tables on this page or use a dry run in your scheduler.
The most common cron accident: leaving the minute field as * while fixing the hour, which runs the job 60 times in that hour.
When both the Day and Weekday fields are restricted, standard cron runs the job when either matches. This is stated in the POSIX specification and the crontab(5) manual. 0 0 13 * 5 does not mean "Friday the 13th"; it means "every Friday and also every 13th". Calculated from a Friday the 13th, its next runs are Friday the 20th, Friday the 27th, Friday the 4th, Friday the 11th and then Sunday the 13th. For a true "both", schedule on one field and test the other inside the script.
0 9 1,15 * * runs at 09:00 on the 1st and 15th of every month. */20 9-17 * * 1-5 runs every 20 minutes from 09:00 to 17:40 on weekdays, because the hour range includes all of hour 17. Steps restart in each parent unit: */7 in the minute field fires at :00, :07 ... :56 and then again at :00, so the gap at the top of the hour is only 4 minutes.
Many implementations also accept 7 for Sunday, but this tool's summary only understands 0-6.
Classic cron uses the server's local time zone. GitHub Actions schedules always run in UTC and the shortest allowed interval is every 5 minutes (GitHub docs). Kubernetes CronJobs use the controller's zone unless you set spec.timeZone (Kubernetes docs). Jobs set between 1:00 and 3:00 a.m. can be skipped or run twice when clocks change for daylight saving, so use UTC or avoid that window for critical work. Our Time Zone Converter helps you translate a local time into UTC before you write the hour field.
This tool produces the standard five-field format. Quartz (Java, Spring) adds a seconds field and a ? placeholder, and AWS EventBridge adds a year field, so a five-field expression will be rejected or misread there. Nicknames such as @daily are not generated here.
If you write crontabs every week, typing the fields directly is fast and the man page is the final authority. A form helps when you touch cron occasionally or want to start from a preset and change one value. It does not validate ranges: the boxes accept any text, so 60 in the minute field is copied as is and your cron daemon will reject the line. After installing a job, check the system log (for example grep CRON /var/log/syslog on Debian and Ubuntu) to confirm the first run.