0 1 * * *
Cron reads this as: at 01:00.
Next 5 runs
Computed in your browser's local time zone. Cron itself evaluates against the server's zone, which on most cloud hosts is UTC — see time zones & DST if that distinction matters here.
- Calculating…
When to use this schedule
An hour past the midnight rush, which makes it a popular slot for backups and batch work that wants a quiet machine but still needs to finish well before morning.
What to watch out for
01:00 sits inside the daylight saving danger zone. In zones that fall back, the 01:00 hour occurs twice, and implementations differ on whether a fixed-time job in that hour runs once or twice. In zones that spring forward from a 01:00 boundary the hour can be skipped entirely. If this job must run exactly once a day, either move it to 0 3 * * * or make it idempotent so a double run is harmless.
The crontab line
0 1 * * * /usr/local/bin/your-job.sh >> /var/log/your-job.log 2>&1Redirect the output somewhere you will actually read it — by default cron mails it, and on a host with no mail transport that means it is discarded. See the crontab guide for the surrounding syntax.
Related schedules
| Expression | Schedule |
|---|---|
0 3 * * * | 03:00 — clear of DST transitions |
30 1 * * * | 01:30 daily |
0 1 * * 1-5 | 01:00 on weekdays only |
Build your own
Need something this page does not cover? Compose it field by field in the visual builder, or paste an expression you already have into the explainer for a per-field breakdown. The examples library collects sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.