← All Tools
Cron Time Predictor Calculator🔒 100% local
Predict cron execution times. Privacy-first, no server uploads, no tracking.
Related Tools
Expands a cron expression into the next five moments it fires, printing each one both as a UTC timestamp and as a local-time reading so the two can be compared. Month and weekday names, lists, ranges and step values are all expanded before matching, and when both day-of-month and day-of-week are restricted the POSIX rule applies: a match on either one is enough. The minute-by-minute scan runs in the tab and stops after a year.
How to use it
- Paste an expression such as 0 9 * * 1-5.
- Press Process.
- Compare the UTC column with the local column to see which hour the job will really run at.
Worked example
0 9 * * 1-5becomesCron: 0 9 * * 1-5
At 9:00 on Mon/Tue/Wed/Thu/Fri
Next 5 fire times:
2026-09-28 08:00:00 UTC — Mon Sep 28 2026 09:00:00 (local)
2026-09-29 08:00:00 UTC — Tue Sep 29 2026 09:00:00 (local)
2026-09-30 08:00:00 UTC — Wed Sep 30 2026 09:00:00 (local)
2026-10-01 08:00:00 UTC — Thu Oct 01 2026 09:00:00 (local)
2026-10-02 08:00:00 UTC — Fri Oct 02 2026 09:00:00 (local)The local column reads 09:00 while UTC reads 08:00 because the page was rendered at UTC+1. That missing hour is the usual reason a job looks like it fires at the wrong time.
When to use it
- You are about to schedule something on a server and want to know when it next runs before it runs.
- You need to explain why a job written as 0 9 * * * shows up at 08:00 in a log.
- You are comparing two candidate expressions and want their fire times side by side.
What it does not do
- The list stops at five matches and the scan gives up after a year, so a rare schedule reports that no fire time was found rather than an approximate date.
- It knows the calendar only. Host uptime, overlapping runs and any CRON_TZ setting on the machine are invisible to it.
- A six-field expression is accepted for display but the seconds field is not used when the times are worked out.