Cron Next Run Times

Enter a cron expression like */15 * * * * or 0 9 * * MON-FRI and see the next run times in UTC. Supports seconds, ranges, steps, lists, month/weekday names and @daily/@hourly shortcuts. Runs entirely in your browser, no server, no sign-up.

Next run times

What this cron tool does

Paste a cron expression and this tool shows you a plain-English description of the schedule plus the next times it will fire — entirely in your browser, so nothing you type leaves your machine. It's the quickest way to sanity-check a crontab line, a scheduled job, or a CI trigger before you ship it.

All times are computed and shown in UTC.

Supported syntax

The tool understands standard 5-field crontab syntax:

┌───────────── minute (0-59)
│ ┌─────────── hour (0-23)
│ │ ┌───────── day of month (1-31)
│ │ │ ┌─────── month (1-12 or JAN-DEC)
│ │ │ │ ┌───── day of week (0-7 or SUN-SAT; 0 and 7 are Sunday)
│ │ │ │ │
* * * * *

Each field accepts:

You can also add a leading seconds field (6 fields total), e.g. */30 * * * * * runs every 30 seconds.

When both day-of-month and day-of-week are restricted, a time matches if either matches — the classic Vixie-cron behavior.

Shortcuts

@yearly (@annually), @monthly, @weekly, @daily (@midnight) and @hourly are all accepted.

Examples

Options

FAQ

Why don't the times match my server's cron?

All run times here are computed in UTC. If your server's crontab runs in a local timezone (or a container sets TZ), shift the results by that offset — the schedule pattern itself is identical.

My expression restricts both day-of-month and day-of-week — why so many runs?

That's classic Vixie-cron behavior, which this tool reproduces: when both fields are restricted, a time fires if either one matches. So 0 0 13 * FRI runs every Friday and every 13th, not only on Friday the 13th.

Can I preview more than a handful of upcoming runs?

Yes — set How many runs anywhere from 1 to 100 (the default is 5). To look at a different time window, put an ISO-8601 timestamp or Unix epoch second in the After field and the list starts from there instead of now.

Does it support seconds or Quartz-style expressions?

A leading seconds field is supported (6 fields, e.g. */30 * * * * *), plus @daily-style shortcuts, ranges, steps, lists, and JAN-DEC / SUN-SAT names. Quartz-specific tokens like ?, L, W and # are not recognized.

Developer & Automation Access

Run it from the terminal

Same engine as this page, headless — via the gizza CLI:

gizza tool cron-next-runs "*/15 * * * *   or   0 9 * * MON-FRI"

New to the CLI? Get gizza →

Open it by URL

Pre-fill and auto-run this tool with query parameters — the names match the API/CLI:

https://gizza.ai/tools/cron-next-runs/?expression=%2A%2F15%20%2A%20%2A%20%2A%20%2A%20%20%20or%20%20%200%209%20%2A%20%2A%20MON-FRI&after=blank%20%3D%20now%2C%20%20or%20%202025-01-01T09%3A00%3A00Z&count=5&format=text

Machine-readable descriptor: tool.json — title + parameters JSON Schema for agents.