Cron Next Run Times Calculator
Paste a 5-field cron expression and pick a start time to list the next times it will fire. The from-date defaults to now, so you can quickly confirm a crontab line or scheduled job will run when you expect. All times are computed in UTC.
How to find a cron expression's next run times
- Enter your cron expression: minute, hour, day of month, month, day of week.
- Set the start time (it defaults to the current time) and choose how many runs to list.
- Read the upcoming UTC run times and copy them if you need them elsewhere.
Examples
Every 15 minutes from 00:02
*/15 * * * * from 2026-06-09T00:02:00Z
2026-06-09T00:15:00Z, 2026-06-09T00:30:00Z, 2026-06-09T00:45:00Z
Every weekday at 9am
0 9 * * 1-5
The next Monday-to-Friday 09:00 UTC slots after your start time.
Frequently asked questions
What cron format does this use?
The standard 5-field crontab format: minute (0-59), hour (0-23), day of month (1-31), month (1-12) and day of week (0-6, where 0 and 7 are both Sunday). It supports *, lists like 1,15, ranges like 1-5, steps like */15 and 0-30/10, and three-letter names such as JAN-DEC and MON-FRI.
What timezone are the run times in?
All run times are calculated and shown in UTC so they are consistent everywhere. A real crontab usually fires in the server's local timezone, so add or subtract that offset when you compare these UTC times to your schedule.
Is the next run time strictly after my start time?
Yes. The calculation starts from the minute after your start time, so if the start time lands exactly on a matching minute, that minute is skipped and you get the following run instead. Seconds in the start time are ignored.
How do day of month and day of week work together?
When both day of month and day of week are set to something other than *, the job runs when EITHER one matches (the classic cron OR behavior). If one of them is *, only the other field constrains the day.
Is my cron expression sent to a server?
No. The expression is parsed and the run times are computed entirely in your browser. Nothing you type is uploaded or stored.
Why did I get an error instead of run times?
Either the expression is invalid (wrong number of fields or a value out of range), or the schedule can never fire, such as February 31st. The tool scans up to about five years ahead and reports an error if it finds no matching run.
Related tools
Cron Expression Explainer
Paste a cron expression to see what it means in plain English plus the next 5 run times. Works fully in your browser, no signup needed.
Crontab Generator
Build a cron expression from simple fields. Pick a preset or set minute, hour, day, month and weekday, then copy the line for your crontab.
Days Until Date Calculator
Count the days until any date. Enter a target date to see how many days, weeks, months and business days are left, with a from date that defaults to today.
.env to JSON
Convert a .env file to JSON, or JSON back to .env. Parses KEY=value lines, comments, quotes and export. Runs entirely in your browser.
Aspect Ratio Calculator
Calculate aspect ratios fast. Enter a ratio like 16:9 and one dimension to get the other, or enter width and height to simplify the ratio.
Base58 Encoder
Encode and decode Base58 online with the Bitcoin alphabet. Convert text to Base58 or back, UTF-8 safe, no confusing 0 O I l. Runs in your browser.