Cron expression for every 5 minutes

Every 5 minutes

*/5
minute
*
hour
*
day (month)
*
month
*
day (week)

Every 5 minutes

Try this expression in the interactive tool:

Open in cron explainer →

Next 10 scheduled runs

#1Thu, 16 Apr 2026, 00:10
#2Thu, 16 Apr 2026, 00:15
#3Thu, 16 Apr 2026, 00:20
#4Thu, 16 Apr 2026, 00:25
#5Thu, 16 Apr 2026, 00:30
#6Thu, 16 Apr 2026, 00:35
#7Thu, 16 Apr 2026, 00:40
#8Thu, 16 Apr 2026, 00:45
#9Thu, 16 Apr 2026, 00:50
#10Thu, 16 Apr 2026, 00:55

Common use cases

Every 5 minutes is one of the most widely used cron schedules in production systems. It strikes a balance between near-real-time responsiveness and reasonable resource consumption.

Common applications include health checks and uptime monitoring — pinging internal services or external dependencies and alerting if they're down. Many infrastructure teams use this interval for lightweight synthetic monitoring that complements heavier tools like Datadog or Pingdom.

Cache warming and invalidation is another frequent use case. If your application serves data that changes every few minutes (stock prices, sports scores, inventory counts), a 5-minute cron job can pre-compute and cache the results so that user-facing requests never hit the database directly.

Note that */5 fires at minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55 — always aligned to the clock, not to when the cron daemon started.

Platform-specific syntax

crontab
*/5 * * * * /path/to/script.sh
AWS EventBridge
rate(5 minutes)
GitHub Actions
schedule:
  - cron: '*/5 * * * *'  # Every 5 min (UTC)
Kubernetes
schedule: "*/5 * * * *"

Technical breakdown

The expression */5 * * * * has five fields: minute=*/5, hour=*, day (month)=*, month=*, day (week)=*. Every 5 minutes.

Frequently asked questions

What's the difference between */5 and 0/5 in the minute field?
They're identical. */5 means 'every 5th minute starting from 0' and 0/5 means the same thing explicitly. Both fire at minutes 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55. The */5 form is more conventional.
Does */5 always run at :00, :05, :10 etc., or relative to when cron started?
Always aligned to the clock. The step operator divides the field's valid range (0-59) into intervals. So */5 always fires when the current minute is divisible by 5, regardless of when the cron daemon started or when the crontab entry was added.