Cron Translator

Cron for once a year on January 1

Midnight on New Year's Day. Equivalent to the @yearly macro.

0 0 1 1 *

At 00:00, on the 1st of the month, in January

Interpreted in UTC · never runs

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.
Hour0
At 00:00.
Day of month1
On the 1st.
Month1
In January.
Day of week*
Every day of the week.

Next runs

  1. Fri, 2027-01-01, 00:00
  2. Sat, 2028-01-01, 00:00
  3. Mon, 2029-01-01, 00:00
  4. Tue, 2030-01-01, 00:00
  5. Wed, 2031-01-01, 00:00
  6. Thu, 2032-01-01, 00:00
  7. Sat, 2033-01-01, 00:00
  8. Sun, 2034-01-01, 00:00

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%200%201%201%20*'

API and MCP setup · this page as markdown

Related schedules