Convert a date and time between time zones with real daylight-saving rules — see the same moment in UTC, London, New York, Karachi, Tokyo, Sydney and more, with day shifts marked. Runs entirely in your browser — your numbers never leave this device.
| City / zone | Local time | Offset | Day |
|---|---|---|---|
| New York — source | Mon 2 Nov 2026, 15:00 | UTC-5 | Source day |
| UTC | Mon 2 Nov 2026, 20:00 | UTC+0 | Same day |
| London | Mon 2 Nov 2026, 20:00 | UTC+0 | Same day |
| Los Angeles | Mon 2 Nov 2026, 12:00 | UTC-8 | Same day |
| Karachi | Tue 3 Nov 2026, 01:00 | UTC+5 | +1 day |
| Dubai | Tue 3 Nov 2026, 00:00 | UTC+4 | +1 day |
| Kolkata | Tue 3 Nov 2026, 01:30 | UTC+5:30 | +1 day |
| Tokyo | Tue 3 Nov 2026, 05:00 | UTC+9 | +1 day |
| Sydney | Tue 3 Nov 2026, 07:00 | UTC+11 | +1 day |
Offsets come from your browser's built-in IANA time-zone database, so daylight saving is applied by date: New York is UTC−5 in November (EST) but UTC−4 in July (EDT). A “+1 day” row means the converted time falls on the next calendar date — the moment is the same, the date on the wall is not.
| Zone | Local time | Offset |
|---|---|---|
| New York (America/New_York) | Mon 2 Nov 2026, 15:00 | UTC−5 |
| Los Angeles (America/Los_Angeles) | Mon 2 Nov 2026, 12:00 | UTC−8 |
| UTC | Mon 2 Nov 2026, 20:00 | UTC+0 |
| London (Europe/London) | Mon 2 Nov 2026, 20:00 | UTC+0 (GMT) |
| Dubai (Asia/Dubai) | Tue 3 Nov 2026, 00:00 | UTC+4 |
| Karachi (Asia/Karachi) | Tue 3 Nov 2026, 01:00 | UTC+5 |
| Kolkata (Asia/Kolkata) | Tue 3 Nov 2026, 01:30 | UTC+5:30 |
| Tokyo (Asia/Tokyo) | Tue 3 Nov 2026, 05:00 | UTC+9 |
| Sydney (Australia/Sydney) | Tue 3 Nov 2026, 07:00 | UTC+11 (AEDT) |
Enter a date and time, choose the zone it is expressed in, and the converter shows that same instant across nine reference zones, with each zone's UTC offset and a day-shift marker. The method has two steps and no shortcuts: first the local time is converted to a UTC instant using the source zone's offset on that specific date, then each target time is produced by applying the target zone's offset on that date. Both offsets come from the IANA time-zone database built into your browser — the same data operating systems and airlines use.
Applying offsets by date is the whole game, because offsets move. New York is UTC−5 in November (Eastern Standard Time) but UTC−4 in July (Eastern Daylight Time); London is UTC+0 in winter and UTC+1 in summer; Sydney runs the other way, gaining an hour when the northern hemisphere loses one. A converter that uses today's offsets for a date six months away can be wrong by an hour in several rows at once — around the spring and autumn changeovers, a meeting set for 'the usual time' quietly moves. The static table below is a fixed reference you can check this tool against: 3 pm in New York on 2 November 2026, after the US clocks have gone back.
Day shifts are marked honestly rather than left for you to spot. When a converted time falls on a different calendar date from the source — Karachi at 1 am the next morning — the row says '+1 day'. The instant is one moment; only the date on the wall differs. Nothing you enter is uploaded: the conversion happens entirely in your browser.
Daylight saving. The US springs forward in March (Eastern Daylight Time, UTC−4) and falls back in November (Eastern Standard Time, UTC−5). The converter applies the offset in force on the date you enter — 2 November 2026 is after the fall-back, so New York is UTC−5 in the reference table, while a July date would show UTC−4.
The converted local time falls on the next calendar date relative to the source date. 15:00 Monday in New York is 01:00 Tuesday in Karachi: it is the same instant, but Karachi's wall clock has already rolled into Tuesday. The marker saves you from booking a call for the wrong day.
London keeps Greenwich Mean Time (UTC+0) in winter and British Summer Time (UTC+1) from late March to late October. In the November reference table London matches UTC exactly; convert a July date and London runs one hour ahead of UTC.
Fourteen source zones are offered, including UTC, London, Paris, four North American zones, Dubai, Karachi, Kolkata, Singapore, Tokyo, Sydney and Auckland. Every conversion shows the nine reference zones in the results table; pick any listed zone as your source, including one of the nine to see its row marked as the source.
They follow the IANA database in your browser, which encodes each zone's legislated rules years ahead — including scheduled DST transitions. If a government changes its rules (as happens occasionally), browsers update the database, and this tool's answers update with it. For dates near a announced-but-unusual change, double-check with the organiser.
No. The conversion uses your browser's own time-zone database and runs entirely on your device — nothing is uploaded or stored.
More in Date & Time Tools · Browse all tools