Time Zone Converter
Translate any date and time between cities — correct for daylight saving on that exact date, with the day change flagged and both UTC offsets shown, so "3 PM your time" is never ambiguous again.
Convert a time
Example: July 15, 3:00 PM in New York is 4:00 AM the next day in Tokyo.
Why the date matters, not just the zones
Time-zone arithmetic isn't a fixed table — it changes with the calendar. In the worked example, 3:00 PM in New York on July 15 is 4:00 AM the next day in Tokyo: New York is on daylight saving (UTC−4) while Tokyo never shifts (UTC+9), a 13-hour gap. Run the same conversion in January and the gap becomes 14 hours, because New York has fallen back to UTC−5. The converter evaluates the rules for the exact date you enter — the same IANA database your operating system trusts — so seasonal shifts, half-hour zones like India, and 45-minute zones like Nepal all come out right.
The classic scheduling pitfalls this avoids
Most cross-zone mistakes come from three habits: assuming the difference you remembered from last winter still holds (DST switches move on different dates in the US, Europe, and the southern hemisphere); trusting three-letter abbreviations (IST means three different zones); and forgetting the date line (a Sydney "Monday 9 AM" starts on your Sunday). Converting with cities and explicit dates — and reading the day-change flag — eliminates all three.
Frequently asked questions
Why do some conversions land on a different day?
Because the zones sit on opposite sides of the moment where the calendar flips. A New York afternoon is already the next morning in Tokyo, and a Tokyo morning is still the previous afternoon in Los Angeles. The converter flags "next day" or "previous day" whenever the calendar date changes.
Does it handle daylight saving correctly?
Yes — and per date, which matters. The gap between London and New York is usually 5 hours, but it becomes 4 for a few weeks each spring and about a week each fall, because the two switch DST on different schedules. The converter evaluates the offsets for the exact date you enter using the IANA time zone database.
What happens if I enter a time that does not exist?
On spring-forward night, an hour vanishes — 2:30 AM simply never happens in a zone jumping from 2:00 to 3:00. If you enter such a time, the converter resolves it deterministically to a nearby real moment rather than failing; the exact convention is documented on the methodology page.
Are city dropdowns the same as time zones?
Each city maps to its IANA zone (New York → America/New_York), which is more reliable than abbreviations like EST or IST — those are ambiguous (IST is India, Ireland, and Israel) and do not encode DST rules. Pick cities and the correct zone rules follow.
Conversions are computed locally in your browser from its IANA time zone data; nothing you enter is transmitted. Zone rules can change with little notice for some jurisdictions — for legally critical timing, confirm against an official source. See the methodology page.