Cron library
Cron expression for every hour
0 * * * *
At the start of every hour 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.
Hourly cron is the workhorse of log rotation, snapshotting, and “once per hour is fine” ETL. The important part is the zero in the minute field: the job starts on the hour, not every minute of the hour.
If the minute field is a star, you get 60 runs an hour. That mix-up is one of the most common crontab bugs, and it looks almost identical on a tired Friday.
When this schedule is a good fit
Typical uses: Hourly database backups; Rotating or compressing application logs; Publishing a sitemap ping.
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
What time zone is “the hour”?
Whatever TZ the cron daemon uses — often the system local time, sometimes UTC. Preview both in the tool if you are unsure.
How do I run at 10 minutes past each hour?
10 * * * *.
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.