Cron calendar & .ics export
Paste a cron expression to see which days it runs, then export the runs to your calendar app.
See your cron schedule on a calendar
A cron expression is compact but hard to picture. Does 0 3 1,15 * * hit a weekend? How many days between runs of 0 0 */10 * * at the end of a month? A calendar answers at a glance. This tool evaluates the expression with the same engine as the rest of the site, in any of the supported dialects (Unix, Quartz, Spring, Kubernetes, EventBridge, Jenkins, GitHub Actions, node-cron, Airflow, Azure and Google Cloud Scheduler) and a time zone of your choice, and draws a month grid with the number of runs on each day.
Hover or tap a day to see the times. When you are happy, download an .ics file containing one event per run for the chosen period, with a title and duration you set. Import it into Google Calendar, Outlook or Apple Calendar to share the schedule with a team or to block out maintenance windows. Events are marked as free time so they do not make people look busy.
Good uses
- Checking when a batch job collides with a release freeze or a weekend.
- Showing a stakeholder when a report will arrive.
- Verifying daylight saving behaviour: pick a zone and a period that spans the change and watch the local times.
- Documenting a schedule in a runbook with a picture instead of an expression.
Events use absolute UTC times, so they stay correct for every viewer. The grid and file are produced in your browser; no schedule is uploaded.
Frequently asked questions
Why export a cron schedule to a calendar?
Schedules are easier to reason about on a calendar: you can see that the month-end job lands on a weekend, that two jobs share a day, or when the maintenance window actually starts. Importing the file into Google Calendar, Outlook or Apple Calendar also lets the team see it.
Are the times in UTC?
Yes. Each event is written with an absolute UTC time (a trailing Z), so every calendar app shows it correctly in the viewer's own time zone, including across daylight saving changes. The grid view groups runs by the local day of the time zone you choose.
Why is the number of events limited?
A schedule such as every minute produces 1,440 runs a day, which would swamp any calendar. The export stops at the limit you set (up to 1,000 events) and tells you when it did.
Does the file update itself?
No. It contains the runs for the chosen window, like a snapshot. Generate a new file when you change the schedule or when the window ends. For a repeating event in a calendar, create a recurring event by hand.