Cron library
Cron expression for every 6 hours
0 */6 * * *
At minute 0 past hour 0, 6, 12, and 18 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.
Four times a day is a natural cadence for reports that follow a workday: overnight, mid-morning, after lunch, and evening. */6 on the hour field hits 0, 6, 12, and 18.
If your team thinks in “6am, noon, 6pm, midnight” in a US or EU city, set the preview time zone to that city. The expression itself is zone-naive; the daemon’s TZ decides the wall clock.
When this schedule is a good fit
Typical uses: Quarter-day financial snapshots; Refreshing a CDN-backed export; Cycling a staging database refresh.
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
Is 18:00 6pm?
Yes, in a 24-hour clock. Cron hours are 0–23.
How do I run at 03, 09, 15, and 21 instead?
0 3,9,15,21 * * * or 0 3-21/6 * * *.
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.