Skip to content

Cron Expression Explainer

No pressure and no sales script. Just honest answers.

Prefer Saad Raza SEO on Google Add this site as a preferred source and Google will show more of my SEO and AI search guides when you search.

Add saadrazaseo.com as a preferred source on Google
Free tool

Runs in your browser. Nothing you enter is uploaded or stored.

Loading the tool...

To understand a cron schedule, paste the expression into the free Cron Expression Explainer above and press Explain. It checks the five fields, tells you in plain English when the job runs, shows each field’s values and lists the next ten run times in UTC or your own time zone. It understands ranges, lists, steps, month and day names and macros such as @daily, and it flags errors like a minute of 61 or a missing field. Paste up to 200 expressions to check a whole crontab at once.

Last updated: 11 November 2026. Written by Saad Raza.

Key takeaways

  • A cron expression has five fields, separated by spaces: minute, hour, day of month, month and day of week. A job runs when all five match.
  • An asterisk means every value, a comma makes a list, a hyphen makes a range, and a slash makes a step. For example, */15 in the minute field means every 15 minutes.
  • When both day of month and day of week are restricted, standard cron runs the job when either one matches. This surprises many people.
  • Cron uses the time zone of the server, and many servers use UTC. Daylight saving changes can cause a local-time job to skip or run twice.
  • This tool reads the standard five-field format. Quartz and Spring expressions, which add a seconds field, are reported as unsupported rather than guessed at.
  • It runs in your browser. Your schedules are not uploaded.

Why cron matters for websites and SEO

Many routine jobs on a website run on a schedule: backups, cache purges, sitemap generation, feed updates, scheduled posts, database clean-ups, uptime and link checks, and report exports. WordPress itself uses a scheduler, and hosting panels let you add cron jobs for tasks that should run at set times. A schedule that is wrong can run too often and slow the site, or never run and leave you with a stale sitemap, an old feed or a missing backup.

Cron syntax is compact, which makes it easy to write a line that looks right and does something else. A tester that explains the schedule in words and lists the real next run times is a cheap way to be sure.

How to use the Cron Expression Explainer

  1. Paste one or more cron expressions, one per line. Do not include the command, only the five time fields or a macro.
  2. Choose whether to show the next runs in UTC or in your browser’s time zone.
  3. Press Explain. For one expression you see the meaning, a field-by-field table and the next ten runs. For several, you see a table with the meaning and the next three runs of each.
  4. Fix anything marked invalid. The message names the field and the problem.

The five fields

FieldAllowed valuesNotes
Minute0 to 59*/15 is every 15 minutes
Hour0 to 230 is midnight
Day of month1 to 31Months without day 31 skip it
Month1 to 12 or JAN to DECNames are not case sensitive
Day of week0 to 7 or SUN to SAT0 and 7 are both Sunday

The special characters work like this. An asterisk matches every value. A comma separates a list, as in 9,17. A hyphen is a range, as in 1-5. A slash is a step, as in */10 for every tenth value or 0-30/10 for every tenth value from 0 to 30. The macros @hourly, @daily, @midnight, @weekly, @monthly, @yearly and @annually are accepted and expanded to their five-field forms.

A worked example

The example has eight lines. The expression */15 * * * * reads as every 15 minutes. 30 9 * * 1-5 reads as at 09:30, on Monday through Friday, which suits a weekday morning report. 0 0 1 * * is at 00:00 on day 1 of the month, a monthly job. 0 2 * * sun is at 02:00 on Sunday, a typical weekly backup slot.

0 9,17 * jan,jul mon-fri reads as at 09:00 and 17:00, on Monday through Friday, in January and July. @daily expands to at 00:00 every day. The last two lines are deliberately wrong: 61 * * * * is reported as a minute field value outside 0 to 59, and * * * * as having 4 fields instead of 5. The summary shows 8 expressions, 6 valid and 2 invalid.

For the first expression, the tool lists the next three runs as quarter-hour marks from the current time, so a run at 23:45, then 00:00 and 00:15. It builds this list by checking each day in turn, so the times are exact rather than estimated.

The day-of-month and day-of-week trap

If you set both the day of month and the day of week, standard cron does not require both to match. It runs the job when either matches. So 0 9 13 * 5 does not mean Friday the 13th at 09:00. It runs at 09:00 on the 13th of every month and also at 09:00 on every Friday. If you only want one of them, leave the other as an asterisk. The explainer follows this rule when it lists the next runs, so the list shows what cron will really do. If you need an “and” rule, run the job daily and test the condition inside the script.

Common schedules

  • Every 5 minutes: */5 * * * *
  • Every hour on the hour: 0 * * * *
  • Every day at 03:30: 30 3 * * *
  • Weekdays at 08:00: 0 8 * * 1-5
  • Every Monday at 06:00: 0 6 * * 1
  • The first day of each month at midnight: 0 0 1 * *
  • Every two hours: 0 */2 * * *

Good practice for scheduled jobs

Spread heavy jobs across the day rather than starting them all on the hour, and run them when traffic is low. Know the server’s time zone and write it in a comment next to the job. Log the output so that you can tell when a job fails. Avoid schedules that overlap, since a job that takes longer than its interval can pile up. After you set a job, confirm the first real run. If it is a sitemap or feed job, check the result with the sitemap validator. If it purges a cache or changes redirects, check with the redirect checker.

When the job’s times appear as raw numbers in logs, decode them with the Unix timestamp converter. To test the pattern in a log line that records the job’s run, use the regex tester. If a scheduled task secretly slows your site, a technical SEO audit can find the cause.

Limits

The explainer reads standard five-field cron. It does not support the seconds field of Quartz and Spring, the special characters L, W, # and ? used in Quartz, the @reboot macro, or extra syntax from particular cron programs. A question mark is treated as an asterisk. The plain-English text is a summary and does not cover every unusual combination, so check the field table and the run times when the meaning matters. The next runs are calculated for the next several years and are listed in UTC or in your browser’s time zone, which may not be the time zone of your server, and a job at a local time that does not exist or occurs twice on a daylight-saving changeover day may behave differently on a real server. The tool does not run, schedule or monitor anything. It handles up to 200 expressions per run. Everything is processed in your browser, and nothing is sent to a server.

Questions about the Cron Expression Explainer

What does * * * * * mean in cron?

Five asterisks mean every minute of every hour of every day. It is the most frequent schedule cron can express.

How do I run a job every 15 minutes?

Use */15 in the minute field and asterisks in the rest: */15 * * * *. It runs at minutes 0, 15, 30 and 45 of every hour.

Why did my job run on days I did not expect?

If both day of month and day of week are set, cron runs when either one matches. Leave one of them as an asterisk to avoid this.

What time zone does cron use?

The time zone of the server that runs it, which is often UTC. Check your hosting settings, and use UTC in the explainer if you are unsure.

Is my schedule uploaded?

No. The tool works in your browser, so your schedules stay on your device.

If you want help with scheduled tasks and site performance, see my SEO services or ask for a free audit. You can also browse the other free technical SEO tools.

Got your results? Let’s turn them into a plan

Tools show the issues. I will tell you which ones matter most and how to fix them.

Your details are only used to reply to your request. No spam.

Grow my trafficCall