Meeting Planner: Compare Time Zones from UTC and Export an .ics Event

1. Meeting time in UTC

Enter the start in UTC (Coordinated Universal Time) on a 24-hour clock. UTC has no daylight saving time, so every UTC date and time names exactly one moment.

Start date (UTC)

Format YYYY-MM-DD, years 1970–2099.

Start time (UTC, 24-hour)

Format HH:MM, 00:00–23:59.

Duration (minutes)

Whole minutes from 1 to 1440 (24 hours).

Event title

1–200 characters. Used in the calendar file only.

2. Time zones to compare

Select 2 to 8 zones.

3. Comparison

No comparison yet. Enter a UTC date and time, select at least two time zones and press “Compare times”.

How times are calculated

Why the input is UTC

Local clocks are ambiguous around daylight-saving changes. When clocks spring forward, a local hour is skipped: in New York on 2026-03-08 the clock jumps from 01:59 straight to 03:00, so 02:30 never happens. When clocks fall back, an hour repeats: in New York on 2026-11-01 the time 01:30 happens twice, first at UTC−04:00 and then at UTC−05:00. A UTC time has neither problem, so this planner starts from UTC and derives every local time from it.

Reading the comparison

Each city shows the full local date and time together with its numeric UTC offset, so two identical local times can still be told apart. A “+1 day” or “−1 day” label marks a local date that differs from the UTC start date, and a note warns when a clock change is nearby.

Time zone data

Offsets come from the time zone database built into your browser (the Intl API). Governments sometimes change daylight-saving rules, so times far in the future may differ from what a later rule update produces. Check important dates again closer to the meeting.

The calendar file

The downloaded .ics file stores the start and end in UTC. Your calendar app converts them to your own time zone when you import the file.

Privacy

Everything runs in your browser. Meeting details are not sent anywhere, not stored and not emailed; the calendar file is created locally.