Time Zone Converter
Convert a date and time from one time zone to another — daylight saving included.
Pick a date and time to convert.
To convert a time between zones, find each zone’s offset from UTC and add the difference. For example, 3 PM in New York (UTC−5) is 8 PM in London (UTC+0), a gap of +5 hours. The exact gap shifts twice a year as daylight saving time starts and ends, so always convert against a specific date.
How a time zone conversion works
Every time zone is defined as an offset from Coordinated Universal Time (UTC) — the worldwide reference clock. New York runs at UTC−5 in winter, Tokyo at UTC+9 all year, and London at UTC+0 in winter. To move a time from one zone to another you convert it to UTC first, then apply the destination zone’s offset. The difference between the two offsets is how many hours forward or back the clock jumps.
This converter reads the offsets straight from your browser’s built-in IANA time zone database, the same data your operating system uses. That means it knows each region’s daylight saving rules and the exact dates they change, so the result is correct for the specific day you enter rather than a fixed average.
- 1 Pick the source time. Enter the date and time as it reads on the clock in the “From” zone. The field defaults to your current local time.
- 2 Choose the two zones. Set the “From” zone where the time is now and the “To” zone you want it in — for example New York to London.
- 3 Convert to UTC. The tool subtracts the source offset to get the absolute instant. 3 PM New York (UTC−5) becomes 8 PM UTC.
- 4 Apply the target offset. It then adds the destination offset. 8 PM UTC + 0 hours = 8 PM London, so 3 PM in New York is 8 PM in London.
- 5 Read the offset note. The hint shows the hour gap for that date, with daylight saving already factored in.
Common cities and their typical UTC offset
Standard-time offsets; many shift by an hour during daylight saving (DST), so treat these as a guide rather than fixed values.
| City | IANA zone | Typical offset | DST? |
|---|---|---|---|
| Los Angeles | America/Los_Angeles | UTC−8 | Yes (→ −7) |
| New York | America/New_York | UTC−5 | Yes (→ −4) |
| London | Europe/London | UTC+0 | Yes (→ +1) |
| Berlin / Paris | Europe/Berlin | UTC+1 | Yes (→ +2) |
| Istanbul | Europe/Istanbul | UTC+3 | No |
| Dubai | Asia/Dubai | UTC+4 | No |
| Mumbai | Asia/Kolkata | UTC+5:30 | No |
| Beijing | Asia/Shanghai | UTC+8 | No |
| Tokyo | Asia/Tokyo | UTC+9 | No |
| Sydney | Australia/Sydney | UTC+10 | Yes (→ +11) |
Daylight saving and planning across zones
The trickiest part of time zones is that the gap between two cities is not constant. Daylight saving time moves clocks forward an hour in spring and back in autumn, but countries do it on different dates — and some, like Türkiye, China, and India, do not observe it at all. This converter handles those shifts automatically, because it evaluates each zone’s offset on the exact date you enter rather than assuming a year-round value.
Planning a call or class across zones? Convert the proposed time in your own zone to each participant’s zone and check that it lands in waking hours for everyone. For a recurring meeting, re-check it around late March and late October — that is when daylight saving transitions can quietly shift the overlap by an hour. Picking a fixed reference like “14:00 UTC” avoids the ambiguity entirely.