Cron Job Time Format Calculator

Cron Schedule Builder

Preset

Cron Expression

Timezone

Minute

Hour

Day of Month

Month

Day of Week

Upcoming Runs

Start Datetime

Supported syntax: *, lists, ranges, and step values like */10, 1,15, 1-5, or 1-10/2.

Formula Used

The calculator evaluates the standard five-field pattern:

minute hour day_of_month month day_of_week

Each field expands into a valid set of numbers. A datetime matches when its minute, hour, and month values are included, plus the day rule passes.

For day logic, standard cron behavior is applied:

match = minute ∩ hour ∩ month ∩ (day_of_month OR day_of_week when both are restricted)

Upcoming run spacing is measured with:

interval_minutes = (next_run_timestamp - previous_run_timestamp) / 60

Average spacing is then:

average_interval = sum(interval_minutes) / number_of_intervals

How to Use This Calculator

Choose a preset or enter a full five-part cron expression.
Edit minute, hour, day, month, and weekday fields if needed.
Select the timezone used for schedule interpretation.
Pick the starting datetime from which future runs are calculated.
Set how many upcoming run times you want listed.
Click Calculate Schedule to view the decoded result above the form.
Review the next-run table, interval metrics, and Plotly graph.
Export the result table as CSV or PDF when needed.

Example Data Table

Use Case	Expression	Meaning
Health check	`/5 * * *`	Runs every five minutes.
Night backup	`0 2 * * *`	Runs daily at 02:00.
Weekday report	`30 9 * * 1-5`	Runs Monday to Friday at 09:30.
Month opening task	`0 0 1 * *`	Runs at midnight on day one monthly.
Quarterly reminder	`15 8 1 jan,apr,jul,oct *`	Runs at 08:15 on the first day of quarter-start months.

FAQs

1. What cron format does this calculator support?

This page supports the standard five-field format: minute, hour, day of month, month, and day of week. It accepts stars, lists, ranges, and step values. It does not process special Quartz fields like seconds or year.

2. Does the calculator understand month and weekday names?

Yes. You can use names like jan, feb, mon, or fri. The calculator converts those names to numeric cron values before validating the schedule and generating future execution times.

3. Why does day of month sometimes behave like OR with weekday?

Standard cron treats day-of-month and day-of-week as an OR condition when both are restricted. That means a job may run when either field matches. This tool follows that rule so the preview better reflects real cron behavior.

4. Can I use this tool to validate a broken expression?

Yes. Invalid ranges, unsupported syntax, empty segments, and out-of-range values trigger an error. That makes it easier to spot mistakes before you place the expression inside a server crontab or deployment pipeline.

5. How is the next run time calculated?

The calculator starts from your chosen datetime, moves forward minute by minute, and records every timestamp matching the cron rules. It then reports the next execution time, additional upcoming runs, and interval statistics.

6. Why should I choose the correct timezone?

Cron timing depends on the timezone of the system or service interpreting the expression. Using the wrong timezone can shift jobs by hours, especially across daylight saving transitions or when working with global infrastructure.

7. What does the Plotly graph show?

The graph plots each upcoming scheduled run against its distance from the chosen starting time in minutes. It helps you see whether runs are evenly spaced, clustered, or irregular across the selected schedule window.

8. When should I export the result as CSV or PDF?

Use CSV when you want to review timings in spreadsheets or share machine-friendly data. Use PDF when you need a print-ready schedule summary for documentation, change reviews, audits, or client-facing handoff material.