HubTools

Cron Every 5 Minutes Generator

Pre-loaded with */5 * * * * — the canonical 'every 5 minutes' cron pattern.

What does cron `*/5 * * * *` mean?

*/5 * * * * fires at minute 0, 5, 10, 15, 20, ... 55 of every hour, every day — twelve times an hour, 288 times a day. The */5 in the minute field is step syntax: 'every 5 starting from 0'. It's the standard pattern for short-interval polling jobs: refreshing a cached API response, syncing data from a third-party SaaS, scraping a status endpoint, or processing a queue that doesn't justify a long-running worker.
Minute0-59, * for every, */5 for every 5 minutes
Hour0-23, * for every, */2 for every 2 hours
Day of Month1-31, * for every, 1,15 for specific days
Month1-12, * for every, 1-6 for Jan through Jun
Day of Week0-6 (0=Sunday), * for every, 1-5 for weekdays
Generated Expression

*/5 * * * *

Every 5 minutes
Next 5 Runs:
5/2/2026, 2:10:00 PM5/2/2026, 2:15:00 PM5/2/2026, 2:20:00 PM5/2/2026, 2:25:00 PM5/2/2026, 2:30:00 PM
Cron Reference
FieldRangeSpecialExample
Minute0-59* , - /*/5 = every 5 min
Hour0-23* , - /9-17 = 9 AM to 5 PM
Day of Month1-31* , - /1,15 = 1st and 15th
Month1-12* , - /1-6 = Jan to Jun
Day of Week0-6* , - /1-5 = Mon to Fri
Special Characters
* Any value
, Value list separator
- Range of values
/ Step values
Day of Week Values
0=Sun1=Mon2=Tue3=Wed4=Thu5=Fri6=Sat

About the */5 step pattern

Step syntax */N in any cron field means 'every N units, starting from the field's minimum value'.
  • Field positions: minute hour day-of-month month day-of-week
  • */5 in the minute field expands to 0,5,10,15,20,25,30,35,40,45,50,55
  • Use */N in any field — */2 in hour = every 2 hours, */7 in day = every 7 days
  • Some runners (notably old BSD cron) don't support */N — fall back to explicit lists

Frequently asked questions

Why */5 instead of 0,5,10,15,20,25,30,35,40,45,50,55?
They evaluate to the same schedule, but */5 is shorter and conveys intent: 'every 5 minutes'. Step syntax (*/N) is supported by Vixie cron, cronie, BusyBox cron, GNU cron, and every modern scheduler (systemd timers, Kubernetes CronJob, AWS EventBridge, GitHub Actions). Use the explicit list form only if your runtime is from before ~2000 or has a known step-syntax bug.