0 1 * * *
Cron reads this as: at 01:00.
Next 5 runs
These times are in your browser's local time zone. Cron itself uses the server's zone, which on most cloud hosts is UTC. If the difference matters here, see time zones & DST.
- Calculating…
When to use this schedule
01:00 is an hour after the midnight rush, so it is a popular slot for backups and batch work that need a quiet machine but still have to finish well before morning.
What to watch out for
01:00 falls inside the hours that daylight saving changes can affect. 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 at 01:00, the hour can be skipped entirely. If this job must run exactly once a day, 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>&1Send the output to a log you will read. By default cron mails it, and on a host with no mail transport that mail is silently dropped. 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
If this page doesn't cover the schedule you need, 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 has sixty schedules in one place, and the guides cover crontab syntax, time zones, troubleshooting and production practices.