Cron Translator

Cron for every 4 hours

Six runs a day, dividing the day evenly.

0 */4 * * *

At minute 0 past every 4th hour

Interpreted in UTC · approximately 6 runs per day

Things to check

Note
Interpreted in UTC
A cron expression has no timezone of its own — the scheduler's zone decides when it fires. These times are computed in UTC. The same expression on a host in another zone runs at a different moment.
Fix: Set the schedule timezone explicitly (TZ= or CRON_TZ= in crontab, `timeZone` in Kubernetes, or the scheduler's own setting). Vercel Cron Jobs always run in UTC.

Fields

Minute0: At minute 0.
Hour*/4: Every 4 hours.
Day of month*: Every day of the month.
Month*: Every month.
Day of week*: Every day of the week.

Next runs

Wed, 2026-09-02, 16:002026-09-02T16:00:00.000Z
Wed, 2026-09-02, 20:002026-09-02T20:00:00.000Z
Thu, 2026-09-03, 00:002026-09-03T00:00:00.000Z
Thu, 2026-09-03, 04:002026-09-03T04:00:00.000Z
Thu, 2026-09-03, 08:002026-09-03T08:00:00.000Z
Thu, 2026-09-03, 12:002026-09-03T12:00:00.000Z
Thu, 2026-09-03, 16:002026-09-03T16:00:00.000Z
Thu, 2026-09-03, 20:002026-09-03T20:00:00.000Z

Try a different expression or timezone

Times above are in UTC. Pick a timezone here to see this schedule in local time.

Call this from code or an agent

curl 'https://crontoenglish.com/api/v1/explain?expression=0%20*%2F4%20*%20*%20*'

API and MCP setup · this page as markdown

Related schedules