Cron library
Cron expression for every 2 hours
0 */2 * * *
At minute 0 past hour 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, and 22 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.
The hour field */2 is the even hours: 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, and 22. Combined with minute 0, the job starts at midnight UTC (or local) and every two hours after.
Odd-hour schedules use 1-23/2. That is a simple way to split two heavy jobs so they never start together.
When this schedule is a good fit
Typical uses: A full-text index rebuild that is too heavy for hourly; Pulling a partner catalog; Generating a sample of production metrics for a staging replay.
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
Does this include midnight?
Yes. 0 is in the */2 series.
How do I start at 01:00 instead?
0 1-23/2 * * *.
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.