Zero Signup ToolsFree browser tools

Developer Tools

Cron Next Run Time Calculator

Paste a cron expression and see the next run times in your local time zone or UTC, with a plain-English summary and the average gap between runs. No signup.

Cron expression

Standard 5 fields: minute, hour, day of month, month, day of week. Names like MON or JAN and the @daily, @hourly, and @weekly macros are accepted.

Examples

Options

Time zone

Local time uses UTC.

How many runs
Start from

Next run times

Runs every 15 minutes every day.

Normalized: */15 * * * * Average gap between runs: about 15 minutes.

  1. 2026-06-23T13:45:00

    Tuesday, June 23, 2026 at 13:45 (in 2 minutes)

  2. 2026-06-23T14:00:00

    Tuesday, June 23, 2026 at 14:00 (in 17 minutes)

  3. 2026-06-23T14:15:00

    Tuesday, June 23, 2026 at 14:15 (in 32 minutes)

  4. 2026-06-23T14:30:00

    Tuesday, June 23, 2026 at 14:30 (in 47 minutes)

  5. 2026-06-23T14:45:00

    Tuesday, June 23, 2026 at 14:45 (in 1h 2m)

  6. 2026-06-23T15:00:00

    Tuesday, June 23, 2026 at 15:00 (in 1h 17m)

  7. 2026-06-23T15:15:00

    Tuesday, June 23, 2026 at 15:15 (in 1h 32m)

  8. 2026-06-23T15:30:00

    Tuesday, June 23, 2026 at 15:30 (in 1h 47m)

  9. 2026-06-23T15:45:00

    Tuesday, June 23, 2026 at 15:45 (in 2h 2m)

  10. 2026-06-23T16:00:00

    Tuesday, June 23, 2026 at 16:00 (in 2h 17m)

How cron fields and timing work

  • The five fields are minute (0 to 59), hour (0 to 23), day of month (1 to 31), month (1 to 12 or JAN to DEC), and day of week (0 to 6 or SUN to SAT, where both 0 and 7 mean Sunday).
  • Use a star for every value, a list with commas (1,15,30), a range with a dash (1-5), or a step with a slash (*/15 means every 15, and 10-30/5 means 10, 15, 20, 25, 30).
  • When the day-of-month and day-of-week fields are both set, cron runs when either one matches, not only when both do. This calculator follows that standard rule.
  • Cron fires on the start of a minute, so the times shown always have zero seconds. A schedule like 0 9 * * * means 09:00 exactly.
  • Server crontabs usually run in the machine time zone, which is often UTC. Switch the time zone above to match where the job actually runs, since daylight saving can shift local clock times.

How to use

  1. Paste or type a standard five-field cron expression, for example 30 9 * * 1-5, or tap one of the examples.
  2. Choose the time zone: Local uses your device, UTC matches most servers.
  3. Pick how many upcoming runs to list, and optionally switch the start from Now to a custom date and time.
  4. Read the next run times as ISO timestamps and readable dates, plus a plain-English summary and the average gap between runs.
  5. Copy a single run, the full ISO list, or the complete summary to paste into a ticket, runbook, or chat.

About this tool

Cron Next Run Time Calculator answers the one question a crontab line never tells you on its own: when will it actually run next. You paste a standard five-field cron expression, the kind used by Vixie cron, most Linux distributions, Docker, and many CI systems, and the tool lists the next upcoming run times as real dates, not just a description of the rule. It works by parsing each field into the exact set of values it allows, then stepping forward minute by minute from a start instant and collecting the first matches, which is the same logic a cron daemon uses, so the times you see are the times the job would fire. Every part of standard cron syntax is supported: a star for every value, comma lists such as 0,15,30,45, ranges such as 1-5, and steps such as */15, 10-30/5, or 9/2. Month and weekday fields accept names as well as numbers, so JAN through DEC and SUN through SAT all work, and both 0 and 7 are treated as Sunday. The common macros @hourly, @daily, @midnight, @weekly, @monthly, @yearly, and @annually are expanded for you and shown in their normalized five-field form so you can see exactly what was simulated. The calculator also follows the often-misunderstood day rule correctly: when the day-of-month and day-of-week fields are both restricted, cron runs when either one matches, not only when both do, so a schedule like 0 0 13 * 5 fires on the 13th of the month and on every Friday. Time zones matter for scheduling, so you can read the results in your device local time or in UTC, which is what most servers run in, and switching between them shows how daylight saving can move a local clock time. You can start the preview from now or from any custom date and time, choose how many upcoming runs to list, and copy a single time, the whole list of ISO timestamps, or a full summary that includes the plain-English description and the average gap between runs. This tool is the missing companion to the catalog's cron explainer and cron generators: where those describe a schedule or help you build the expression, this one shows you the concrete clock times it produces, which is what you need when debugging a job that did not fire, confirming a new schedule before deploying it, or planning around a backup, report, or cleanup task. Everything is computed in your browser, so the expression you type is never uploaded.

Free to use. Works in your browser. No signup, no login.

Related tools

You may also like

All tools
All toolsDeveloper Tools