Time Zone Converter
Enter a date and time, pick the source and target zones — get the converted time with correct daylight saving offsets, plus a full city comparison.
All zones at this moment
Times are computed with the IANA time zone database built into your browser, including daylight saving transitions. Historical dates before 1970 may use simplified zone rules.
Frequently asked questions
Does this time zone converter handle daylight saving time?
Yes. It uses the browser’s built-in IANA time zone database (via the Intl API), which includes the full DST history and rules for every zone. That means a New York 9:00 AM in January and a New York 9:00 AM in July are converted with the correct offsets — EST (−5) and EDT (−4) respectively — without you having to think about it.
Why do some conversions change the date?
Because a time zone offset can push the clock past midnight. 9:00 AM in Los Angeles is 5:00 PM in London the same day, but 9:00 PM in Los Angeles is 5:00 AM the next day in London. The result card flags when the target date is a day earlier or later than the source date.
What is UTC and why do time zones use it?
UTC (Coordinated Universal Time) is the global reference clock, replacing GMT as the technical standard. Every IANA zone is defined as an offset from UTC, which is why servers, flight schedules and calendars store timestamps in UTC and convert for display. This converter shows each zone’s offset in the results.
How do I schedule a meeting across time zones?
Convert the proposed time into each attendee’s zone and compare the working-hours overlap. A useful habit: pick the time in the zone with the most restrictive schedule first, then check whether everyone else lands between 8:00 and 18:00 local. The comparison table above shows every listed zone at once so you can eyeball the overlap.