Cron Expression Builder
Build a cron expression field by field or decode one into plain English, with each field checked, the next run times in your time zone, and every field expanded into the values it matches.
How to Use
- Choose Decode to paste an expression (or a whole crontab line with its command), or Build to fill in the five fields one at a time.
- Each field is checked as you type: it shows the values it matches, or says what is wrong — minute 61, a range that runs backwards, or Quartz-only syntax such as
Lor#. - Read the plain-English description and the next run times. They are in your local time zone; switch to UTC to see what a server running on UTC will do.
- Start from a preset such as @hourly, Weekdays 09:00 or Every 15 min, then adjust it.
- Press Copy line for the crontab line, and read Show Work to see each field expanded into its values and the day rule applied.
Worked Example
Run a report at 9 in the morning on weekdays: 0 9 * * 1-5.
Minute 0 = {0}. Hour 9 = {9}. Day of month * = every day. Month * = every month. Day of week 1-5 = {1, 2, 3, 4, 5} = Monday to Friday.
Runs on each matching day: 1 hour × 1 minute = 1. Weekdays in the year from Saturday 3 October 2026: 260, so 260 runs.
If it is Saturday 3 October 2026 at 10:15, the next runs are Monday 5 October at 09:00, Tuesday 6 October at 09:00 and Wednesday 7 October at 09:00.
The common mistake: writing * 9 * * 1-5. The hour is right, but the minute field is *, which means every minute from 0 to 59. The job runs at 09:00, 09:01, 09:02 … 09:59: 60 × 1 = 60 runs a weekday, 300 a week and 15,600 a year instead of 260. Always set the minute when you mean a single time.
Every 15 minutes in office hours: */15 9-17 * * 1-5. Minute */15 = start at 0 and add 15 = {0, 15, 30, 45}. Hour 9-17 = {9 … 17}, 9 values. Runs per weekday: 9 × 4 = 36, the first at 09:00 and the last at 17:45 (not 18:00 — hour 18 is not in the range).
Show Work
Cron Syntax
Where Cron Came From
The name comes from the Greek chronos, time. The cron in Version 7 Unix (1979) was a simple loop: once a minute it read the system table in /usr/lib/crontab, ran any line whose five fields matched the current time, and went back to sleep. Later Unix versions gave every user their own crontab, edited with the crontab command.
Paul Vixie’s rewrite of 1987, Vixie cron, became the cron of most Linux and BSD systems, and Red Hat’s cronie, forked from it in 2007, is still the default on Fedora and RHEL. The @-macros such as @daily and @reboot come from that line. POSIX standardised the five fields, lists and ranges, and the rule that a day matching either day field is enough.
The same five fields now schedule Kubernetes CronJobs and GitHub Actions workflows. Java’s Quartz scheduler and Spring added a seconds field and the ?, L, W and # characters, which is why expressions copied from Java projects often have six or seven fields and fail in a real crontab.
About This Tool
This tool reads and writes standard five-field cron expressions, the format used by crontab, cronie, Vixie cron, Kubernetes and GitHub Actions. Decode an expression, or a whole crontab line with its command, into plain English; or build one a field at a time with each field checked as you type.
The run times are worked out from the fields themselves, minute by matching minute, in your browser’s time zone or in UTC, and the day-of-month/day-of-week OR rule is applied the way cron applies it. It also catches what usually goes wrong: a * left in the minute field, an impossible date such as 30 February, ranges that run backwards, and Quartz syntax pasted into a crontab. Nothing is sent anywhere; it all runs on this page.
Related tools: Unix Timestamp Converter, Timezone Converter, and Regex Tester.
Frequently Asked Questions
What do the five cron fields mean?
In order: minute (0–59), hour (0–23), day of the month (1–31), month (1–12 or JAN–DEC) and day of the week (0–7 or SUN–SAT, where 0 and 7 are both Sunday). A * means every value. So 30 2 * * 0 runs at 02:30 every Sunday, and 0 0 1 * * runs at midnight on the 1st of each month.
Why does my job run 60 times at 9 o’clock?
Because the minute field is *. The expression * 9 * * 1-5 means “every minute of the 9 o’clock hour”, so it runs at 09:00, 09:01 … 09:59 — 60 times a weekday and 15,600 times a year. To run once at 09:00, set the minute too: 0 9 * * 1-5.
What happens when both day fields are set?
The job runs on days that match either field, not both. 0 0 1 * 1 runs on the 1st of every month and on every Monday: in the year from 3 October 2026 that is 62 days (12 firsts plus 52 Mondays, less the two Mondays that are also the 1st), not just the Mondays that fall on the 1st. If either day field starts with *, as in */2, both must match instead.
Which time zone does cron use?
The time zone of the machine running it, which on most cloud servers and containers is UTC. A job set to 0 9 * * * on a UTC server runs at 10:00 in London in summer and at 05:00 in New York while daylight saving time is in force. GitHub Actions schedules always run in UTC; cronie also lets you set CRON_TZ at the top of a crontab. Switch this page to UTC to check.
Can cron run every 30 seconds, or use six fields?
Standard cron has no seconds field, so a minute is the smallest step. The usual workaround is two lines: * * * * * job and * * * * * sleep 30; job. Six-field expressions with seconds first are Quartz and Spring syntax (Spring’s */30 * * * * * is every 30 seconds); paste one here and the tool offers the five-field version without the seconds.
How do I use the Cron Expression Builder?
Just pick your options. The answer shows up right away — there is no button to press. Change anything and it updates by itself.
Is it free? Does it work without internet?
Yes to both. It is free with no sign-up, and once the page has loaded it keeps working even with no internet.
Where does my data go?
Nowhere — every calculation runs on your own device. Nothing you enter is uploaded, logged, or stored.
Common Use Cases
Nightly backups
30 2 * * * runs at 02:30 every night, 365 times a year, when servers are quiet. Check the time zone first: on a UTC server that is 21:30 the evening before in New York (EST).
Business-hours health checks
*/15 9-17 * * 1-5 checks every 15 minutes from 09:00 to 17:45 on weekdays: 36 checks a day, 180 a week.
Monthly reports
0 6 1 * * builds the report at 06:00 on the 1st, 12 times a year. Cron has no “last day of the month”, so run on the 1st and report on the month before.
Kubernetes and CI schedules
Kubernetes CronJobs and GitHub Actions use the same five fields. GitHub runs them in UTC and no more often than every 5 minutes, so */5 * * * * is the fastest it accepts.
Debugging a job that never ran
Paste the crontab line: 0 0 30 2 * shows no run times at all, because February never has a 30th.
Last updated: