Cron expression: every hour

0 * * * * runs every hour. Here is what each field means, when it runs next and how to use it in crontab, GitHub Actions, Kubernetes and Node.js.

Updated

0 * * * *
Cron expression
Every hour
Schedule

Open in the Cron Expression Generator →

What 0 * * * * means

Cron reads five fields from left to right: minute, hour, day of the month, month and day of the week. For every hour they are:

FieldValueMeaningAllowed
Minute000–59
Hour*every hour0–23
Day of month*every day of the month1–31
Month*every month1–12
Day of week*every day of the week0–6 (Sun–Sat)

Next runs

Calculated in your browser for your time zone. On a server, cron uses the server’s time zone (often UTC).

  1. Enable JavaScript to see the next run times.

Typical uses

  • Hourly reports and digests
  • Log rotation
  • Pulling analytics

Good to know

Runs at minute 0 of every hour. Many jobs start at :00, so pick another minute (for example 17 * * * *) to avoid load spikes. @hourly is the same schedule.

Use it in crontab, GitHub Actions, Kubernetes and Node.js

crontab (crontab -e):

0 * * * * /usr/local/bin/my-job.sh >> /var/log/my-job.log 2>&1

GitHub Actions (times are UTC):

on:
  schedule:
    - cron: '0 * * * *'

Kubernetes CronJob:

apiVersion: batch/v1
kind: CronJob
metadata:
  name: my-job
spec:
  schedule: "0 * * * *"
  concurrencyPolicy: Forbid
  jobTemplate:
    spec:
      template:
        spec:
          restartPolicy: OnFailure
          containers:
            - name: my-job
              image: alpine:3
              command: ["sh", "-c", "echo running"]

Node.js (node-cron):

import cron from 'node-cron';
cron.schedule('0 * * * *', () => {
  // your job
});

Related schedules

Build your own scheduleTurn any schedule into a cron expression — or any expression into plain English — with the next run times.
Open the Cron Generator

Frequently asked questions

What is the cron expression for every hour?
0 * * * *. It runs at 0.
Which time zone does cron use?
Classic cron uses the server’s local time zone, and many servers run in UTC. GitHub Actions always uses UTC. Kubernetes CronJobs use the controller’s time zone unless you set spec.timeZone (for example Europe/Berlin).
How do I test a cron expression?
Paste it into the Cron Expression Generator to see it in plain English with the next run times, then check your job’s log after the first scheduled run.