How the calculation works
The calculator walks the calendar forward from now, matching every field at once, and returns the first ten timestamps that satisfy the expression. It does not guess: if the expression is invalid, it reports the offending field instead of returning plausible-looking times.
The timezone you select is the timezone used for matching, which mirrors how a cron daemon interprets its crontab. That matters for expressions anchored to a wall-clock hour such as 0 2 * * *: in a DST zone, 02:00 may not exist on one day of the year.
Reading the output
- Local time is shown in the selected timezone, with the zone abbreviation where available.
- UTC is shown alongside so you can compare with server logs and container clocks.
- Relative labels (“in 3 hours”) are computed from your device clock, not from the server.
- The list stops at ten entries; for sparse schedules such as quarterly jobs, the last entries can be years away.
Common expressions to test
0 0 * * * # daily at 00:00
0 9 * * 1-5 # weekdays at 09:00
*/5 * * * * # every 5 minutes
0 0 1 * * # first of the month
0 0 1 1,4,7,10 * # quarterly
Timezone and DST checks worth doing once per year
Run the preview twice: once with the server's timezone and once with the timezone the business thinks in. If the two disagree, the safest fix is to schedule in UTC and convert the intended local time, because UTC has no DST. Document the conversion in a comment next to the crontab line.
If a job must run once per day regardless of DST, prefer an hourly job guarded by a date check, or use systemd timers with Persistent=true.