What the expression does

0 0 * * * runs once per day at 00:00 in the daemon's timezone: minute 0, hour 0, every day of every month.

The first two fields pin the time to midnight; the last three are wildcards, so every day matches. There is no “once per 24 hours from now” semantics — it is a wall-clock schedule.

When this schedule is useful

  • Nightly database dumps and backup rotations.
  • Cleaning temporary files, sessions or expired cache entries.
  • Daily report generation before the business day starts.
  • Recomputing daily aggregates from yesterday's events.

Nearby expressions worth knowing

Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:

  • Daily at 02:00: 0 2 * * * — A quieter slot than midnight.
  • Daily at noon: 0 12 * * * — Useful for jobs tied to business hours.
  • Twice daily: 0 2,14 * * * — Morning and afternoon runs.
  • Every 24 hours from now (approx.): 0 3 * * * — Cron is wall-clock; use a scheduler for exact intervals.
cron
0 2 * * *          # Daily at 02:00
0 12 * * *         # Daily at noon
0 2,14 * * *       # Twice daily
0 3 * * *          # Every 24 hours from now (approx.)

Timezone, load and edge cases

Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.

Midnight is a popular time; backups, log rotation and monitoring all collide. Consider 02:00–04:00 with a random minute.

If the host timezone observes DST, a 00:00 job may run twice or shift by an hour. For strict once-per-day behavior, schedule in UTC or guard with a date check.

A failed nightly job is invisible until someone notices missing data. Log the exit code and alert on absence, not just failure.

If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.

Verify it before shipping

  • Run the expression through the explainer and read the English sentence once.
  • Check the next five run times in the server's timezone, not your laptop's.
  • Execute the command manually with the same user and environment cron will use.
  • Redirect stdout and stderr to a log file, and include a timestamp in each line.