Cron library
Cron expression for every 10 minutes
*/10 * * * *
Every 10 minutes every day.
Runs 100% in your browser. Nothing you paste is uploaded, stored, or sent to a server.
Or build one
Meaning
Next 10 run times
How to use
- Read the expression and the English meaning above. Confirm they match the job you have in mind.
- Use the time zone dropdown to preview the next 10 fire times in UTC or a US/EU city.
- Copy the expression into crontab, GitHub Actions (`on.schedule.cron`), or your job runner.
- If you need a nearby interval, browse the related schedules at the bottom of this page.
A 10-minute step is a comfortable middle ground: frequent enough for a retry loop, sparse enough that a 30-second job will not overlap itself under normal conditions.
The minute field expands to 0, 10, 20, 30, 40, and 50. If you need to avoid the top of the hour — when everyone else runs — shift the origin, for example 3-59/10.
When this schedule is a good fit
Typical uses: Retrying failed webhooks; Compacting a local SQLite cache; Pulling a third-party RSS or status feed.
Cron fields are zone-naive. The daemon’s TZ — or the TZ= line above the job — decides what “midnight” or “9am” means. Preview both UTC and the office zone before you ship.
FAQ
How many runs per hour?
Six. Twenty-four hours of that is 144 runs.
Will two hosts fire at the same time?
Yes, if they share the same crontab and clocks are close. Jitter the minute field per host if the downstream API is shared.
Does this page upload my crontab?
No. The explainer and the next-run list run in your browser. The expression on this page is a public example.