Guides

Check a time-zone conversion before you send it

Check source and destination cities, local dates, DST ambiguity and copied results before sharing a time-zone conversion.

Start with the original location and date

A message such as “tomorrow at nine” is incomplete for an international audience. Identify the city whose clock defines the appointment, its local calendar date, and the intended time. In the time converter, From interprets your input; To only changes how that instant is displayed. The date field belongs to From, not your device's zone or the destination.

Choose a named IANA zone through the city picker. A present-day UTC difference is not a safe replacement for a region's rules on a future appointment date. Country shortcuts represent the region indicated in their label. For a multi-zone country, choose the actual city. A nearby city is not automatically interchangeable: political borders, seasonal changes and historical rules can differ.

A worked cross-date check

Enter 2026-10-13 09:26 for Beijing and choose Los Angeles:

ItemExpected reading
SourceBeijing · 2026-10-13 09:26 · UTC+08:00
Same instant in UTC2026-10-13 01:26
DestinationLos Angeles · 2026-10-12 18:26 · UTC−07:00
Destination date relationPrevious day

Read the entire result before copying. “18:26” alone omits the most important difference: Los Angeles is still on October 12. For Beijing 2026-01-13 09:26, Los Angeles instead reads January 12 at 17:26, using UTC−08:00. This one-hour change comes from the selected date's seasonal rules, not a different input format.

Resolve invalid or ambiguous input

The tool accepts YYYY-MM-DD HH:mm, with optional seconds, for dates in 1970–2100. Invalid dates must be corrected rather than allowed to roll into another month. A spring-forward gap is a separate problem: New York 2024-03-10 02:30 never occurred. Choose an existing local time after checking the original appointment.

New York 2024-11-03 01:30 occurred twice. The earlier occurrence uses UTC−04:00 and the later UTC−05:00; they are one hour apart. Ask the sender which occurrence they intend, then select the corresponding option. See the DST guide for the distinction between a zone and an offset.

Check before copying

Changing the source city or input clears the previous result. Press Convert time again; do not reuse a time copied before the edit. Adding destination cities compares the same successfully resolved instant, without changing the appointment. Swapping after a conversion also retains that instant.

A 12/24-hour switch changes display, not the calculation. In 12-hour format keep AM or PM; 12 AM is midnight and 12 PM is noon. Copied results include the full date, city, IANA identifier and offset. If automatic copying is unavailable, use the visible text fallback.

For a group, compare the whole meeting

A one-city conversion cannot tell you whether a 90-minute call fits everyone's working day. Use the meeting planner for complete intervals and the international meeting checklist for confirmation steps. Results depend on available browser time-zone rules; recheck important future appointments near the event.

Technical reference: MDN's explanation of ambiguous local times.

Questions, answered

What should I include when sending a converted time?

Include the date, clock time, destination city and IANA time zone. For a cross-date conversion, explicitly state the destination date.

Does swapping cities change the appointment?

After a successful conversion, swapping preserves the absolute instant and expresses it as a clock reading in the new source city.