How it works

One instant. A local clock for every city.

A shared timestamp

Every city row is rendered from the same timestamp: a count of milliseconds since the Unix epoch. Changing a date, a time or the timeline changes that timestamp for all rows. There is no separate clock calculation drifting independently in each city.

IANA identifiers and Intl

An identifier such as America/New_York describes a location’s time-zone rules. The browser’s Intl.DateTimeFormat formats the common instant with those rules. No runtime date library or remote time API is required.

Calculating UTC offsets

The tool reads the local calendar fields for the instant and compares those fields with the UTC representation. The difference is the date-specific offset in minutes. Keeping minutes preserves half-hour and quarter-hour zones.

Entering a local clock time

A local date and time does not always identify one instant. The converter checks candidate offsets around the selected date and keeps only instants that format back to the exact requested fields. Zero matches means a skipped time; two matches means a repeated time that needs an explicit first-or-second choice.

Daylight-saving status

Offset arithmetic never depends on an abbreviation. The site samples annual offsets to describe seasonal changes. For supported conventional regimes, it identifies the higher seasonal offset as daylight-saving time. Exceptional legal terminology and unsupported regimes are labeled as unknown rather than guessed.

Finding meeting overlap

The planner samples candidate starts every fifteen minutes in the first city’s selected day. It checks the entire meeting duration against every work interval, including intervals that cross midnight. Equal start and end means no work interval. It ranks candidates by the number of participants within their selected workday and penalizes hours before 6 AM or at/after 10 PM.

The shaded timelines show local day periods. Blue underlines indicate sampled shared working moments. Recommendation labels evaluate the full meeting, which can extend beyond a highlighted start. Weekends are included; there is no holiday or calendar-availability data.

Your local zone without GPS

The browser’s configured time zone is detected with Intl.DateTimeFormat().resolvedOptions().timeZone. No precise location permission is requested. The tool saves preferences locally when storage is available, and works without storage too.

Static content and live clocks

Searchable pages contain static descriptions, dated conversion tables and links. Live current-time values are added in the browser so a stale build-time clock is never presented as “now.” Pair pages label their reference date and distinguish daily seasonal samples from exact transitions.

Limitations

An inaccurate device clock or outdated time-zone database affects results. Future laws cannot be predicted. See the accuracy disclaimer and data sources.