Time Zone Converter

Convert a time from one UTC offset to another, with the local day shown and the overlap for scheduling calls across zones.

How to use this calculator

  1. 1Enter the time and its zone.
  2. 2Choose the zone to convert to.
  3. 3Check the day indicator — converting across zones frequently shifts the calendar date.

How the calculation works

UTC time = Local time − Offset Target local time = UTC time + Target offset
Offset
Hours the zone is ahead of (+) or behind (−) UTC

Converting via UTC as a common reference is simpler and less error-prone than converting directly between two arbitrary offsets.

This uses standard-time offsets. Many regions shift by an hour for part of the year under daylight saving, and the dates that happens vary by country — that is not modelled here.

Worked example

9:00 AM Eastern (UTC−5) converted to London (UTC+0)

  1. 1.9:00 AM in UTC−5 is 14:00 UTC (add 5 hours).
  2. 2.UTC+0 has no offset, so the London time is also 14:00.
  3. 3.That is 2:00 PM, the same day.

Result: 2:00 PM, same day

Why time zones exist

Clock time was originally just local solar time — noon was whenever the sun was directly overhead at your particular location, which meant every town at a different longitude technically had its own correct time, drifting a few minutes from its neighbors. That was a minor curiosity in a world where nobody travelled faster than a horse, but it became a genuine operational hazard once railways started running trains between cities on published timetables. Two towns 50 miles apart could disagree by several minutes about what time it was, which made coordinating a shared schedule dangerous as well as confusing.

Time zones are the compromise that solved this: instead of every location keeping its own precise solar time, a whole band of longitude agrees to share a single offset from a common reference, in exchange for a clock that is only exactly right at one meridian within the zone and slightly off everywhere else in it.

How the world settled on Greenwich

The reference point the world eventually agreed on was fixed at the International Meridian Conference, held in Washington, D.C. in October 1884, where delegates from twenty-five nations voted to designate the meridian running through the Royal Observatory in Greenwich, England as zero degrees longitude — largely because a majority of the world’s shipping already used charts built around it. The conference also recommended dividing the globe into 24 time zones of 15 degrees each, radiating out from that line.

Adoption was gradual rather than immediate — it took decades for most countries to formally align their civil time with the new standard — but the Greenwich meridian has remained the reference point the entire modern time zone system is built from ever since.

UTC, GMT and "my time zone" are not quite the same thing

Greenwich Mean Time, GMT, is technically a specific time zone — the one at zero offset, historically defined by the average position of the sun over Greenwich. Coordinated Universal Time, UTC, is the modern successor used as the reference for civil timekeeping worldwide, kept by a network of atomic clocks rather than the Earth’s rotation. In practice the two are close enough that they are used interchangeably in casual conversation, and this calculator’s "UTC+0" and "GMT" describe the same offset for everyday purposes.

Daylight saving complicates all of this

Many countries shift their clocks forward by an hour for part of the year specifically to shift an hour of daylight from the early morning, when most people are asleep, to the evening, when they are awake and using it — the original justification centered on energy savings, though that benefit remains genuinely disputed by researchers. The dates it starts and ends are not synchronized globally, differ between the northern and southern hemispheres, and change occasionally by legislation, while a large share of the world — including most of Africa and Asia — does not observe it at all.

Because there is no single global daylight-saving calendar to draw from, this converter works from fixed standard-time offsets rather than guessing whether a particular zone is currently in daylight saving. For a specific date, check separately whether either location is observing it and adjust by an hour if so.

Where converting between time zones actually matters

Coordinating anything across more than one time zone eventually runs into this exact calculation.

  • International meetings and callsfinding a time that falls inside working hours for every participant means converting one proposed time into everyone else’s local time.
  • Flight itinerariesdeparture and arrival times are given in local time at each airport, so the true flight duration is only obvious after converting one to the other.
  • Live streaming and broadcast schedulesa single global broadcast time has to be translated into a local start time for each audience.
  • Distributed teamshandoffs between offices or shifts in different regions depend on knowing exactly when one location’s day ends and another’s begins.
  • Financial marketstraders coordinate around the overlapping open hours of exchanges that operate on entirely different local clocks.

What this assumes, and where it stops

Assumptions

  • Fixed standard-time offsets, not adjusted for daylight saving.

Limitations

  • Daylight saving is not modelled. Whether a zone is currently observing it depends on the specific date and location.
  • Some regions use non-standard offsets or have changed their zone historically; only the current common offsets are listed.

Common questions

Does this account for daylight saving time?

No — it uses fixed standard-time offsets. Daylight saving start and end dates vary by country and change some years, so a general converter cannot reliably track them all. For a specific date, check whether either location is currently observing daylight saving and adjust the offset by an hour accordingly.

Why does the date change when I convert?

Because time zones are offset from a shared UTC reference, and a large enough offset difference pushes the clock past midnight. Converting 9 PM in Tokyo (UTC+9) to New York (UTC−5) lands on 7 AM the same calendar day in UTC terms, but the date in New York is still the previous day locally.

Formula and content last reviewed on .

Results are estimates for information only, not professional advice.

Report an error

Tools people commonly use alongside the time zone converter.

See all date & time calculators →