Developer Utilities

Cron Calendar

All tools

See exactly when a cron job will fire in the timezone your scheduler actually uses.

How it works

Four simple steps

1

Enter a cron expression

Paste five-field cron or start from a common preset.

2

Read the human summary

See when the job runs in plain English.

3

Preview next runs

List the next fire times in your chosen timezone.

4

Copy for deploy configs

Use the expression in crontab, K8s CronJob, or CI schedules.

Cron Calendar

About Cron Calendar

A nightly export is scheduled as 30 2 * * * on a server set to America/New_York. Twice a year somebody asks why it ran at an odd time or not at all. Cron Calendar lists the real upcoming run times for that zone, so the daylight-saving surprise shows up in review instead of in an incident channel.

Type an expression or start from one of ten presets (every 15 minutes, weekdays at 09:00, quarterly and so on), then choose one of 18 IANA timezones, from UTC and America/Los_Angeles to Asia/Kolkata and Pacific/Auckland. The tool describes the schedule in a sentence, breaks down each of the five fields, and lists up to 100 upcoming runs with the UTC offset, the exact UTC instant and a relative hint such as 'in 3h'. Tick Compare two expressions to put a second schedule beside the first, which helps when you are replacing a job. The text version can be copied or downloaded for a ticket.

Ranges, steps, lists, month and weekday names, and macros such as @daily and @weekly are accepted. Six-field Quartz expressions, @reboot and the L, W and # extensions are rejected with a reason. One rule trips people up: when both day-of-month and day-of-week are restricted, classic cron runs on either match, so 0 0 13 * 5 fires on the 13th and on every Friday. If you would rather build the expression from form fields first, start in the cron expression generator, or grab a line from the common cron presets.

All the date math runs in this tab using the browser's built-in timezone data, so nothing about your job schedule is sent anywhere. To convert a single moment between zones rather than a recurring schedule, use the converter in Math Tools.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

Those runs fall inside an hour that is skipped when clocks spring forward in the chosen timezone. Depending on the scheduler, such a run is either dropped or fired right after the jump, so the tool marks it instead of guessing. A separate banner appears whenever the UTC offset changes inside the preview window.

Not as is. Six fields are rejected because the calendar follows the classic five-field crontab format. Drop the leading seconds field, replace any L, W or # tokens with explicit days, and preview again.

Kubernetes evaluates CronJobs in UTC unless the spec sets a timeZone field, while plain crond follows the host's system timezone. Pick whatever your scheduler really uses, otherwise the preview will look right and still be wrong.

View more FAQs

Related tools

View all

CSV to SQL

Infer column types and generate CREATE TABLE + INSERT statements from CSV.

Open

SQL Query Builder

Build SELECT queries visually and reverse-parse SQL into a structure tree.

Open

Log Pattern Miner

Cluster log lines into templates, surface anomalies, and mask PII locally.

Open

MongoDB Query Builder

Build find/aggregate pipelines visually and export mongosh snippets.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools