How to use this calculator
The time zone converter translates a local date and time in one city into the corresponding local times elsewhere. Choose the source location, enter the event’s date and time, then select destination cities. Each result includes the local date, which prevents an evening event in one region from being mistaken for the same calendar day everywhere.
Use the event’s actual date rather than today’s date when planning ahead. Seasonal time changes can alter offsets and temporarily change the gap between two cities. A named location gives the calculator the rules needed for that date. An abbreviation such as CST is less precise because the same letters can refer to different regions.
Formula and calculation method
Source local timestamp + source zone → one instant → destination local timestamp in each target zone.
Resolve the source timestamp
The source location and date determine its applicable offset. Once the local reading is resolved to an instant, every target can represent that same moment. If the source reading repeats during a backward clock change, choose the first or second occurrence. A missing reading during a forward jump needs an explicit resolution rather than an unnoticed guess.
Preserve dates and event duration
A conversion can cross a day, month, or year boundary. Keep the complete target date with the local time when copying or sharing the result. If you enter an event duration, its elapsed length is carried with the instant-based event. A clock change can make the displayed start-to-end readings look different from that elapsed duration.
Worked examples
New York evening to Tokyo afternoon
At 23:00 in New York on January 15, 2024, the UTC instant is 04:00 on January 16. Tokyo is nine hours ahead of UTC, so the result is 13:00 on January 16. The local dates differ, even though both readings identify exactly the same moment.
London’s seasonal offset
At 12:00 UTC on January 15, 2024, London is also at 12:00. At 12:00 UTC on July 15, London is at 13:00 under that year’s summer rules. A converter that always treated London as UTC would therefore be an hour wrong for the second example.
Two occurrences of one source time
In New York on November 3, 2024, 01:30 occurred twice during the backward clock change. The first occurrence corresponds to 05:30 UTC and the second to 06:30 UTC. Selecting an occurrence changes every destination result by one hour, so the choice must reflect the intended event.
Edge cases and practical checks
Missing local readings
When a clock jumps forward, some local readings never happen. A requested event in that gap cannot be converted exactly as written. Review the available adjustment policy and the resulting timestamp before sharing. Moving a nonexistent time to a valid one changes the event specification and should be intentional.
Future rules and ambiguous place names
Conversions rely on time-zone data available in your browser. Future government decisions can change the result after software updates. Choose a specific city or IANA zone when place names are ambiguous, and recheck distant future events before they occur. The converter does not independently download every new rule announcement.
Frequently asked questions
Does the converter handle daylight saving automatically?
It applies the selected zones’ rules for the entered date. You still need to resolve a repeated or missing source reading when the clock transition makes it ambiguous. Enter the actual event date, because converting only a time of day cannot determine the seasonal offset.
Why is the destination on the next day?
The target location’s offset can move the same instant across midnight. That is expected, not an extra duration added to the event. Include the displayed target date in invitations and messages, especially for evening meetings or overnight travel across distant regions.
Can I just add the current hour difference?
That works only when the difference remains the same on the event date. Seasonal transitions and rule changes can alter it. Use the date-specific conversion when planning ahead or checking historical timestamps, particularly during the weeks when regions switch clocks on different dates.
What do first and second occurrence mean?
A backward clock change can repeat a local hour. The first occurrence is the earlier instant and the second is the later one. Both can display the same local clock reading while having different UTC offsets. The original event record must tell you which was intended.
Does changing the source city keep my intended event?
Changing the location while keeping the same local clock reading generally selects a different instant. If you want to preserve a fixed event, work from its resolved timestamp or use a shared calculation. Always review the destination dates after editing the source.
Can I share a conversion?
Yes. Copy a calculation link after selecting the source, targets, and date. A recipient can reopen and adjust those inputs. The canonical page remains the general converter page; the shared parameters describe your particular scenario and should be reviewed before sending.
Published by TrueHour. Calculation methodology and sources · Report a correction · Time and date guides