Time Zone Converter
Convert a time from one time zone to another to organise a call, a meeting or a trip. The calculation relies on the IANA time zone database built into PHP : the switch to daylight saving or standard time is therefore applied automatically based on the date entered, with no risk of manual calculation error.
Calculator
Results
| Departure | — |
| Arrival | — |
| Current time difference | — |
How the time zone conversion is calculated
Arrival time = Departure time − UTC offset of the departure zone + UTC offset of the arrival zone
The UTC offset of each zone isn't a constant : it changes on the dates when clocks move to daylight saving or standard time, which aren't the same everywhere in the world (some countries don't change their clocks at all). That's why the time difference between two cities can vary by ±1 hour depending on the time of year — the calculation is therefore always made from the exact date entered, never from a fixed offset held in memory.
How time zones work (Greenwich meridian, UTC, GMT)
The Earth turns 360° in twenty-four hours, so 15° of longitude is one hour of solar time. Draw that on a globe and you get 24 tidy slices, pinned to the Greenwich meridian — the origin agreed at the 1884 conference.
Borders ignore meridians. A government can put a whole country on one legal clock for trade, politics or sheer habit, even when the sun disagrees. The jagged map you see in atlases is that decision, not a geometry exercise.
GMT and UTC get used as if they were twins. They aren't, quite. GMT is a time zone, the one at Greenwich. UTC is a time scale, kept by atomic clocks, with the odd leap second. For booking a call, treat them as the same (UTC+0 ≈ GMT). This converter, like most modern tools, reports offsets against UTC. No need to be precious about it.
Daylight saving vs. standard time: why the gap between two cities isn't always constant
London and New York are five hours apart. Until they aren't.
Britain switches between GMT and BST on the last Sunday of March and the last Sunday of October. The United States starts daylight saving on the second Sunday of March and gives it up on the first Sunday of November. For two or three weeks in spring, and a week in autumn, the gap is four hours, not five. Australia flips in the opposite season. Japan, India, China and most of Africa do not change their clocks at all.
That is why we always calculate from the date you type, never from a remembered offset. The IANA database knows, for each city, whether that particular day is on daylight saving or standard time.
The International Date Line: what happens when you cross it
Near 180° longitude the calendar jumps. The line kinks around island groups so a single country is not split in two. Kiribati's Line Islands sit at UTC+14 and see the new year among the first; a few Pacific islands sit at UTC−11 or UTC−12, among the last.
Cross it westbound (Americas towards Asia) and you skip a day. A Monday-night flight from Los Angeles lands in Tokyo on Wednesday morning. Go east and you live the same date twice. The sun has not leapt. Only the weekday has.
It is not an extra time zone to recover from. The journey lasts what it lasts; the calendar is what moved.
Scheduling an international meeting without a time zone mistake
Look for overlapping office hours. 15:00 in London is 10:00 in New York — workable. 15:00 in London is 23:00 in Tokyo. Someone is getting up too early, or staying up too late.
The safest habit is to pick one time in UTC, then convert for each person. Mental arithmetic ("ten my time, so four yours") is how daylight saving bites you — especially in those March weeks when the US has already sprung forward and Britain has not. Type the actual date of the call, not a generic Tuesday.
Once the local time is fixed, a countdown keeps you from missing it by a minute, time zone or not.
Time zones with a non-integer offset: India (UTC+5:30), Nepal (UTC+5:45)
Whole hours feel natural. India declined the invitation.
The whole country runs on UTC+5:30 (IANA id Asia/Kolkata),
all year, with no daylight saving. Nepal goes further: UTC+5:45
(Asia/Kathmandu). Iran is at +3:30, Newfoundland at −3:30, Adelaide at
+9:30. Those half-hours and quarter-hours are the legal offsets, not rounding errors.
So a result that reads 10:45 is not a bug. That is Mumbai, or Kathmandu, refusing to land on the hour.
Why China uses a single time zone despite spanning five geographic ones
East to west, China covers roughly five geographic zones, from about UTC+5 to UTC+9.
In law, since 1949, it has one: UTC+8, Beijing time
(Asia/Shanghai in the list).
The sun did not get the memo. In Kashgar it is highest around 15:00. Parts of Xinjiang unofficially keep UTC+6 in daily life, while trains and flights stay on Beijing time. A 9 a.m. meeting does not mean the same morning in Shanghai and in Ürümqi.
The converter applies legal time. It cannot guess an unwritten local custom.
Jet lag and time difference: rough guidance by number of zones crossed
The time difference is what the clocks say. Jet lag is what your body does with that — sleep, appetite, mood — until the internal clock catches up.
A common rule of thumb: one time zone ≈ one day to settle. Six hours, about a week. Eastbound is worse: you shorten the day, and advancing the body clock costs more than delaying it. Westbound you lengthen the day, and most travellers cope better. The Date Line itself adds nothing. Hours shifted matter; the name of Wednesday does not.
Convert the arrival time so you know whether it will be 3 a.m. on the ground. For sleep, count the zones, not the skipped calendar days.
Legal time zone vs. true solar time: the difference explained
Solar noon is when the sun is highest. Legal time is what the statute puts on station clocks and payslips.
Spain is the textbook case. The peninsula sits geographically nearer UTC+0 — with Portugal and the UK — yet legally it runs Central European Time (UTC+1 in winter, UTC+2 in summer), aligned with Berlin since 1940. In Galicia in August the sun culminates around half past two. Britain, sitting on Greenwich, is one of the few large countries whose winter clock still tracks the sun reasonably well. BST then pulls it an hour off in summer, on purpose.
We convert legal time to legal time. The tool will not tell you whether it is still daylight outside.
Why a named city beats a raw offset such as UTC+1
Europe/London is not "UTC+0". In January, yes. In July it is BST, UTC+1.
A raw offset never springs forward. An IANA city does.
Pick a city and you inherit its daylight-saving rules, its historical quirks, India's extra thirty minutes. Pick "UTC+1" and you freeze an offset — fine for a ship at sea, a poor idea for a June meeting in Madrid.
The list here is a few dozen landmark cities, not the ~400 IANA identifiers. Guided choice, not a search box. If your town is missing, take the large city that shares its legal time zone.
tzdata: the IANA database this converter actually uses
PHP does not ship a homemade table "London = +0". It reads the IANA time zone
database (tzdata, formerly Olson): Continent/City identifiers,
changeover dates, the history of decrees.
That is how it knows India has no daylight saving, São Paulo no longer has it, and
Sydney flips in the opposite season from Berlin. We do not maintain that table by
hand. It comes with PHP, through DateTimeZone.
When a country changes the law, tzdata follows — in the next update. Until then the calculation reflects published rules, not a rumour of reform.
Will the clocks still change? The European (and British) stalemate
In 2018 the European Commission ran a consultation. Parliament voted to stop the twice-yearly change. Member states would then pick permanent summer time or permanent standard time. The file has sat there ever since.
We are not forecasting a date. There isn't one. In 2026 the EU still moves its clocks in March and October. Britain, outside the Union, still sets BST on its own — and still does so on the same weekends.
For a meeting next year, type the date. If the law ever changes, the IANA database will follow. This page will not pretend to know when.