Time Zone Converter
Choose two places and a local date/time to convert the same instant across IANA time zones with daylight-saving rules applied for that date.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, 9:00 a.m. in New York is 2:00 p.m. in London and 7:30 p.m. in Mumbai — the half-hour that reminds everyone India never does anything by halves.
How to use Time Zone Converter
Offsets are rules, not constants. Convert with the rules on:
The Time Zone Converter converts a time and date between zones — New York to London, Chicago to Berlin — applying each zone's real rules, including daylight saving. Enter the time and both zones and read the converted time, day shift included.
- 1Search for the source city or place.
- 2Choose the local date and time there.
- 3Search for the destination city or place.
- 4Read the destination time and the matching UTC instant.
What people use Time Zone Converter for
1. Calls and meetings
The standing use: schedule across zones without the 3 a.m. accident. The working-hours overlap is computed on the Working Hours Overlap Calculator.
2. Flights and itineraries
Departure in one zone, arrival in another, both printed in local time — the converter is how you learn you land 'before you left' (you did not; the date line did it).
3. Broadcasts and launches
Kickoffs, product drops and streams publish in one zone and are watched in fifty — convert the announcement once, correctly.
4. Family across the water
London to Sydney swings between 9 and 11 hours across the year — the converter absorbs the two hemispheres' opposite daylight-saving seasons.
Worked examples
9:00 New York (EST, winter) = 14:00 London = 15:00 Berlin = 19:30 Mumbai = 01:00 next day in Sydney (AEDT). One meeting, four dates' worth of arithmetic, one conversion.
For about three weeks each spring, the US has sprung forward but Europe has not: New York–London shrinks to 4 hours. Converters using fixed offsets get these weeks wrong; rule-based ones do not.
Reference offsets from New York (winter)
Standard-time differences — daylight saving moves several of these.
| City | Behind/ahead of New York |
|---|---|
| Chicago | 1 h behind |
| Denver | 2 h behind |
| Los Angeles | 3 h behind |
| London | 5 h ahead |
| Berlin / Paris | 6 h ahead |
| Mumbai | 10 h 30 ahead |
| Sydney | 16 h ahead (next day) |
Offsets belong to dates, not cities: always convert the specific date, especially near the March and October/November changeovers.
Convert local time without guessing about DST
Time-zone conversion becomes unreliable when people manually add or subtract a fixed number of hours. The offset between two cities can change during the year because daylight-saving schedules do not start and end on the same dates everywhere. This converter resolves each place to an IANA time zone and applies the rules for the exact date you choose.
Use it for international calls, remote teams, travel planning and event scheduling. The result shows the same instant in both locations plus UTC, which makes it easier to verify invitations and avoid mixing up local wall time with a fixed offset.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Time Zone Converter:
- When comparing day length across a year, remember the curve is your latitude's signature: near-equatorial sites hover at twelve hours while high latitudes swing wildly. Choose expectations by latitude, not by calendar folklore.
- Convert solar times to local clock times deliberately: the sun keeps astronomical time, while governments keep political time, and the gap between them is large in many countries. State both when sharing results.
Limits & appropriate use
Solar arithmetic's limits are small but real: the official zenith encodes average refraction, not today's atmosphere; coordinates are rounded to your input's precision; and terrain is absent unless you add height yourself — a mountain rises the sun late and the formulas won't know. Time adds the political layer: zones and DST are human law, and western edges of big zones (Spain, western China) make solar noon wander hours from clock noon. Every output here therefore carries its convention and both clocks, because an unanchored sunrise time is an argument, not a fact.
Lunar and seasonal outputs carry their own gentle limits: phase from the synodic approximation is hours-precise, which outruns every planning need but not ephemeris science; day length is geometric daylight, not sunshine, and clouds belong to climate's department. Escalation is rare and well-defined — astronomical almanacs and ephemerides for science, terrain-aware apps for mountain photography, and the tz database maintainers whenever a government invents a new DST rule at 48 hours' notice, as they delight in doing.
- Science-grade ephemerides → astronomical almanacs/JPL horizons.
- Mountain sunrise/sunset → terrain-aware horizon adjustments.
- Legal daylight definitions → jurisdictional statutes (they vary!).
Data & methodology
Coordinates are mapped to an IANA time zone; browser Intl rules convert the selected local wall time through UTC to the destination zone.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Declination
- The sun's latitude-equivalent angle, ±23.44° across the year.
- Equation of time
- The sundial-vs-clock correction from orbit eccentricity and tilt.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Sun & Moon. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- Coordinates are mapped to an IANA time zone; browser Intl rules convert the selected local wall time through UTC to the destination zone.
- Before relying on the answer
- Check the date, location and time zone together. A solar or lunar event is tied to all three, and some events do not occur at high latitudes on a given date.
- What the result cannot establish
- A calculated event assumes the model's horizon and atmospheric conventions. Buildings, terrain and local weather can alter what you observe.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Does it handle daylight saving time?
Yes. The converter uses the selected date and IANA time-zone rules, so DST changes are reflected where applicable.
Can I convert between cities?
Yes. Search for each city or place and MapBench resolves its time zone from the coordinates.
Is the result based on my computer clock?
The selected wall-clock time is converted using the source location's time-zone rules, then shown at the destination.
Are sunrise and solar times exact to what I will see?
Calculated events use astronomical geometry. Terrain, buildings, weather and atmospheric conditions can shift what an observer actually sees.
Does daylight saving change the Sun's position?
No. Daylight saving changes the civil clock label, not solar geometry. Timezone rules affect displayed local time.
What happens in the weeks when only one side has changed its clocks?
The gap between the zones temporarily grows or shrinks by an hour (New York–London is 4 hours, not 5, for about three weeks each spring). The converter applies each zone's rules for the exact date, so those weeks come out right.
Can I convert a whole schedule of times at once?
One time per conversion here — step through the schedule, or convert the anchor time and shift the rest by the same difference (valid until a clock-change date intervenes, which the single conversions reveal).
Does it need my location to work?
No — you name both zones explicitly, so the conversion is identical anywhere. Your location only matters if you ask for 'my time' as one of the zones.
Why does the date change?
Enough hours east or west crosses midnight — Sydney is routinely 'tomorrow' from the US. The converter shows the resulting date explicitly.
Half-hour zones?
Handled — India (+5:30), Iran (+3:30) and Newfoundland (−3:30) among them; Nepal's +5:45 quarter-hour too.
What is UTC in all this?
The reference meridian time all offsets hang from — the World Time Zone Map shows the whole pattern at a glance.
Arizona and Hawaii?
No daylight saving there (nor in most of the tropics) — the rules know it even when visitors forget.
Related tools and resources
The map: the World Time Zone Map; overlap: the Working Hours Overlap Calculator; offset by place: the UTC Offset by Coordinates.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our time zones hub
Time Zone Converter sits in the time zones cluster, alongside 16 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Find My Location: GPS vs IP Address vs VPN — What's Actually Accurate? — Why your phone, your public IP, and a VPN can all report different places — and which one to trust when you need real coordinates.