Time Zones Converter
Pick a time, pick where it is, pick where you want it — this time zones converter does the offset arithmetic between the world’s major zones and tells you honestly when the answer lands on a different day.
The Arithmetic: Everything Is a Distance From UTC
Every time zone is a signed distance from Coordinated Universal Time — New York standard at UTC−5, Mumbai at UTC+5:30, Tokyo at UTC+9 — and converting between two zones is nothing but subtracting their distances and adding the difference to the clock: noon in New York (−5) to London (0) is +5 hours, 17:00; to Mumbai (+5:30) is +10:30, 22:30; to Tokyo (+9) is +14, 02:00 the next day — the answers the widget returns for those pairs, and a showcase of the system’s three behaviours: a plain shift, a half-hour shift (India, and a handful of other half- and quarter-hour zones, refuse the whole-hour grid), and a day rollover, which the converter announces rather than hides because “02:00” without “tomorrow” has missed more flights and meetings than any other silent fact in travel. The planet’s full span runs from UTC−12 to UTC+14 — a 26-hour spread, so that at some moments three calendar dates exist on Earth at once — and every conversion on Earth is the subtraction this page performs.
Daylight Saving: The Hour That Moves Twice a Year
The honest complication is printed in the widget’s note and deserves its section: most of the temperate world advances its clocks an hour for the summer (daylight saving time), which changes the effective offset while the standard offset — the one the selector names — stays fixed. The traps are calendrical: the US and Europe switch on different March and October/November Sundays, creating two or three weeks a year when the New York–London gap is 4 or 6 hours instead of the usual 5; the southern hemisphere saves daylight in the opposite season (Sydney’s +11 summer against its +10 standard coincides with the north’s winter); and Arizona, Hawaii, India, China and Japan do not switch at all. A converter can handle this two ways — a live database of every jurisdiction’s rules, or the standard offsets stated plainly with the one-hour adjustment named — and this page takes the second, honest route for a reference tool: the arithmetic is exact for the offsets selected, the note tells you when to adjust, and a meeting that truly matters deserves the live check the note recommends, at timeanddate’s converter, the field’s reference implementation.
The Meeting Problem: Finding Hours That Work Everywhere
The converter’s dominant use is scheduling across the spread, and its worked geography teaches the craft. The golden window of global business runs roughly 13:00–17:00 UTC: morning in the Americas (08:00–12:00 New York), afternoon in Europe, evening in India (18:30–22:30) — and the middle of the night in East Asia and Australia, which is why truly global calls rotate their pain. The extreme pair, New York and Sydney, shares almost no civilised hour (noon in New York is 03:00–04:00 in Sydney), so their meetings are always someone’s early morning or late evening, and the day shift crosses the date line — a Tuesday call in New York is a Wednesday in Sydney, which the converter’s day announcement exists to keep out of calendar invitations. The craft rules follow from the arithmetic: always invite in the invitee’s zone with both times stated, never say “tomorrow” across the Pacific without a date attached, and treat the 30- and 45-minute zones (Mumbai, Kathmandu at +5:45, Adelaide) as first-class — the half hour in the worked example’s 22:30 is not a rounding error but India’s whole position on the grid. Teams that rotate the inconvenient slot — rather than fixing the pain permanently on the far side of the world — keep their global members measurably longer, a management finding the offset table predicts for free.
Why Zones Are Where They Are
The map’s jaggedness is politics drawn over astronomy. Solar time would give every meridian its own noon; standard zones (a 19th-century railway invention, GMT their original anchor) averaged that into hour-wide bands, and nations then bent the bands: Spain keeps Central European time (a 1940s political alignment) despite sitting on Britain’s longitude, so its evenings run famously late; China spans five geographical zones under a single UTC+8, so sunrise in Kashgar comes near 10:00 by the clock; India chose one zone at +5:30, the half-hour compromise for a wide country. The converter’s list is therefore labelled by city rather than country where it matters — the zone is the city’s, whatever the atlas implies — and the student’s takeaway stands: a time zone is a legal fact about a place, not a physical one, which is why its database (the IANA tz database, maintained from legislation worldwide) is a political document wearing an engineer’s clothes.
The Date Line: Where the Next Day Actually Lives
The converter’s “next day” label points at a real place: the International Date Line, zigzagging through the Pacific so that island nations share a date with their trading partners rather than with their longitude. Cross it westward and a day is added; eastward, repeated — which is how Samoa famously skipped December 30, 2011 entirely, moving from UTC−10 to UTC+14 to align with Australia and New Zealand, and how a traveller can land in Honolulu two hours “before” leaving Tokyo on the same calendar reading. The 26-hour spread of offsets (from UTC−12 to UTC+14) means that for two hours each day, three calendar dates are in progress on Earth at once: when it is Tuesday 01:00 in Kiritimati (UTC+14), it is Monday 11:00 in London — and still Sunday 23:00 in the UTC−12 zone. Sunday, Monday and Tuesday, simultaneously, all correct — a fact any reader can reproduce by chaining this converter’s day-shift labels across the Pacific, and one that no single-clock intuition survives unassisted. The pilots and dispatchers who live across the line plan in UTC for exactly this reason: it is the one clock that never asks which day it is somewhere else, or whether summer has moved somebody’s hour.
Related Tools
More from the Conversion Calculators hub: the Time Difference Calculator — gaps between moments rather than places — the Elapsed Time Calculator, and the Time Until Calculator for counting down in whatever zone the event lives.
Frequently Asked Questions
What time is it in Tokyo when it is noon in New York?
02:00 the next day, on standard offsets — Tokyo is UTC+9, New York standard is UTC−5, and the 14-hour difference rolls noon forward past midnight. In summer, with New York on daylight time (UTC−4), the answer is 01:00 the next day — Japan does not observe daylight saving, so the pair’s gap breathes between 13 and 14 hours across the year. The converter returns the standard-time figure and its note names the one-hour summer adjustment; for these two cities the day-after is the constant.
Why is India half an hour off the grid?
Because a single zone for a country spanning about 2,000 km of longitude (roughly two hours of solar time) was set at the compromise meridian — 82.5°E, giving UTC+5:30 — splitting the difference between its east and west rather than favouring either. India is the famous case, not the only one: Iran (+3:30), Newfoundland (−3:30), and Nepal — the grid’s extremist — at +5:45, a quarter-hour offset chosen to be distinct. The converter includes Mumbai at its true half-hour offset; a tool that rounded it would misstate every Indian conversion by thirty minutes.
How many time zones are there?
Twenty-four in the idealised model (one per hour of the day) and about thirty-eight distinct UTC offsets in civil use once half- and quarter-hour zones and daylight variants are counted — and several hundred named zones in the IANA database, because zones are defined by place and history (each with its own legislation and switch dates), not merely by offset. Two places can share today’s offset and still be different zones, diverging when their daylight rules differ — the reason serious systems store the zone name, not the number.
What is UTC, and how is it different from GMT?
UTC is the modern atomic-clock standard the offsets are measured from; GMT is its historical predecessor (Greenwich Mean Time, the railway-era anchor) and survives as the name of the UK’s winter time zone (UTC+0). For conversion purposes at whole-hour precision they coincide — nobody’s meeting has ever failed over their sub-second definitional difference — and the converter uses UTC as the reference because that is the standard the world’s zone database is written against.
Does the converter handle dates, or only clock times?
Clock times, with the day shift announced — which is the honest scope of a zone conversion: “02:00 the next day” is a complete answer for a recurring call or a same-week plan. For a specific dated event, the daylight rules of that date govern, and the article’s advice applies: verify against a live, date-aware source. Within its scope the arithmetic is exact — offsets in, times out, the day carried openly — and the calendar questions belong to this site’s date tools, linked above.