🌍 Timezone Converter
Convert a moment in time between zones. Daylight saving is handled by your browser’s own timezone database, so the offsets shown are the ones actually in effect on that date — not a fixed guess.
Why the offset depends on the date
The converter does not hold a table of fixed offsets. It reads your wall-clock time as belonging to the From zone, works out the true instant, then asks the browser's IANA timezone database what each zone's offset was at that moment. The gap between two cities is not a constant.
Take 09:00 in New York. On 15 June 2026 that is 14:00 in London, five hours ahead. On 15 March 2026 it is 13:00 - only four hours, because US clocks moved forward on 8 March and British ones did not until 29 March. Meetings booked in those three weeks are the classic way to be an hour late.
Reading the result
- The difference is shown in hours and can be fractional. New York to Kathmandu reads 9.75, because Nepal runs at UTC+05:45.
- Each row carries the offset in effect on that date plus the zone's short name, so you can see EDT rather than EST and know DST was applied.
- The UTC and Unix timestamp rows describe that same instant, ready to paste into a log or an API call.
- Zones are IANA names, not abbreviations. Pick Asia/Kolkata rather than IST, which is claimed by India, Ireland and Israel.
Frequently asked questions
What time is 9am New York in London?
2pm for most of the year, but 1pm between the second Sunday in March and the last Sunday in March, when the US has changed clocks and the UK has not.
Does the converter handle daylight saving automatically?
Yes, using the date you enter rather than today's. Convert a meeting in November and it applies November's offsets.
Why do some zones differ by 45 or 30 minutes?
Not every country picked a whole hour. Nepal is UTC+05:45, India UTC+05:30 and South Australia UTC+09:30, and the tool shows those as fractional hour differences.