Cron Translator

Cron for twice a day

At midnight and noon, written as an explicit list rather than a step.

0 0,12 * * *

At 00:00 and 12:00

Interpreted in UTC · approximately 2 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.
Hour0,12: At 00:00 and 12:00.
Day of month*: Every day of the month.
Month*: Every month.
Day of week*: Every day of the week.

Next runs

Thu, 2026-09-03, 00:002026-09-03T00:00:00.000Z
Thu, 2026-09-03, 12:002026-09-03T12:00:00.000Z
Fri, 2026-09-04, 00:002026-09-04T00:00:00.000Z
Fri, 2026-09-04, 12:002026-09-04T12:00:00.000Z
Sat, 2026-09-05, 00:002026-09-05T00:00:00.000Z
Sat, 2026-09-05, 12:002026-09-05T12:00:00.000Z
Sun, 2026-09-06, 00:002026-09-06T00:00:00.000Z
Sun, 2026-09-06, 12:002026-09-06T12: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%200%2C12%20*%20*%20*'

API and MCP setup · this page as markdown

Related schedules