Flagship tool
Time Zone Converter
Convert a date and time from one city or IANA time zone to many — DST-correct for the date you choose, with explicit handling of times that don't exist or happen twice.
How it works
Pick a source city or time zone, a date and a time. Time resolves that wall-clock reading to one exact instant using the zone's rules for that date, then shows the same instant in every destination with its UTC offset, the abbreviation hint, and whether DST is in effect.
Offsets are never fixed: they come from the IANA time-zone database for the specific moment. Abbreviations like IST or CST are shown only as hints next to the city, offset and IANA ID, because they mean different things in different places.
Use Copy result for a plain-text summary or Copy link to share exactly these places, date and time.
Worked example
8:00 PM on Wednesday 7 October 2026 in Chennai (Asia/Kolkata, UTC+05:30) is the instant 14:30 UTC. Each destination shows that instant with the offset its zone uses on that date:
- London: 3:30 PM BST (UTC+01:00)
- New York: 10:30 AM EDT (UTC-04:00)
- San Francisco: 7:30 AM PDT (UTC-07:00)
Two months later the same Chennai time lands an hour earlier in London and New York, because both have left daylight saving time while India never uses it. That's why Time always converts for a specific date.
Enter 2:30 AM in New York on 8 March 2026 and Time stops to explain: that time doesn't exist (clocks jump from 2:00 to 3:00). You choose 3:30 AM EDT or 1:30 AM EST — it never guesses.
Edge cases handled
- Nonexistent local times (spring forward): you choose the shifted-forward or earlier reading.
- Ambiguous local times (fall back): you choose the first or second occurrence.
- Destinations on a different calendar day are marked “+1 day” or “−1 day”.
- Half-hour and 45-minute offsets (India, Nepal, Newfoundland, Chatham Islands).
- Zones that don't use DST at all (India, Japan, most of Africa, Arizona).
- Legacy names such as Asia/Calcutta are accepted and shown as Asia/Kolkata.