Time Zone Converter
Search cities, choose the date, and see the exact local time—including DST and the date change.
- Runs in your browser — files never leave your device
- Fewer clicks, keyboard friendly
- More accurate results
Source time
Seoul, South Korea — Asia/Seoul
Thursday, October 29, 2026 at 14:37
GMT+9 · UTC+09:00
Converted time
New York, United States — America/New_York
Thursday, October 29, 2026 at 01:37
EDT · UTC−04:00
Calculated in this browser. Your dates and cities are not sent anywhere.
How to use
- Search for the source city, or enter its IANA time-zone name.
- Set the date and clock time that applies in the source city.
- Search for the destination city to see its matching local date and time immediately.
- Check the UTC offsets and date-change label before sending an invitation.
- Use “Swap cities” to start from the converted time in the other city.
Why the date is part of a correct conversion
A city does not keep one fixed UTC offset all year. The converter first resolves the date and clock time in the source IANA time zone, then formats that same instant in the destination zone. That is why it can show a previous or next calendar day instead of asking you to do the date-line arithmetic yourself.
Use named zones such as America/New_York or Europe/London for meetings. A bare offset such as UTC−05:00 has no daylight-saving rule, so it is useful only when a fixed offset is actually intended.
Daylight saving, repeated hours, and unusual offsets
When clocks move forward, a short range of local times never occurs. When they move back, one hour occurs twice. This converter stops on a skipped time and labels a repeated time; for the repeated case it uses the earlier occurrence. It also checks for an offset transition within 36 hours of the selected moment.
Offsets are not always whole hours. India uses UTC+05:30 and Nepal uses UTC+05:45, so rounding a time difference to an hour can be wrong. The offsets shown here come from the time-zone data exposed by your browser’s Intl implementation for the selected instant.
Frequently asked questions
Does this time zone converter handle daylight saving time?
Yes. The result uses the selected date and the source and destination IANA time zones, so the UTC offset can change when either location observes daylight saving time. A warning appears when an offset transition is within 36 hours of the selected moment.
Why does a local time sometimes not exist?
A local time can be skipped when clocks move forward for daylight saving time. For example, a zone that jumps from 01:59 to 03:00 has no local 02:30 on that date, so the converter asks for a different time instead of silently changing it.
Which occurrence is used when a clock time happens twice?
When clocks move back, the converter uses the earlier of the two matching instants and labels the result as ambiguous. A repeated 01:30 is therefore not treated as a fixed one-hour offset without telling you.
Can I enter an IANA time-zone name instead of a city?
Yes. Enter names such as Asia/Seoul, America/Los_Angeles, or Europe/London. Named IANA zones include regional rules, unlike a fixed value such as UTC+09:00.
Are my meeting times or cities sent to a server?
No. The conversion runs in the browser using its built-in internationalization data. The most recent choices are saved only in this browser so they can be restored after a refresh.
Related tools
Updated 2026-10-11