Time Zone Converter
Scheduling across oceans without the 3 AM surprise: pick a time and two places, and see exactly when it lands — DST included.
Spotted a mistake or have an idea? — errors get fixed and credited publicly.
Last reviewed: July 20, 2026 · Formulas verified by automated tests before every release.
Why time zone math goes wrong
Manual conversion fails for two reasons: daylight saving time (zones shift on different dates, and some never shift at all) and half-hour offsets (India +5:30, parts of Australia +9:30). This converter uses the official IANA time zone database built into your browser, so the rules for every zone and every date are applied automatically.
Handy overlaps for scheduling
- US East ↔ Europe: 9–11 AM ET = 2–4 PM London = 3–5 PM Central Europe.
- US ↔ India: 8–10 AM ET = 5:30–7:30 PM IST — the golden window.
- Europe ↔ Asia-Pacific: 8–9 AM London = 5–6 PM Tokyo = 6–7 PM Sydney (winter).
Frequently asked questions
Does the converter handle daylight saving time?
Yes — conversions use your browser's IANA time zone database, which applies the correct DST rules for each zone and each date automatically, including future and past dates.
Why does the date sometimes change?
Big time differences cross midnight: 9 PM Tuesday in Los Angeles is already 9:30 AM Wednesday in India. The converter warns you whenever the day flips.
What is the best time for a call between the US and India?
The classic overlap is early US morning / Indian evening: 8–10 AM Eastern = 5:30–7:30 PM IST. India runs on a single half-hour-offset zone (UTC+5:30) year-round.
Why do some zones shift against each other during the year?
Not everyone observes DST: most of the US and Europe shift, while India, China and Japan never do. So London–Delhi is 5:30 in winter but 4:30 in summer.