Cron Builder: Build or Decode a Cron Expression and See Exactly When It Runs

Key Takeaways
- Paste a 5-field cron expression, a 6-field expression with seconds, or a macro such as
@dailyto load it into the form, or start from a preset. The Simple tab sets common schedules with day chips and a time picker, and the Advanced tab gives you every field. - Every change updates the expression, a plain-English explanation, warnings and tips, and the next 10 run times in any time zone, with DST handled.
- Copy ready-to-paste lines for crontab, GitHub Actions, a Kubernetes CronJob, and a real server cron for WordPress.
- The builder catches the mistakes that make a job run at the wrong time or never run: both day fields set, uneven steps, missing month days, impossible dates, backwards ranges, and Quartz-only syntax.
- If an AI assistant wrote the cron line for you, paste it here and read the explanation and the next runs before you deploy it.
Cron decides when your scheduled jobs run: backups, report exports, feed imports, cache warmers, email digests, and the sync jobs that keep your marketing stack in step. Five short fields control all of it, and a single misplaced asterisk can turn a monthly job into one that runs every Monday, or into one that never runs at all.
The builder below works in both directions. Paste an existing cron expression to load it into the form, or start with a preset and adjust each field. You get the expression, a plain-English explanation, the next 10 run times in any time zone, and ready-to-paste lines for crontab, GitHub Actions, Kubernetes, and WordPress.
Cron Builder v1.1.1Last Update: Nov 20, 2026
Paste a cron expression to load it into the form, or start with a preset and adjust each field. The expression, its meaning and the next run times update as you go.
How to Use the Cron Builder
There are two ways in. If you already have a schedule, paste it. If you are starting from scratch, pick a preset or set the schedule on the Simple or Advanced tab. Both tabs edit the same schedule, and the output below the form updates as you go, so you can watch the meaning and the run times change while you edit.
Paste an Expression
Paste a cron expression into the first field and it loads into the form automatically. You can also type one and press Enter or click Load. The builder accepts the standard 5 fields (minute, hour, day of month, month, day of week), 6 fields with seconds first, and the macros @yearly, @annually, @monthly, @weekly, @daily, @midnight, @hourly, and @reboot. Month and day names such as JAN and MON-FRI work in any case.
If the expression uses something the Simple tab cannot show, such as */15 9-17 * * MON-FRI with its hour range, the builder switches to the Advanced tab and tells you why. Paste only the schedule. If you copy a whole crontab line with the command attached, the builder tells you it found too many fields and asks for the schedule alone.
Start From a Preset
The preset menu covers the schedules most teams need: every minute, every 5, 15, or 30 minutes, every hour on the hour, every 15 minutes on weekdays from 9 to 5, and daily, weekday, weekly (Monday), monthly (the 1st), quarterly, or yearly at a time you choose. Set the time beside the menu first, then apply the preset. Change the time afterward and a time-based preset updates with it. Choose Weekdays at, for example, and the day chips show Mon through Fri highlighted.
The weekday business-hours preset writes */15 9-16 * * 1-5, so the last run is at 4:45 PM. That is deliberate. If you write 9-17 in the hour field, the job keeps running every 15 minutes until 5:45 PM, because the hour field means every minute inside hour 17, not up to 5:00 PM.
Use the Simple Tab
The Simple tab is open by default and handles most schedules without any cron syntax. Start with How often:
- Every few minutes lets you choose an interval from every minute up to every 30 minutes.
- Hourly runs once an hour at the minute you pick, such as :15 past the hour.
- Daily runs every day at the time in Run at.
- Weekly, on chosen days runs at the Run at time on the days you select.
- Monthly, on chosen dates runs at the Run at time on the dates you pick from a 1 to 31 calendar-style grid, in the months you select.
Days of the week appear as Sun through Sat chips under On these days, so limiting an every-15-minutes job to weekdays is a matter of clicking Sun and Sat off. Monthly schedules add the date grid and 12 month chips, Jan through Dec, under In these months.
Use the Advanced Tab
The Advanced tab shows every cron field (second, minute, hour, day of month, month, and day of week), each with a mode menu:
- Every writes
*, so the field matches every value. - Every N, from a start writes a step such as
*/15, or10-59/15when you start somewhere other than the first value. - Specific values lets you pick values as chips, and the builder compresses them into a list such as
1-5,7,9. Days of the week are Sun through Sat chips, months are Jan through Dec chips, and days of the month are a 1 to 31 grid. - A range writes a start and end such as
9-17. - Custom text takes anything valid you type, for combinations the other modes do not cover.
When the schedule runs at one time of day, the minute and hour fields collapse into a single Run at time picker. Click Several Times or an Interval to bring back the minute and hour fields when you need a list of times, a step, or a range.
Turn on Include a seconds field when the schedule is for Quartz, Spring, node-cron, or another scheduler that puts seconds first. Leave it off for crontab, GitHub Actions, and Kubernetes, which accept 5 fields only.
Read the Output
Below the form you get four things:
- The expression. Click it or use the copy button.
- A plain-English explanation.
*/15 9-17 * * 1-5reads as Every 15 minutes, from 9:00 AM through 5:45 PM, on Monday through Friday. - Warnings and tips. These cover how cron will actually read what you wrote, and where other schedulers disagree.
- The next 10 runs. A numbered table lists each run’s date and time in the zone you select, plus how far away it is. The zone starts at your browser’s time zone, and you can switch to UTC or any IANA time zone.
Under the runs, the ready-to-paste section has a snippet for each platform with its own copy button and notes. Everything runs in your browser. Nothing you paste is sent to our server.
Cron Syntax: The Five Fields
A standard cron expression is five fields separated by spaces. The builder follows Vixie cron and cronie, the implementations behind most Linux crontabs, which GitHub Actions and Kubernetes also follow. The crontab(5) manual page is the reference if you want the full rules.
| Position | Field | Allowed Values | Names | Notes |
|---|---|---|---|---|
| 1 | Minute | 0 to 59 | None | The first field in standard cron. |
| 2 | Hour | 0 to 23 | None | 24-hour time. The next runs display 12-hour times. |
| 3 | Day of month | 1 to 31 | None | Months without the chosen day are skipped. |
| 4 | Month | 1 to 12 | JAN to DEC | Names work in any case. |
| 5 | Day of week | 0 to 7 | SUN to SAT | 0 and 7 both mean Sunday. |
| Optional first | Second | 0 to 59 | None | Only for 6-field schedulers like Quartz, Spring, and node-cron. |
Four operators do all the work:
| Operator | Meaning | Example | Reads As |
|---|---|---|---|
* | Every value | * * * * * | Every minute |
, | A list of values | 0 9,17 * * * | At 9:00 AM and 5:00 PM |
- | A range | 0 9 * * 1-5 | At 9:00 AM, Monday through Friday |
/ | A step | */15 * * * * | Every 15 minutes |
Common Cron Expression Examples
These are the schedules I see most often in marketing and web operations, with the explanation the builder gives for each.
| Expression | What It Means | Typical Use |
|---|---|---|
*/15 * * * * | Every 15 minutes | Pulling new leads or orders from an API |
0 * * * * | At minute 0 past every hour | Refreshing a product feed or sitemap |
30 2 * * * | At 2:30 AM, every day | Nightly backups (watch out for DST, below) |
0 9 * * 1-5 | At 9:00 AM, Monday through Friday | A daily sales or campaign report |
*/15 9-16 * * 1-5 | Every 15 minutes, 9:00 AM through 4:45 PM, weekdays | Syncing a CRM during business hours |
0 6 * * 1 | At 6:00 AM, on Monday | A weekly analytics digest |
0 0 1 * * | At 12:00 AM, on the 1st of the month | Monthly billing or usage exports |
0 9 1 1,4,7,10 * | At 9:00 AM on the 1st of January, April, July, and October | Quarterly reporting |
@reboot | Once each time the cron daemon starts | Restarting a worker after a server reboot |
Each macro is shorthand for a 5-field schedule: @yearly and @annually are 0 0 1 1 *, @monthly is 0 0 1 * *, @weekly is 0 0 * * 0, @daily and @midnight are 0 0 * * *, and @hourly is 0 * * * *. @reboot has no clock time at all, so the builder skips the run list for it.
Time Zones and Daylight Saving Time
Most scheduling surprises are time zone surprises. A cron expression has no time zone of its own. It runs in whatever zone the scheduler uses:
- Crontab uses the server’s time zone. Check it with
timedatectlordatebefore you assume. - GitHub Actions uses UTC unless the workflow sets
timezone:. - Kubernetes uses the kube-controller-manager’s zone unless the CronJob sets
timeZone.
That is why the run list lets you pick the zone. Pick the zone your scheduler actually uses, not the zone you live in, and the 10 runs show you exactly when the job fires.
Daylight saving time adds two edge cases. On the spring-forward night, times like 2:30 AM do not exist in zones such as America/New_York, and on the fall-back night, the 1:00 AM hour happens twice. The builder’s run list treats a skipped time as not running and runs a repeated hour once. Platforms handle the skipped hour differently: GitHub Actions moves it to the next valid time (a 2:30 AM run becomes 3:00 AM), and crontab behavior depends on the cron daemon. The simplest fix is to keep critical jobs out of the 1:00 AM to 3:00 AM window in any zone that observes DST, or to schedule them in UTC, which never shifts.
Ready-to-Paste Lines for Each Platform
The same expression has to be written a little differently for each platform. The builder generates all four from whatever is in the form, using the time zone you picked where the platform supports one. The samples below use 0 9 * * 1-5 in America/Indiana/Indianapolis, except the WordPress one, which uses every 15 minutes.
Crontab
0 9 * * 1-5 /path/to/command >> /var/log/my-job.log 2>&1 Replace /path/to/command with your command. Escape any % as \%, because crontab treats a bare percent sign as a newline. Crontab has no seconds field, so a 6-field expression gets a note instead of a line.
GitHub Actions
on:
schedule:
- cron: '0 9 * * 1-5'
timezone: "America/Indiana/Indianapolis" GitHub Actions schedules run in UTC by default. The builder adds the optional timezone: key only when you pick a zone other than UTC. GitHub does not accept macros, so @daily becomes 0 0 * * *, and day-of-week 7 is rewritten as 0. Per the GitHub Actions workflow syntax, the shortest interval is once every 5 minutes, scheduled runs can start late at busy times (especially at the top of the hour), and they run only from the default branch. The builder warns you when a schedule is more frequent than GitHub will honor. If you run CI/CD maintenance on a schedule, pick an odd minute like 17 instead of 0.
Kubernetes CronJob
apiVersion: batch/v1
kind: CronJob
metadata:
name: my-job
spec:
schedule: "0 9 * * 1-5"
timeZone: "America/Indiana/Indianapolis"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
containers:
- name: my-job
image: busybox:1.36
command: ["sh", "-c", "echo hello"]
restartPolicy: OnFailure The YAML sets timeZone, which the Kubernetes CronJob documentation lists as stable since version 1.27. On older clusters, or without the field, the schedule follows the controller manager’s zone. concurrencyPolicy: Forbid keeps a slow run from overlapping the next one. Swap in your own image and command. If you edit the file by hand, run it through our YAML validator before you apply it.
WordPress With a Real Server Cron
// wp-config.php: stop WP-Cron from running on page loads
define( 'DISABLE_WP_CRON', true );
# crontab: run due WordPress events on this schedule
*/15 * * * * curl -s "https://example.com/wp-cron.php?doing_wp_cron" > /dev/null 2>&1 WP-Cron does not read cron expressions. It checks for due events when someone loads a page, using intervals like hourly, twice daily, daily, and weekly. On a quiet site, that means scheduled posts and plugin jobs run late. On a busy site, it means extra work on page loads. The fix, documented in the WordPress Plugin Handbook, is to set DISABLE_WP_CRON in wp-config.php and have the server call wp-cron.php on a real schedule. Every 5 or 15 minutes is typical. Replace example.com with your domain.
Cron Gotchas the Builder Catches
Cron syntax is short, and short syntax hides rules. These are the ones that cause real outages and missed sends, and the builder explains each one when it applies:
- Both day fields set means either one.
0 9 15 * 1runs on the 15th of every month and on every Monday, not on the 15th only when it is a Monday. Cron ORs the day-of-month and day-of-week fields when both are restricted. If a day field starts with*(including*/2), crontab treats it as unrestricted and requires both to match, but other schedulers may not, so the builder warns you. - Sunday is 0 or 7. Both work in crontab. The builder rewrites 7 as 0 for GitHub Actions and Kubernetes.
- A step from a start runs to the end.
20/15in the minute field means minutes 20, 35, and 50, not every 15 minutes starting at 20 forever. Some older crontabs read it as just minute 20, so the builder writes it as20-59/15to remove the doubt. - Uneven steps reset.
*/7in the minute field runs at 0, 7, 14, and so on through 56, then starts over at 0. The gap at the top of the hour is 4 minutes, not 7. Use a step that divides evenly into 60 (or 24 for hours) when the interval matters. - Short months are skipped. A job on the 31st runs in only seven months. Cron does not move it to the last day of a shorter month. A job on February 29 runs only in leap years.
- Impossible dates never run.
0 0 31 2 *asks for February 31. The builder flags it as a schedule that never runs instead of letting you deploy a job that silently does nothing. - Ranges cannot wrap around.
22-2in the hour field is backwards. Write22-23,0-2to cover 10 PM through 2 AM. - Quartz syntax is not cron.
L(last day),W(nearest weekday),#(nth weekday),?, and a seventh year field come from Quartz and Spring. Standard cron rejects them, and so does the builder, with a workaround. For the first Monday of the month, for example, run on days 1 to 7 and check the weekday in your script.
Why Cron Still Matters in a Marketing Stack
Plenty of SaaS platforms hide scheduling behind a calendar picker, but the moment you own any piece of the stack, cron shows up. Data warehouse loads, ETL jobs, feed generation, sitemap refreshes, log cleanup, report exports, and WordPress maintenance all run on it. Marketing operations and DevOps teams share these schedules, and a job that runs in UTC when everyone assumed Eastern time can send a morning email at 4:00 AM.
AI coding assistants have made it easy to generate a crontab line or a GitHub workflow in seconds. They are also confident when they are wrong about the day fields, step values, or time zones. Treat a generated schedule like any other generated code: paste it into the builder, read the explanation in plain English, check the next 10 runs in the zone your scheduler uses, and fix anything the warnings point out. It takes less than a minute, and it is a lot cheaper than finding out from a customer.
Frequently Asked Questions
What Is a Cron Expression?
A cron expression is a schedule written as five fields: minute, hour, day of month, month, and day of week. Crontab, GitHub Actions, Kubernetes, and many other schedulers read it to decide when a job runs. Some schedulers add a seconds field at the start, for six fields.
What Does */15 Mean in Cron?
It means every 15 units of that field, starting from the first value. In the minute field, */15 runs at minutes 0, 15, 30, and 45 of every hour.
Why Did My Job Run on the Wrong Days?
If both the day-of-month and day-of-week fields are restricted, cron runs when either one matches. 0 9 15 * 1 runs on the 15th and on every Monday. Paste the expression into the builder to see the explanation and the next 10 runs.
What Time Zone Does Cron Use?
It depends on the scheduler. Crontab uses the server time zone, GitHub Actions uses UTC unless the workflow sets timezone, and Kubernetes uses the controller manager time zone unless the CronJob sets timeZone (version 1.27 or later).
Can Cron Run Every 30 Seconds?
Standard cron cannot, because its smallest unit is the minute. Schedulers like Quartz, Spring, and node-cron accept a sixth seconds field, so */30 * * * * * runs every 30 seconds there. On the Advanced tab, turn on the seconds field to build one.
How Do I Run a Job on the Last Day of the Month?
Standard cron has no last-day option. The L in some examples is Quartz syntax. Schedule the job for days 28 through 31 and have your script exit unless tomorrow is the 1st.
Does GitHub Actions Support Cron Time Zones?
Yes. Add a timezone key with an IANA name, such as America/New_York, beside the cron line in on.schedule. Without it, schedules run in UTC. The shortest interval GitHub allows is every 5 minutes.
Should I Disable WP-Cron in WordPress?
On most production sites, yes, as long as you replace it. Set DISABLE_WP_CRON to true in wp-config.php and add a server cron that calls wp-cron.php every 5 or 15 minutes, so scheduled posts and plugin jobs run on time without slowing page loads.







