Time Zone Converter
Enter a date and time, choose the zone it is in and the zone you want, and the converter shows the local time there, both UTC offsets, whether each zone is on daylight saving time and any day shift.
Last updated November 4, 2026
Result
Jan 15, 2026, 11:00 PM in Tokyo
| Measure | Value |
|---|---|
| Time in target zone | Jan 15, 2026, 11:00 PM |
| New York (Eastern) offset | UTC-5 (standard time) |
| Tokyo offset | UTC+9 (standard time) |
| Offset difference | 14 hours ahead of New York (Eastern) |
| Day shift | Same day |
| Same moment in UTC | Jan 15, 2026, 2:00 PM |
Show the work
Formula: target local time = source time − source UTC offset + target UTC offset
- Entered: Jan 15, 2026, 9:00 AM in New York (Eastern), which is UTC-5 (standard time) on that date.
- Convert to UTC: 09:00 − (-300 minutes) = Jan 15, 2026, 2:00 PM UTC.
- Tokyo is UTC+9 (standard time) on that date, so add 540 minutes to UTC.
- Result: Jan 15, 2026, 11:00 PM. Offset difference: 540 − (-300) = 840 minutes. Same day.
Result: Jan 15, 2026, 11:00 PM Tokyo (UTC+9)
How a time zone conversion works
target time = source time − source UTC offset + target UTC offset
Every zone is defined by its offset from UTC. New York is UTC-5 in winter and UTC-4 in summer, Tokyo is always UTC+9, and India is UTC+5:30. The calculator turns your local time into UTC by subtracting the source offset, then adds the target offset.
Offsets are read for the exact date you enter from the IANA database in your browser, so the right daylight saving rule applies. When the result crosses midnight the date shifts by one day, shown as +1 or -1.
See how we calculate for the formulas, sources and review schedule behind every calculator.
Daylight saving time and why offsets change
Many regions move clocks forward an hour in spring and back in autumn, and the southern hemisphere runs the other way: Sydney is UTC+11 in January and UTC+10 in July. Arizona, Hawaii, Tokyo, Singapore, Dubai and Kolkata do not change their clocks.
Skipped and repeated times
When clocks jump forward, one local hour never happens. On March 8, 2026 in New York 2:30 AM does not exist, so the converter says so and asks for a different time.
When clocks go back, one hour happens twice. On November 1, 2026, 1:30 AM occurs first on daylight time (UTC-4) and again on standard time (UTC-5). The converter uses the first occurrence and says so.
How to use the Time Zone Converter
- Enter the date and time you know, in the zone where it applies.
- Choose the From zone for that time and the To zone you want.
- Read the converted time, both UTC offsets and the day shift, or open Show the work.
Worked example
At 9:00 AM on January 15, 2026 in New York (UTC-5), subtract the offset to get 14:00 UTC, then add Tokyo’s UTC+9 to get 23:00. In July New York is UTC-4, so the gap is 13 hours.
| From | To | Result |
|---|---|---|
| Jan 15, 2026, 9:00 AM New York | Tokyo | Jan 15, 11:00 PM (UTC-5 to UTC+9, 14 h) |
| Jul 15, 2026, 9:00 AM New York | Tokyo | Jul 15, 10:00 PM (UTC-4 to UTC+9, 13 h) |
| Jan 15, 2026, 8:00 PM New York | Tokyo | Jan 16, 10:00 AM (next day, +1) |
| Jan 15, 2026, 9:00 AM New York | Sydney | Jan 16, 1:00 AM (UTC+11, +1 day) |
Frequently asked questions
Does the converter handle daylight saving time automatically?
Yes. It looks up each zone’s offset for the exact date you enter, so summer and winter dates differ.
What happens if I enter a time that does not exist?
During the spring clock change one local hour is skipped, so the converter shows a message and you can choose another time.
Which time is used when the clocks go back and a time happens twice?
The first occurrence, still on daylight saving time, is used, and a note under the result says so.
Why is the date different in the target zone?
Zones are up to 26 hours apart, so a time can land on the previous or next calendar day. The day shift row shows +1 or -1 when this happens.